Dashboard architecture
Vifu publishes one deployment-local Dashboard. The same open application is
embedded in the vifu binary and can run beside a self-managed Vifu Server.
Open Dashboard
The open Dashboard is attached to one Vifu Server. Its server-side shell uses the deployment Admin Key and creates an HttpOnly browser session. The browser calls a same-origin proxy and never receives the Admin Key.
The release binary embeds the same views directly. Run vifu, use the TUI for
live activity, and press B to open the Dashboard served at the same Server
address.
It owns only Runtime operations: Apps, Agents, Providers, endpoints, keys, Gateway connections, traces, releases, deployment status, and Runtime settings. It does not own account login, organizations, billing, cloud ownership, or production deployment configuration.
Hosted Vifu Cloud Console
The same Vifu.dev application serves login at vifu.dev and the Console at
dashboard.vifu.dev. The Console receives an HttpOnly parent-domain session,
asks the account API for Apps visible to that user, and obtains short-lived
Runtime authority on the server. It imports the open @vifu/console views, but
keeps account sessions, identity integration, ownership checks, and Runtime
grants in the hosted application boundary.
An Agent Gateway can create a temporary Guest App for a first run. The TUI
opens dashboard.vifu.dev/pair with a one-time claim token in the URL fragment.
The Dashboard removes that fragment from the visible URL, retains it across the
account login redirect, and sends it through a same-origin server route. The
account API exchanges the signed-in identity for short-lived Runtime authority
before claiming the App. Neither that authority nor the claim token is
stored in a browser cookie or exposed to client code after the claim completes.
Dependency direction
Hosted products can import Vifu's open runtime views. The open Dashboard never imports account or Cloud control-plane code.