The web console for Flui, the cloud platform you build on the providers you choose and on servers you own.
Website · Docs · flui-core · flui.yaml spec
This is the web interface of Flui. It ships with every Flui installation, runs on your own infrastructure and talks only to your own Flui API. There is no hosted tenant in front of it and no telemetry leaving your network.
The dashboard, the flui CLI and AI agents over MCP are clients of the same API, so anything you start in one you can follow in the others.
If Flui is useful to you, a ⭐ on flui-core helps other people find it.
- Topology: every cluster, server and application on one map, with live traffic and what needs attention.
- Applications: deploy from a repository, a framework template, the catalog or your own
flui.yaml; follow builds, releases, logs, metrics and crashes; scale, restart and roll back. - Databases: backups and point-in-time recovery, connection pooling, active sessions, an SQL console and migration between clusters.
- Clusters and infrastructure: servers, networks, firewalls, DNS and certificates across providers, with scaling groups that grow and shrink within a spending cap.
- Agents: keys for AI agents limited to what they need, and the approvals they ask for before they change anything.
- Access: projects, people and what each of them can see and do.
- Providers and settings: cloud keys, image registry, mail, backups and platform updates.
The dashboard comes up with every Flui installation. To create one:
npm install -g @flui-cloud/cli
flui vault init
flui config set hetzner
flui env create --provider hetzner --region nbg1 --node-size cx23The install page builds these commands for other providers, regions and your own servers.
The dashboard talks to a running Flui installation:
# 1. Wire the endpoints and sign-in configuration into src/assets/config.json
flui env export-config --dashboard-path .
# 2. Install and run the dev server
pnpm install
pnpm start # http://localhost:4200Working against an API running on your machine? flui dev creds and flui dev tunnel wire the credentials and open the tunnels you need.
Other helpers:
pnpm run api:generate # regenerate the typed API client from a running backend
pnpm run build # production buildStack: Angular standalone components, Signals for state, Spartan UI on TailwindCSS, strict TypeScript, and an API client generated from the Flui OpenAPI spec.
The dashboard is a pure client of the Flui API. It makes no provider calls of its own, keeps no server-side state and has no auth backend of its own: sign-in goes through the identity service that runs inside your Flui installation.
Flui is in alpha. The dashboard is used every day, but the surface is large: expect the interface to keep changing as the API settles.
Issues and pull requests are welcome. For larger changes, open an issue first. Bugs that are not about the interface go to flui-core.