Unified Platform
Choose how SoarStarter templates deploy alone or work together through one stable platform contract.
SoarStarter supports two deployment models. Pick one before installation so identity, data, subscriptions, and storage all come from a deliberate backend preset.
Product model
| Term | Exact meaning |
|---|---|
| Standalone deployment | One template operates independently and does not share identity or business data with another SoarStarter client. |
| Unified deployment | Multiple surfaces share identity, data, subscription entitlement, and the Soar App API. |
| Backend implementation | The concrete backend a client connects to: Supabase or a conforming Soar App API host. |
| Bundle | A commercial purchase containing templates. It does not require Unified deployment. |
A Bundle and a Unified deployment answer different questions. You may buy the Bundle and deploy every template independently.
Roles
- Unified Platform Hosts: Next.js, Nuxt, and TanStack Start run Better Auth, the database, shared services, and
/api/app/v1. - Unified Clients: Swift, Kotlin, Expo, Electron, and Tauri connect to any host that conforms to the frozen v1 contracts.
The hosts share an external contract, not an internal framework architecture. Clients select a backend at build or deployment time; the choice is not exposed as an end-user setting and never silently falls back.