Build the product. The platform is already there.
Every FormaBase product starts with sign-in, billing, attribution, email and the brand kit already wired in. Creators write the features; the platform handles everything a business needs around them.
Every product uses the same stack, so any product can be maintained by anyone at FormaBase and every product looks and behaves like part of one family.
| Layer | What products use |
|---|---|
| Application | Next.js (App Router), React and TypeScript in strict mode |
| Interface | The FormaBase design system: tokens, components, motion and layout |
| Data | An isolated Postgres database for the product's own features |
| Platform services | The FormaBase SDK for sign-in, access, checkout, email and events |
| Delivery | Its own repository and deployment, with a preview for every change |
The SDK
In progressProducts reach the Core through one SDK and one key scoped to that product. The SDK covers sign-in, access checks, checkout, transactional email and product events, and carries Affiliate attribution through checkout without the product doing anything.
import { formabase } from "@formabase/sdk";
// Who is signed in, and do they have access to this product?
const session = await formabase.auth.getSession();
const access = await formabase.entitlements.check(session.customerId);
if (!access.active) {
// Checkout runs on the Core. The product never sees a payment key,
// and Affiliate attribution is carried through automatically.
return formabase.checkout.redirect({ plan: "pro-monthly" });
}
// Transactional email goes through the Core as well.
await formabase.email.send({ template: "report-ready", to: session.customerId });The brand kit
LiveProducts are built from the same design system as this site, so the whole catalog looks and feels consistent. Colors, type sizes and spacing come only from FormaBase tokens; automated checks reject hard-coded colors and sizes. New visual patterns are added to the design system, not inside a product.
The kit is versioned. Each product pins a version, so updates apply going forward and never change a live product unexpectedly. Explore it in the design system.
| Practice | Detail | Status |
|---|---|---|
| Pull requests | Every change ships as a pull request, and production deploys only from reviewed merges | Live |
| Automated checks | Formatting, linting, type checks, tests and a production build on every change | Live |
| Preview deployments | Every change gets its own private preview to review before it ships | Live |
| Product template | A starter repository with sign-in, billing, attribution and the brand kit pre-wired | Planned |
| Scoped access | Creators work in their assigned repository and development resources only | Planned |
| Test-mode keys | Development uses test-mode keys scoped to the product, so nothing copied has production value | Planned |
AI-assisted development is first-class: products are built with modern coding assistants, and Creators review, test and take responsibility for the code they submit.
Before a product launches, and on every update after that, it must:
- Disclose every external endpoint, package, model, build script and outside service it uses
- Use only approved third-party services; new ones are requested through the portal and provisioned by FormaBase
- Contain no obfuscated code, hidden dependencies, backdoors or undisclosed tracking
- Run every customer charge through the FormaBase checkout
- Keep live customer data and production secrets out of development tools, tests and AI prompts
- Pass automated screening, and human approval for first releases
When a product is ready, the Creator hands over a complete, operable package:
| Item | Why |
|---|---|
| Source code in the FormaBase repository | FormaBase owns and operates the product from launch |
| Build instructions and tests | Anyone can rebuild and verify it |
| Third-party inventory | Every package, model and service is known and licensed |
| Data schema | The product's data is understood and portable |
| Cost estimates | Running costs are known before launch |
| Deployment and rollback instructions | Releases are safe and reversible |
| Hand-off notes | Support and operations can take over cleanly |
After hand-off, FormaBase operates the product: support, fixes and maintenance. The Creator moves on to the next idea while their royalty runs.