Pay for decisions, not seats.
One unit across the whole platform. One consumption catalog. Volume discounts on the curve. Deployment is a multiplier, not a separate SKU. Every line item on the bill ties back to a published NC cost — the same worksheet your FP&A team will build anyway.
Every action. What it costs in credits. What you'd typically run.
Published NC costs per action, typical monthly volume for a Fortune 500 carrier, and the resulting monthly NC draw. Your final dollar figure depends on commit size and deployment — a 30-min call lands it. This is the worksheet, not a summary.
The catalog is the same for every customer. If your NC draw moves, it's because your volume moved — not because a sales conversation moved.
One catalog, four tiers, no custom logos.
Discounts off the standard NC rate apply automatically as monthly volume crosses each tier. Every customer on the same tier gets the same discount. The curve is published because consumption is the contract — the final rate is set on the commercial call, against your actual volume.
Deployment is a multiplier, not a separate product.
Same platform, same NC catalog, one multiplier on your credit draw. Move from pilot to customer-VPC to on-prem without re-pricing the catalog or renegotiating the contract. The multiplier is the only thing that changes.
Customer-VPC is where most Fortune 500 deployments land — it's the architecture behind our 17-day legal reviews. See the Architecture page for the full boundary manifest.
What a real month looks like on the ledger.
Three composite deployments drawn from live customers, redacted. Each breakdown shows the consumption line items, monthly NC draw, and the deployment multiplier applied. Your actual commit and rate come from a commercial call — this is the worksheet, not a brochure.
Toggle deployment from the Tweaks panel to see each scenario re-draw live in credits.
What never costs a credit.
Security posture, identity, audit, and handoff are part of the platform — not a tier upsell. Consuming a credit for any of these would mean we think it's optional. We don't.
The commercial terms your procurement team will ask for first.
Annual commits unlock tier 3+ pricing and lock the rate for the term. Quarterly true-ups are non-punitive — unused NC roll within the commit year, overages bill at the same tier rate. Multi-year commits bank one extra tier.
The seven questions procurement has asked every quarter.
Answered once, here, in the language your finance team will paste into an SOW. For anything not covered, a 30-min commercial call will produce a worked quote — not a brochure.
01 How exactly do volume discounts apply? +
Tiered, not retroactive. Your discount on a given month is determined by the tier your monthly NC volume lands in — standard below 250k, −10% from 250k to 1M, −20% from 1M to 5M, −35% above 5M. Every NC in that month draws at that tier's discount. No cumulative recalculation, no year-end settle-ups, no "you crossed 1M in December so we're clawing back November." The curve is published; the final rate you commit at is set on the commercial call against your actual volume.
ref · spec · tier-01
02 Do unused Node Credits expire? +
Not within the commit year. NC from an under-consumed quarter roll forward against the annual commit. What does expire is the annual envelope — unused NC at the end of the commit year don't carry into the next term. That's the trade for rate-locked tier pricing. If your consumption is lumpy, the workforce-planning team is the one to talk to; we can shape the commit around your cycle rather than calendar months.
ref · MSA · commit terms
03 What counts as "one" candidate screen? +
One scored evaluation against one success profile, producing one signed decision trace — 2 NC. Re-screening the same candidate against a revised success profile is a new screen — and should be; it's a different decision. Bulk rescoring (pool against a refit profile) is priced separately at 1,800 NC per thousand, because it's a batch operation that runs under different compute guarantees.
ref · spec · rescore-01
04 How do overages work past the commit? +
At the same tier discount that applied to the quarter they occurred in. If a seasonal surge pushes you through Tier 3 into Tier 4 in Q3, Q3's overage draws at Tier 4's −35% tier — not at standard, not at a punitive uplift. We don't run a snap-back clause. If overages persist for two quarters, we'll re-cut the commit at the new volume rather than leave you paying overage terms on what is now your baseline.
ref · MSA · §4.2
05 Can we change deployment mid-term? +
Yes. The catalog is the catalog regardless of deployment; only the multiplier changes. Migrating from Nodes Cloud pilot to Customer VPC in month 4 re-draws every subsequent invoice at the 2.0× multiplier — it doesn't require a new contract, a new procurement cycle, or a new DPA if your template already permits VPC deployment. The architecture review deliverables from the Customer-VPC path become your enablement package for the switch.
ref · MSA · §6.1
06 Is there a minimum commit? +
Not to start. Pilots run at Tier 1 standard with no annual commit; you draw credits as you consume, invoiced monthly, NET 45. Tier 3 discounts unlock at 1.2M NC committed annually — roughly the volume at which a carrier's first two role families are in production. Tier 4 is 12M NC / yr. Below 1.2M the math almost never justifies a commit, and we'd rather you stay flexible.
ref · MSA · §2.3
07 Is there a per-seat or per-user fee? +
No. The entire catalog is consumption-priced in Node Credits. Admin and reviewer seats are unlimited; SSO group-mapped RBAC does the access control, not a license key. We've watched per-seat pricing quietly cap how much of the platform actually gets used — which is the opposite of what a decision-intelligence platform should optimize for. So we deleted the seat SKU and never looked back.
ref · MSA · §3.4
Thirty minutes with a commercial engineer. A worked quote you can model against.
Bring last quarter's hiring and headcount numbers. Leave with a line-item NC forecast, the deployment that matches your security review, and a signed-order-form-ready commit. No separate deck. No "circle back with pricing."