Vessel Ledger
Demo ReadyPersonal finance / records
A calm ledger for obligations and recurring records.
Provision tenant APIs, push migrations, inspect schemas, verify backups, and give coding agents structured project context through CLI, dashboard, and MCP.
Showcase Console
9 apps · one foundation · live and demo-ready
Featured
Personal finance / records
A calm ledger for obligations and recurring records.
Home / objects
Persistent atmosphere context for conscious home-building.
All apps
Mail / AI
Inbox maintenance for real life.
Commerce / catalog
An editorial marketplace for independent makers.
Brewing / recipes
A brewing project for repeatable, classic-quality beer.
Language / texts
Read the Greek world from the source.
Home / coordination
Shared-space coordination, made calm.
Home / operations
A home operations dashboard for the long-term resident.
Platform
Infrastructure for small, serious web projects.
Demo philosophy
Flux apps can expose a curated demo account with fake data, constrained actions, and no private secrets. The point is to let people understand the product by using it — including the Flux control plane itself and the demo-ready apps in the showcase above.
Example demo-ready apps: Vessel Ledger · Habitat
Agent access
Flux is a self-hosted Postgres backend and control plane with three interfaces. MCP exposes project state, schema inspection, backups, migration status, project doctor, activity, and FLUX.md context to AI tools through structured, permissioned project context — without replacing the dashboard or CLI.
For humans
Browse projects, inspect schemas, manage backups, run project doctor, and sync FLUX.md briefs in the browser.
For operators
Provision stacks, push migrations, and automate backup-aware workflows from the terminal — the same control plane MCP calls.
For AI coding agents
Cursor, Codex, Claude, and other MCP clients get structured, capability-scoped project context — inspect and plan by default.
MCP workflow
Example prompts
“Inspect this project's schema and summarize missing tables.”
“Check backup trust before applying this migration.”
“Generate or refresh FLUX.md for this app.”
“Run project doctor and explain what blocks deploy.”
Read-only and context tools are the default MCP posture. Migration apply requires scoped capabilities, restore-verified backup trust, and explicit confirmation — destructive lifecycle operations stay blocked. MCP never returns raw database passwords, pooled admin credentials, or long-lived JWT secrets.
The foundation
Every app starts with durable relational storage.
Plain SQL workflows for creating and evolving app schemas.
Backups are treated as useful only after they can be restored.
PostgREST-style APIs without hand-written CRUD servers.
Expose real interfaces with seeded data and locked-down permissions.
Start pooled, move dedicated when the app needs its own house.
Philosophy
A foundry for small durable apps.
Flux is the shared foundation underneath the apps above: Postgres, migrations, backups, JWT-aware APIs, demo mode, and deployment standards.
It is not trying to replace your database tools. It gives each app a reliable operating base.
Build the next one
$ curl -sL https://flux.vsl-base.com/install | bash$ flux create my-app