Enterprise
Enterprise
The open core is complete. Enterprise adds the org layer.
Section titled “The open core is complete. Enterprise adds the org layer.”First, the part that matters to most readers: the open-source project is useful on its own, and stays that way. The entire single-team verification loop — generation for all six runtimes, execution, grounding validation, self-healing, truthful reports, single-project traceability, local LLMs, per-project RBAC — is Apache-2.0 and will never be metered or crippled. That boundary is written down in ee/README.md and enforced in code review.
The commercial edition exists for what organizations need across teams:
Organizations & governance
An organization/team entity, a hosted control plane, and centralized management across many projects and teams.
SSO / SAML / SCIM
Enterprise identity-provider integration and automated user lifecycle management.
Audit trails & compliance
Real, tamper-evident audit trails and compliance evidence exports — the same truthfulness discipline, at audit grade.
Cross-project analytics
Cross-run and cross-project quality analytics, and fleet management for many ARTA deployments.
Advanced integrations
Jira at scale and test-management-suite synchronization.
Managed AI
ARTA Intelligence (fine-tuned generation models) and managed LLM inference for teams that don’t want to run their own.
Where the line is drawn — in code
Section titled “Where the line is drawn — in code”The seam is
src/api/entitlements.py:
the open core ships an allow-everything no-op; commercial editions install
their own implementation. Contributions that move local-loop features behind
that seam are rejected by policy — so the boundary can’t quietly drift.
Talk to us
Section titled “Talk to us”The commercial edition is early. If your organization needs the org layer — or wants to shape it — open a conversation: