Skip to main content

Module Catalog

Orkestra ships 8 core modules (always loaded) and an empty optional-addon catalog — per ADR-0006 the base is core-only. A fork adds its own verticals in-tree through the same Module seam the core uses. The table further down lists the verticals the core-only pivot removed; their archived orkestra-cc/orkestra-<name> repos are kept for forks to crib from.

Core modules

Always loaded. Topologically sorted by their Dependencies():

usernotificationtenantauthzauthnavigationloggingcompliance

See Core modules and the rest under that section. (compliance was re-homed from an addon back into core by ADR-0009.)

Archived verticals (fork crib material)

The base ships none of these. They are snapshots of the verticals the core-only pivot removed, preserved in public archive repos for a fork to crib from when rebuilding the equivalent in-tree.

VerticalDepends onArchived repo
billingdocumentsorkestra-cc/orkestra-billing
documentsorkestra-cc/orkestra-documents
companyorkestra-cc/orkestra-company
graphorkestra-cc/orkestra-graph
aimodelsorkestra-cc/orkestra-aimodels
raggraph, aimodelsorkestra-cc/orkestra-rag
agentsauth, aimodelsorkestra-cc/orkestra-agents
salesaimodelsorkestra-cc/orkestra-sales
subscriptionsorkestra-cc/orkestra-subscriptions
paymentsorkestra-cc/orkestra-payments
identitytenant, authzorkestra-cc/orkestra-identity
devauthorkestra-cc/orkestra-dev

:::note compliance moved to core The removed compliance addon is not in this list — ADR-0009 brought audit + GDPR DSR back into the always-loaded core. See compliance. :::

:::info Auto-synced (forks) A fork's addon pages are auto-generated from each addon's README.md at build time (and re-synced nightly). The base catalog is empty, so no addon pages are generated here. See the sync architecture. :::