Enterprise
Enterprise ORGN — VPC and air-gap deployment, dedicated seats, audit workflows. Sales-assisted onboarding with FAR 9.5 OCI positioning for federal teams.
ORGN Enterprise is for organizations that need verifiable confidentiality at procurement scale — dedicated capacity, network isolation, fine-grained access control, and sales-assisted deployment. Self-serve pay-as-you-go covers evaluation; Enterprise covers production in regulated environments.
Pricing summary: $2,150 per seat / month, including 400 agent run hours per seat per month. Full detail on Pricing.
What Enterprise includes
Beyond pay-as-you-go credits, Enterprise typically adds:
| Capability | Description |
|---|---|
| VPC deployment | ORGN stack deployed inside your cloud account or dedicated network boundary |
| Air-gap options | Disconnected or highly restricted networks — sales-assisted architecture, not self-serve toggle |
| Seat-based capacity | Agent run hours bundled per seat with overage handling in contract |
| Access control | Fine-grained roles, team policies, audit-friendly admin workflows |
| Dedicated support | Priority channel for deployment, incident, and compliance questions — see Support |
| SLAs | Uptime and response commitments defined in contract |
The same four-layer stack applies: CDE, Studio, Gateway, and Scanner. Enterprise changes where it runs and who administers it — not the trust primitives. See Stack overview.
Deployment models
VPC (virtual private cloud)
Most Enterprise customers start with VPC deployment: ORGN components run in an isolated network you control (AWS, GCP, Azure, or on-prem compatible with TDX infrastructure). Your data plane stays inside your boundary; control-plane metadata policies are defined during onboarding.
VPC is sales-assisted. Engagements include architecture review, identity federation options, and egress policy alignment.
Air-gap
Air-gapped deployments target environments where outbound internet is prohibited or severely limited — classified programs, high-side networks, or strict data-sovereignty regimes.
Air-gap requires custom artifact delivery, offline attestation verification workflows, and often dedicated model routing. It is not available from the public signup flow. Expect a design-partner or pilot phase before production cutover.
Air-gap and VPC are related but not identical. VPC can still reach managed inference providers under controlled egress; air-gap may require bring-your-own-model or fully offline inference paths negotiated during sales.
Trust and compliance evidence
Enterprise buyers evaluate ORGN on evidence, not marketing claims. The canonical security narrative — TEE vs ZDR, data boundaries, shared responsibility — lives in one place:
Use that page in security questionnaires. Product-specific boundaries:
Export attestation artifacts from Scanner for compliance archives. Code vulnerability findings come from Studio code security — a different product from Scanner.
Federal procurement and OCI (FAR 9.5)
Many federal contractors evaluate AI development tools under FAR Subpart 9.5 — Organizational Conflicts of Interest (OCI). Using a vendor whose parent company competes on the same contract — or holds unrelated financial interests in the procurement — can create compliance exposure.
ORGN is positioned as an OCI-conscious alternative for teams who cannot use policy-trust tools tied to hyperscaler or model-vendor ecosystems on sensitive government work. The trust differentiation is cryptographic verification (TEE attestation, Trust Domain isolation) rather than Terms-of-Service promises alone.
Legal disclaimer: ORGN documentation describes product architecture and common procurement considerations. It is not legal advice, not a certification, and not a determination of OCI compliance for your contract. Your contracting officer, counsel, and security authority must evaluate fit for your specific solicitation, agency, and prime/sub relationship. ORGN does not warrant compliance with FAR 9.5 or any agency supplement for your program.
Documented precedent in the market includes public scrutiny when widely used AI IDEs create perceived conflicts when their vendors also bid on adjacent government work. Your compliance team should map ORGN's deployment model (especially VPC/air-gap) to your contract's OCI mitigation plan.
Identity and teams at Enterprise scale
- SSO: id-orgn PKCE across products; enterprise IdP federation available during onboarding — SSO
- Teams: Org structure, invitations, usage — Teams
- GitHub: Identity via Sign in with GitHub at id-orgn; repository access via the ORGN GitHub App — Teams — GitHub integration
How to engage
Enterprise is sales-assisted. Typical path:
- Evaluate trust model and Scanner verification on pay-as-you-go (Choose your path — Compliance)
- Security review with architecture and data-boundary docs (Trust model)
- Contact ORGN for VPC/air-gap scoping, seat count, and contract — Support
- Pilot in VPC or designated environment before production rollout
Related pages
- Pricing — seat economics and pay-as-you-go comparison
- Trust model — canonical "not through policy. Through math."
- Glossary — Trust Domain, Scanner vs code security
- Support — contact channels