Components Overview

VGate ships as four independently-buildable components. There is no monorepo build — each is built, tested, and linted from within its own directory. They communicate over the manager's REST API.

All components are hosted under the vgate-project GitHub organization:

• Manager — github.com/vgate-project/vgate-manager
• Server — github.com/vgate-project/vgate-server
• Admin Console — github.com/vgate-project/vgate-admin
• User Portal — github.com/vgate-project/vgate-user

Component	Repository	Stack	Builds to
Manager	vgate-manager	Go 1.26 · Gin + GORM	vgate-manager binary
Server	vgate-server	Go 1.26 · xray-core	vgate binary
Admin Console	vgate-admin	Vue 3 · Vite · TS	static dist/
User Portal	vgate-user	Vue 3 · Vite · TS	static dist/

Dependencies between components

Admin Console ─┐
               ├─► Manager ◄─► DB
User Portal  ──┘        ▲
                        │ REST /api/v1/server/*
                        │ node token auth + traffic reports
                   Server (proxy node)

• The manager depends on a database (SQLite or Postgres). Everything else depends on the manager.
• Server nodes depend on the manager at runtime (sync + report). They do not depend on the frontends.
• The frontends depend only on the manager's REST API.

Who runs what

• Operators deploy and run the manager + server nodes, and use the admin console.
• Customers use the user portal and VLESS client apps with their subscription link.
• Developers may replace the user portal or build custom clients against the REST API.

Per-component docs

• Manager (Backend API)
• Server (Proxy Node)
• Admin Console
• User Portal