Self-hostingSelf-hosting
Self-hosting Vifu
A complete Vifu deployment runs the Dashboard, Vifu Server, Vifu Agent Gateway, and PostgreSQL. Choose one starting path:
| Goal | Guide |
|---|---|
| Try Vifu or run one persistent deployment | Run with Docker |
| Develop the Dashboard or Rust runtime | Run Vifu locally |
Both paths run the same product and use the same project data model. Docker is the shortest first run. Local development keeps the Rust and Next.js processes outside Docker so source changes are faster to test.
Services
| Service | Purpose | Default address |
|---|---|---|
| PostgreSQL | Projects, releases, sessions, credentials, and logs | 127.0.0.1:5432 |
| Vifu Server | Runtime HTTP, SSE, and Gateway connection | 127.0.0.1:6790 |
| Dashboard | Project and runtime management | 127.0.0.1:6791 |
| Agent Gateway | Provider discovery and invocation | Connects internally to Vifu Server |
After the stack is healthy, create a project and continue with Agent Providers.
Before remote access
The included ports bind to loopback by default. For remote access, keep PostgreSQL private and place the Dashboard and runtime behind HTTPS and your chosen network access controls. Never expose provider credentials, bootstrap values, or the Dashboard's server credential to browser code or game clients.