Community vs Enterprise
Compare the OrkStage Community edition (AGPL-3.0) with the commercial Enterprise edition area by area, with the status of each Enterprise item.
Community is complete. It includes templates, multicloud placement, tenant limits, policies and cost, deployments, health, incidents, status pages, notifications, the audit log, API keys, webhooks, CI intake, IaC import and the CLI. Enterprise adds features for organizational scale and compliance.
Enterprise items marked planned are on the roadmap but not built yet.
| Area | Community (AGPL-3.0) | Enterprise |
|---|---|---|
| Provisioning | Templates and the visual builder; AWS, Azure, Google Cloud, OCI, DigitalOcean, Vultr, CoreWeave and Magalu Cloud through OpenTofu; Vercel, Render and Supabase through their APIs; triggers; DAG with retries; provider plans before apply; drift scans | Policy packs (rule sets in the style of CIS and SOC 2) planned; custom policy authoring planned; cost budgets per team planned |
| Multicloud | Placement per resource; connectivity strategy for links between clouds | Provisioning of private connectivity (VPN, interconnect) planned |
| Governance | 7 predefined roles; approvals for high risk production changes; audit log that only accepts inserts | Audit log export (NDJSON, CSV); custom roles and detailed permissions planned; approvals with several steps and change windows planned; audit retention policies and SIEM streaming planned |
| Identity | Development login (local); OIDC with Microsoft Entra ID, Google and GitLab through configuration | SAML 2.0 SSO planned; SCIM provisioning planned; enforced SSO and MFA, session policies planned |
| Organizations | One organization, many tenants | Multiple organizations, delegated administration planned; status pages with your own branding and custom status domains planned |
| Integrations | API keys, webhooks, CI intake, IaC import, ork CLI (Preview) | Change management with ServiceNow or Jira planned; PagerDuty and Opsgenie planned |
| Observability | Health, incidents, private status pages, logs and metrics through adapters | Metrics retention over long periods, SLO management, incident analytics planned |
| Support | Community (GitHub Discussions) | Support backed by an SLA, security advisories before public disclosure planned |
One question is still open: whether the provider adapters now in preview belong to Community or Enterprise. The current recommendation is Community, so that multicloud stays in the open core.
Editions
| Edition | For | Model |
|---|---|---|
| Community | Any size, on your own infrastructure | Free, AGPL-3.0 |
| Enterprise (on your own infrastructure) | Regulated or larger organizations | Annual subscription, support included |
| OrkStage Cloud | Teams that want us to host it | Planned |
Pricing is not published yet. Contact us.
Enterprise overview
OrkStage Enterprise adds identity, governance and compliance features to the open source core. Same code and images, turned on by an offline license key.
License
How OrkStage is licensed: the AGPL-3.0 core, the Enterprise License for the private Enterprise source, other repositories, contributions and trademarks.