Ship the product, not the plumbing
Accounts, teams, billing and an admin console are already built and already tested. Start where the interesting work is.
What you start with
Accounts and teams
Sign-up, sessions, two-factor authentication, invitations and per-organization roles, isolated by tenant from the first query.
Subscriptions that reconcile
Plans, trials, upgrades and dunning, with webhook handling that stays correct when the same event arrives twice.
Operable from day one
Structured logs, metrics, audit trails and runbooks, so the first incident is something you read about rather than guess at.
Questions people ask first
- Is this a framework or a starting point?
- A starting point. You get the repository and you own every line in it — the modules are ordinary code you can read, change or delete, and nothing calls home at runtime.
- Can I remove the parts I do not need?
- Yes. Each optional module is one switch in one configuration file, and turning it off takes its routes, its database tables and its interface with it — not just the menu entry that led there.
- What is it built on?
- A FastAPI and PostgreSQL backend, a React and TypeScript web app, and a shared component and translation layer that both of them read from. No wrapper you cannot open.
- Do I need a card to start?
- No. The free plan asks for no payment details, and you only see a checkout when you choose a paid plan.