We're in closed beta. Sign up for early access — founding pricing locks in at signup.Sign up for early access
Enterprise
Your identity provider stays the source of truth for who can log in. Configure SAML or OIDC SSO yourself from your organization settings.
SCIM 2.0 user and group provisioning — create, update, deactivate users, and map groups to roles. Generate your SCIM token from your organization settings and connect your IdP yourself; no ticket to our team required.
SSO, SCIM, membership, and repository-governance changes are all written to your org’s audit log, with an export endpoint and an optional webhook to your own SIEM.
Required approvals, CODEOWNERS enforcement, stale-approval dismissal, and required status checks — configurable per repository, not bolted on after the fact.
Owner, Admin, Manager, Member, Billing Admin, and Auditor roles, each scoped to a fine-grained permission set spanning membership, SSO, billing, and repository access. Auditor is read-only — access to the audit log and organization data, without the ability to change anything.
Not mined for AI training data, not sold to third parties, not scanned beyond what keeping the service running requires. Every organization, every plan.
The same task→branch→commit→PR mechanism every plan gets, with required approvals and status checks actually gating the merge button, and the result landing in your audit log automatically.
Your identity provider authenticates the login — no separate UnityFreak password to manage.
The same task→branch→commit link every plan gets — traceable from board to code.
Ownership rules resolve automatically; the right reviewers are requested without anyone asking by hand.
The merge button stays disabled until required approvals land and required status checks pass — enforced, not just suggested.
Once it merges, the event lands in your organization’s audit log — reviewable, exportable, and streamable to your SIEM.
Import any repository by URL — full Git history and LFS objects come across in one step. Point your CI and local clones at the new remote and keep working; issues, pull requests, and branch rules don't migrate and need to be recreated.
Tell us about your identity provider, your team size, and your governance requirements — we'll walk you through setup.