Enterprise
Most of your merged code is already written by an agent.
The question your board will ask is not how fast you write it. It is who approved it, against what, and whether you can show them.
Identity & access
SSOSAML 2.0 / OIDC · Okta, Entra, Google, Ping
ProvisioningSCIM 2.0 with group push and attribute mapping
RolesOwner, Approver, Builder, Operator + Viewer. Custom roles from templates.
Domain captureDNS TXT verification. Off until you turn it on. Never grants an administering role.
Evidence
Audit logAppend-only, hash-chained, actor-named — including refusals
StreamingSplunk, Datadog, Elastic, or any HTTPS+JSON endpoint
Retention365 days default, up to 7 years
Approval recordActor, timestamp, comment, and the exact artifact hash approved
Fits the estate you have
Adoption is four ports and a pull request. Nothing is rewritten to accommodate us.
ServiceNowJiraSalesforceWorkdayKubernetesArgo CDGitHub AppHashiCorp VaultGCP Secret ManagerMCP
What a pilot looks like
Four weeks, one workspace, one real service.
Week 1Connect source control and a model chain. Run one build to STAGED and stop there.
Week 2Your security team reads the generated repository against their own checklist, not ours.
Week 3A second build on a service that already exists, to see what the reuse map actually matches.
Week 4Decision. If it is no, you keep the repositories — they build and run with Rathvan removed.