1
Stable REST contract
Frontend and backend meet at a versioned /api/v1 boundary you can implement in any language.
Project Launchpad
Skip the scaffolding. Ship the product.
Auth, roles, console-driven content, localization and billing come wired together behind a stable REST boundary. Your team starts at the finish line of week three.
- Preview equals production
- One field spec, two runtimes
- Roles enforced on both ends
Hero v2 Β· Spotlight layout
Trusted by teams that ship weekly
NorthwindFlowactsVorlaUpliftlyDrfans
Built for evolution, not for the demo
Every capability is optional. The boundary never moves.
2
Console-driven pages
Editors compose pages from typed blocks; the same renderer serves preview and production.
3
Localization as a pipeline
Structure follows the base locale automatically. Copy is translated field by field, protected content intact.
4
Auth and roles built in
Hashed credentials, HTTP-only cookies, CSRF guards and role-based route protection on server and client.
5
Billing that fits
Subscriptions, one-off packs and credit balances share one entitlement model.
6
Observable from day one
Structured logs, audit trails and health endpoints are part of the template, not an afterthought.
What teams measure after switching
π
9 days
Time to first release
π
3+
Locales per site
π§©
38
Typed blocks
β‘
99.9%
Uptime target
Live in three steps
- 1
Register the project
Create it in the Console and configure the Admin and Content integrations.
- 2
Expose three endpoints
Manifest, preview and revalidate. Everything else is derived from your field specs.
- 3
Compose and publish
Drag blocks, fill in copy, publish to test, then promote to production with one click.
What customers say
β
β
β
β
β
βClear boundaries meant almost zero changes to plug in our existing backend.β
Wei Zhang
CTO, Northwind Labs
β
β
β
β
β
βPreview equals production. We have not seen a style drift since.β
Na Li
Frontend Lead, Flowacts
β
β
β
β
β
βVersioned components gave us guard rails; production has been boring, in the best way.β
Qiang Wang
Architect, Vorla
Frequently asked questions
Can I bring my own backend?+
Yes. Projects collaborate through the stable /api/v1 REST boundary, so the backend can be written in any language.
How do components evolve without breaking live pages?+
Breaking changes ship as a new version. Old renderers stay available and the platform gates conflicts by structure hash.
Is preview identical to production?+
Identical. Preview and production share one versioned renderer, byte for byte.
How is billing handled?+
Launchpad ships a credit-based entitlement model that supports subscriptions, one-off packs and usage metering out of the box.
Ready to launch your next project?
Start from clear architectural boundaries and keep them as you grow.
Talk to us