Spin up a client project, credentials and workspace included
A private, local-only ops command center that turns a new client project into a credentialed DevContainer workspace in one wizard — then tracks its to-dos and runs local AI analysis on it. Built for a single operator running many client projects. Cloud service provisioning is mocked in the current MVP.
Key Features
Client and project name in, auto-generated slug, email alias, and 16-char password out. Service provisioning is mocked in the current MVP.
Secrets are written to an AES-256-GCM vault file, viewable masked with reveal and copy on the project page.
The local Claude CLI reads the linked app source and AppInsight data to report payment wiring, feature gaps, and suggested to-dos.
Priorities, categories and tags, nested subtasks, and AppInsight demand scores — fillable from the UI or a terminal script.
Why We Built This
Every new project started the same hour-long ritual
Starting a client project meant the same manual loop every time: invent a slug, make an email alias, generate a password, click through GitHub and Supabase and Vercel and AWS, then paste the credentials somewhere and hope you'd find them later. This collapses that into one wizard — name the client and project, pick services, review, create — and everything downstream is generated: encrypted credentials, a saved project record, and a ready DevContainer workspace. It stays local because it holds every key you own.
A new project meant slugs, an email alias, a password, and four service dashboards before a single line of code. The wizard does it in one pass and isolates any service that fails.
Credentials never touch the database — they're encrypted into a vault file with AES-256-GCM using a scrypt-derived key, and only non-secret metadata is stored alongside.
Each project gets a generated DevContainer workspace with devcontainer.json, MCP config, and .env — so the project row corresponds to something you can actually open and work in.