01
Compose the platform from modules
The shared layer exposes contracts and runtime surfaces. The tenant decides what the public experience looks like.
Modular platform
Build a tenant-owned public experience.
This generic fallback proves the shared platform can render safely, while real brand, copy, atoms, molecules, and motion come from the client repository.
How it works
Client-owned surfaces
Start with a clear narrative, then replace the neutral content with the language and proof that belong to your product.
02
Publish tenant-owned pricing
Pricing tiers belong in the client manifest or template, where each tenant can define its own market, offer, and packaging.
Optional architecture detail
Module footprint
A compact, explicitly published view of the platform capabilities mounted for this tenant.
08
modules
35
entities
governance1.0.0
Audit
2 entities · 7 features
security2.0.0
Auth
8 entities · 7 features
governance0.1.0
Change
1 entities · 1 features
core1.0.0
Eventing
1 entities · 2 features
communication1.0.0
Notification
10 entities · 6 features
core1.0.0
Tenant
8 entities · 5 features
Show remaining modules (2)
localization1.0.0
Translation
1 entities · 1 features
core2.0.0
User
4 entities · 4 features
Testimonials
What our members say about us
This content is deliberately generic so tenant-specific public logic stays outside the platform package.
Platform boundary
Shared fallback
Plans
Replace these neutral placeholders from the client overlay.
Most popular
Starter
Local proof of concept · +Taxes excluded
Custom/mo
- Platform runtime: Shared renderer
- Tenant design: Module catalog
Compare features
See what each plan includes.
| Features | Starter |
|---|---|
| Platform runtime | Shared renderer |
| Tenant design | Module catalog |
Contact
Provide tenant contact details in the client overlay.
Contact details
Use the details below or copy them directly to your clipboard.