What’s in the package: a running, branded software product on your own Cloud Run, GitHub repos, and database — with sign-up, sign-in, invites, teams, roles, admin console, audit trail, and notifications already working on day one. Underneath it, the sovereign 4-layer architecture (Users, Companies, Workspaces, Modules) that every module you (or Cursor, or Claude, or Freshify) build next snaps into cleanly. Yours to own — no vendor in the middle, no per-seat tax. Every package ships with:
- Setup Wizard — CLI that provisions your environment, database connection, and Google Cloud services in under 30 minutes
- Branding Configurator — CLI that skins the platform with your name, colors, and logo
- Sample Data Seeder — log in on day one to a platform with demo Users, Companies, and Workspaces already populated
- Sovereign architecture, ready for AI — clean module boundaries and documented interfaces designed so AI-generated code doesn’t drift. Pair with the Sovereign AI Build Kit to add Cursor rules, agent instructions, and the module scaffolding prompt library.
- Architecture Documentation — README, deploy runbook, the 4-Layer Model, the SMI overview, and the canonical 20 Anti-Patterns your engineers (and Series A reviewers) can read against the code. The full SMI spec, conformance suite, and module template ship with the Sovereign AI Build Kit.
Scale profile
- Who you are in this
- The operator selling software to other Companies whose teams work in Workspaces — the unit that drives seat expansion and feature adoption
- Scales into millions
- Users invited into Workspaces (across all Companies)
- Scales into thousands
- Companies (your customers) and the Workspaces they spin up as teams form and split
- What matters most
- Unlimited Workspaces per Company, invite-based user expansion, and per-Workspace permissions that let plans, roles, and features change without a data-model rewrite
Build and add your own modules like:
- Subscriptions — plans, tiers, seats, term, renewal, upgrade and downgrade — sovereign module that owns subscription state, kept separate from the payment event so a failed charge does not corrupt plan state
- Transactions — invoices, payments, refunds, receipts — sovereign module for money movement, sibling to Subscriptions rather than fused into it
- Metering & Usage — track any usage dimension (seats, API calls, storage) and roll it up to the Subscriptions module
- Entitlements — decide what each plan can do; enforce it at the module level
- Self-serve Billing Portal — customer-facing page to change plan, view invoices, and update payment method — sits on top of Subscriptions and Transactions
- Feature Flags — ship features to some workspaces before others, from a UI
Vibe-code them yourself on the sovereign architecture, or have Freshify build them as Custom Modules →