Pricing
ORGN pricing — pay-as-you-go credits with 10% markup, enterprise seats at $2,150/month. Canonical rates from orgn.com; in-app billing may lag.
ORGN uses prepaid credits for pay-as-you-go usage and per-seat enterprise billing for regulated teams that need dedicated capacity, VPC deployment, and sales-assisted onboarding.
Canonical pricing lives on orgn.com/pricing. This page summarizes what procurement and engineering leads need from documentation. If numbers here and in the product disagree, orgn.com wins.
In-app billing cards (Studio team settings, Gateway console) may show legacy plan tiers or amounts that have not caught up to the marketing site yet. Treat orgn.com/pricing as source of truth until product UI is aligned.
Pay as you go
| Item | Detail |
|---|---|
| Starting credits | $20 prepaid to begin |
| Billing model | Usage-based — you pay for compute, inference, and agent activity consumed |
| Markup | 10% on underlying provider cost |
| Credit expiry | Credits do not expire |
| Team members | Unlimited on the pay-as-you-go plan |
Credits fund ORGN Studio workspaces, agent worktrees, Gateway inference (when billed through your team), and related platform usage. Top up from team billing settings or redeem voucher codes when available.
What consumes credits
Typical consumption includes:
- Confidential workspace runtime (CPU/memory hours in TDX sandboxes)
- Agent runs and chat sessions in Studio or CDE-connected projects
- Gateway inference routed through team-billed paths (token usage at model rates plus markup)
See Teams — Billing for balance, usage history, and team-level spend visibility.
Enterprise
| Item | Detail |
|---|---|
| Price | $2,150 per seat / month |
| Included capacity | 400 agent run hours per seat per month |
| Billing basis | Agent run hours (not just seat login) |
| Procurement | Sales-assisted — contact via Enterprise |
Enterprise adds VPC or air-gapped deployment options, fine-grained access controls, audit workflows, SLAs, and design-partner onboarding. It is aimed at finance, healthcare, defense primes, and other teams where verifiable confidentiality is a procurement requirement.
See Trust model for the security narrative enterprise buyers evaluate alongside price.
Comparing plans
| Pay as you go | Enterprise | |
|---|---|---|
| Best for | Individual developers, startups, eval teams | Regulated orgs, government contractors, VPC requirements |
| Commitment | None — top up credits as needed | Annual contract (typical) |
| Deployment | ORGN-hosted multi-tenant | VPC, air-gap, or dedicated options (sales-assisted) |
| Support | Standard (see Support) | Dedicated support channel |
| Trust evidence | TEE attestation + Scanner audit (all plans) | Same stack + export-friendly compliance workflows |
Gateway inference billing
Gateway API usage can be metered separately depending on how your organization provisions keys:
- Console-managed keys — usage appears in Gateway console team billing and may draw from the same credit balance as Studio when linked to an ORGN team
- Enterprise deployments — inference may be bundled into seat capacity or contracted separately during sales onboarding
Model list and per-token economics vary by provider (TEE vs ZDR). See Gateway models for execution types; pricing follows provider cost plus the platform markup on pay-as-you-go plans.
Related pages
- Teams — Billing & usage — credit balance, plans UI, activity logs
- Enterprise — VPC, air-gap, FAR/OCI positioning
- Trust model — what you are paying to verify, not just use
- Support — billing questions and account help
Trust Model
How ORGN enforces confidentiality through hardware isolation, cryptographic attestation, and explicit data boundaries — not vendor policy alone.
Enterprise
Enterprise ORGN — VPC and air-gap deployment, dedicated seats, audit workflows. Sales-assisted onboarding with FAR 9.5 OCI positioning for federal teams.