Welcome to Orkestra
Orkestra is the SaaS plumbing every product rebuilds — users, auth, RBAC, multi-tenancy, navigation, logging — already done.
Eight core modules (user, auth, authz, tenant, notification, navigation, logging, compliance) supply the baseline on day one. Per ADR-0006 Orkestra is a core-only base — it ships no addons. A fork builds its own verticals (invoicing, payments, subscriptions, RAG, AI agents, documents, identity, …) on top, against the in-tree SDK contract, using the same Module seam the core is built on and toggling them at /admin/modules.
Where to next
- Getting Started — boot Orkestra locally in under five minutes.
- Architecture — the two-tier tenancy model and module lifecycle.
- Operating Orkestra — deployment, module configuration, SMTP/OAuth.
- Module Catalog — the eight core modules, what each does and depends on, plus the seam for a fork's optional modules.
- SDK Reference — the
Moduleinterface,ServiceRegistry, building an addon. - ADRs — architectural decisions that shape the platform.
Who this is for
These docs are for operators self-hosting Orkestra and developers building on the SDK or contributing addons. End-customer documentation (Tier-2 client onboarding) lives elsewhere.
Tech stack at a glance
| Layer | Technology |
|---|---|
| Backend | Go 1.25, Huma v2 (OpenAPI-first), 8 core modules (core-only base) |
| Frontend | React 19, TypeScript 5.9, Vite 7 |
| Mobile | Flutter 3.35+ |
| Database | MongoDB 8.0, Redis 8.2 |
| Auth | Email/password (argon2id) + OAuth 2.1, RS256 JWT, 6-role RBAC |
:::info Status
These docs are a work in progress. Sections marked 🚧 Draft still need fleshing out — PRs welcome at orkestra-cc/orkestra-docs.
:::