Pricing & plans

Plans and compute pricing

Every plan includes every module. Plans differ in compute credits, quotas, queue priority, and support — and every price, limit and seat rate below renders live from the billing catalog the server actually enforces.

How pricing works

You pay for throughput, not unlocks

Three rules govern the catalog. Each one is enforced in the backend, not just on this page.

No feature gates
Every plan ships every module

Every domain workspace, the full four-stage pipeline, TEA/LCA, physics workbenches, the REST API and the Python SDK are available on every tier. There is no route that checks your tier before unlocking a studio (backend/core/constants.py, USER_TIERS).

Throughput only
You pay for capacity, not unlocks

Tiers differ in monthly compute credits, jobs per hour, concurrency, dataset size, storage, queue priority, support and the free-tier dossier watermark. Nothing else changes between a free account and Enterprise.

Self-serve
Public prices, no sales call required

Free, Starter, Pro and Enterprise check out through Stripe from your browser, and this page renders the same catalog the server enforces. Dedicated single-tenant or on-premise deployments are not part of self-serve — those start with a conversation.

Why quotas exist.Limits mirror real infrastructure capacity (hosting, CPU, storage and the shared LLM budget), not artificial feature caps. That is also why Free is deliberately tight: full access, taste-sized throughput. The authoritative limits live in backend/core/constants.py and reach this page through GET /api/billing/plans.
Plans

Self-serve pricing, live from the catalog

Every name, price, limit and seat rate below renders from GET /api/billing/plans — the same source the server uses to enforce them. Cards list only what changes between tiers.

Best value — annual: pay 8 months, get 12 (33% off)
Every plan includes every module — you pay for throughput, not unlocks
All Domain Studios: Formulations, Polymers, Batteries, Alloys, Catalysis · Simplex Mixture DoE + Hansen (HSP) Solver & Blend Optimizer · Polymer QSPR & Copolymer Fox Modeler + 7 more included areas. Cards below list only what changes per tier: compute, quotas, priority & support.

Compare limits — the only things that change between plans

Paid plans raise only quotas, compute, priority, support and watermark — never gate a studio.

Limit (what actually differs)
Compute / month (credits)
Compute / week (credits cap)
Jobs / hour · concurrent
Dataset size · file · storage
Datasets · campaigns · copilot/mo
Support

Live numbers render from GET /api/billing/plans (backend/core/pricing.py + constants.py USER_TIERS). The monthly compute figure is the smaller of the grant and the monthly quota window — what you can actually spend, not a marketing ceiling. DEMO surrogates never bill on any tier. Seats are sold separately and appear on a plan's card only when the deployment has seat checkout configured; a seat carries reduced allowances and is never a full plan.

Self-serve Enterprise is shared managed capacity. It includes OIDC/Google sign-in, evidence-labelled results and self-serve onboarding, but not SAML/SCIM, uptime SLAs, dedicated single-tenant hosting or tax invoicing. On-premise / single-tenant deployment is a separate contact-sales engagement.
Compute credits

Estimating your monthly compute

One credit ≈ one second of medium-weight compute. Use the estimator to sanity-check a plan against seats, compute hours and one-time top-ups — display only; checkout is unchanged.

Monthly estimateunavailable
Loading catalog… Estimate only — checkout is unchanged.
Plan (Starter)$99.00
Seats (0 × $20.00)$0.00
Compute (~0 credits)—
Credit pack (one-time this month)$0.00
Estimated monthly total$99.00
How to read the estimate.The estimator prices extra compute hours at the cheapest recharge-pack rate, which is deliberately above the per-unit rate bundled inside a paid plan. It is a planning aid, not a quote — checkout prices always govern, and usage is metered from the platform's own records.
Academic & Student Program

Free access for university researchers, students & academic staff

Apply with your institution and an institutional email domain. Domains ending in .edu, .university, .ac, .gov or .mil — with or without a country suffix (for example .edu.qa or .ac.uk) — are approved automatically; everything else is reviewed by an administrator. Approved accounts are promoted to the Academic / Student tier (the Starter limit set, free) with extended compute, data and concurrency limits — no parallel plan to maintain.

Sign in to check your status or apply.
Billing FAQ

Questions people ask before they buy

Short answers, each traceable to the backend behavior or the Account & Limits docs.

What is a compute credit?
One credit ≈ one second of medium-weight compute (backend/core/credits.py). Engines meter the compute they actually consume, so a credit is a unit of real work — not a token you buy per click. Every plan includes a monthly credit allowance: that allowance is what you can spend each month, and each plan also has a weekly cap plus a per-hour spend cap so one runaway loop cannot drain the month at once.
Where do I see my compute allowance and weekly cap?
Each plan card and the compare table above show one monthly compute number per tier — the amount the backend actually enforces (the smaller of the monthly grant and the monthly quota window). The weekly cap renders next to it. Your own live usage is in Settings → Billing.
How does annual billing work?
Annual is billed once, up front, at 8× the monthly price: you pay for 8 months and get 12 — 33% off. Switching between monthly and annual is done from Settings → Billing; cancelling stops the next renewal and you keep access to your data and results.
Can I buy extra compute without changing plans?
Yes — credit packs are one-time overflow top-ups that raise the current month's allowance by the pack size (they do not recur). They are priced above the per-credit rate inside a paid plan, so a subscription stays the better deal at sustained volume.
What happens when I hit a limit?
Running out of credits returns HTTP 402 (payment required) — top up a pack or upgrade. Hitting a quota or rate window returns HTTP 429 with the specific window named and when it resets (jobs per hour, weekly credits, daily wall-clock, concurrency). Failed engine runs bill only the seconds they actually consumed; DEMO-labelled surrogates never bill on any tier.
What do team seats include?
Seats add named teammates to a project at a per-seat monthly rate (live on each plan card). A seat is not a full plan: seat members get reduced allowances, and the project's compute still comes from the owner's plan and credit balance. Seats are available on the plans that show a seat rate.
What does Enterprise self-serve include — and not include?
Self-serve Enterprise is the fourth plan above on shared managed capacity: highest queue priority, OIDC/Google sign-in, evidence-labelled results and self-serve onboarding. It does not include SAML/SCIM, uptime SLAs, dedicated single-tenant hosting or tax invoicing. On-premise and single-tenant deployment is a separate contact-sales engagement.
What does every plan include?
Every plan — including Free — ships the whole platform: all Domain Studios, the full four-stage pipeline, physics workbenches, active learning, the REST API and the Python SDK. Tiers differ only in compute allowance, quotas, queue priority, support and the free-tier dossier watermark.
Do failed or demo runs consume credits?
No. DEMO-labelled surrogate runs never bill on any tier. Failed real engine runs are billed only for the elapsed seconds they actually consumed before failing, through the same credit ledger.
Do I need to add a card for a free account?
When verification is enabled on a deployment, new accounts start fully usable and can add a $0 Stripe card check after the grace period (default 7 days) to keep creating new work. No money moves; some card networks place a brief $0–$1 authorization hold that auto-releases. Anyone on a paid plan is already verified by billing, and the whole gate is inert on deployments without Stripe configured.
  • Settings → Billing — shows your plan, usage and the same catalog this page renders.
  • Account & Limits docs — document what is limited, where to see your numbers and fair-use rules.
  • Annual billing — is charged once at checkout, at 8× the monthly price — pay for 8 months, get 12.

Start free, upgrade self-serve — or talk to us about single-tenant

Free through Enterprise check out from this page on shared managed capacity. Dedicated single-tenant or on-premise deployment, SAML/SCIM, uptime SLAs and bespoke integrations are not part of self-serve — they are scoped with our team.