The Flui control plane and dashboard are AGPL v3, and the manifest specification is Apache 2.0. Nothing is held back for a paid tier — the paid tiers sell support, not features, because gating features on an AGPL product would be neither enforceable nor honest.
Alongside them: the bootstrap scripts, the mail service, and framework starter templates for Next.js, Nuxt, Angular, SvelteKit, NestJS, Spring Boot, Django, FastAPI, ASP.NET Core, Vue, Astro and VitePress — all at github.com/flui-cloud.
app.flui.cloud — the service that builds a cluster on your cloud account in about seven minutes — is closed. It is also the narrowest possible thing: a funnel, not a control plane, not a fleet manager, not a mirror of your installation. Each of those was considered and left out.
No code is copied in either direction. It drives the published Flui CLI as a subprocess, which means every fix the managed path needs has to land upstream in flui-core, where self-hosted users get it too. The boundary is what keeps that true.
And it keeps nothing. No SSH authority, no kubeconfig, no provider credentials at rest. The bootstrap key is injected through the provider's own API, used, then deleted from the provider and from the machine. The cluster ends with SSH dormant, and the adoption token is never stored — not even hashed. It cannot mint access to a cluster it built, because it kept nothing that would let it.
