For Developers
Built for developers
who ship.
Standard React. Automatic multi-tenancy. Database isolation by default. Build modules that inherit the entire platform — auth, billing, and styling — without configuration.
Module Architecture
Two layers. One module.
Every module you build automatically renders in two contexts: the builder's backoffice dashboard and the end-user's public experience. You write one module — the platform handles the routing.
Builder Backoffice
Admin controls, configuration, analytics
End-User Experience
Public pages, customer portals, checkouts
Security Model
Isolation at every layer.
Multi-tenancy is not an afterthought. It is enforced at the edge, the application layer, and the database layer simultaneously.
Edge Resolution
Every request is resolved to a tenant at the edge in under 10ms. Custom domains and subdomains are mapped to project contexts before your application code runs.
Application Context
The tenant context is injected into every server component automatically. Your module code always runs within a scoped context — no manual tenant filtering required.
Database Isolation
Row-level security is enforced at the database layer. The tenant context is set before your query executes. It is physically impossible to read another tenant's data.
Extensibility
Standard React. Full platform power.
Modules are React server components. If you know React, you know how to build for BusinessOS. The platform provides the routing, database wrappers, auth, and billing — you write the business logic.
React Server Components
Write standard RSC. No proprietary framework, no lock-in. Your module code is portable React.
Automatic Auth Inheritance
Your module inherits the platform's auth system. No OAuth setup, no session management, no token handling.
Native Billing Integration
Payment processing, entitlement gating, and subscription management are available as platform APIs.
Shared Design System
Your module inherits the project's CSS theme automatically. Build UI that matches the operator's brand without extra work.
Read the Documentation.
Architecture decisions, API references, module development guides, and security documentation — all in one place.
Open Documentation