How Aurora Pricing Works in Plain Language
Use this page when you want the rules around self-serve, guided buying, add-ons, renewals, and Command stated clearly before procurement hardens the deal.
5 operators, 1 workspace, 1 framework, 25 review projects
Reviewer controls, enterprise controls, exports, and reusable proof stay in the paid base.
Aurora grows through named units instead of forcing a hidden plan jump.
- Annual prepay is the default:Aurora publishes annual pricing first so buyers understand the real commercial model instead of reverse-engineering monthly teaser numbers.
- Add-ons stay visible:Operators, frameworks, connectors, review projects, covered users, vendors, and Command scope expand through named units.
- Procurement paths stay flexible:Direct annual invoice, AWS Marketplace, and private offer paths stay on the table when procurement prefers them.
- Command stays premium on purpose:Command remains quote-led because deployment, premium support, and environment-boundary proof change the operating burden.
Base Platform, Clear Modules, Premium Command
Start with Platform Core
Every paid Aurora deal starts from Platform Core. That gives the team the governed-proof base, reviewer-control plane, enterprise controls, and 25 review projects before deeper expansion begins.
Add modules when the work changes
Continuous Compliance, Risk & Accountability, Vendor Risk, Workforce Readiness, Response Readiness, and the readiness bundle stay visible so the commercial model follows the workload instead of forcing a ladder.
Treat Command as a premium proof plane
Command Insight, Command Control, and Command Expansion Pack are priced separately because deployment, collector health, boundary scope, and premium support are materially different from standard modules.
Self-Serve, Sales-Assist, and Quote-Only Are Explicit
Self-serve
Standard non-Command configurations stay self-serve up to 10 operators, 3 workspaces, 25 automated connectors, 250 vendors, 1,000 covered users, 5 frameworks, and no regulated or private deployment requirement.
Sales-assist
Aurora moves into a guided motion when support burden, procurement complexity, connector scope, or review workload start pushing the standard envelope even if the buyer is still in public-price territory.
Quote-only
Command, regulated or private deployments, heavy environment-boundary work, and materially service-heavy launches stay quote-led so the economics match the real operating burden.
What Happens After the Deal Closes
Contracted-rate add-ons during term
When your footprint expands during the active term, Aurora uses the same contracted units the team already approved instead of forcing a surprise full-package reset.
Quarterly true-up review
Aurora reviews metered expansion units quarterly so growth is regular, visible, and easy to explain internally.
80% and 100% usage warnings
Aurora warns early as you approach capacity and gets explicit again when you actually cross the boundary so there is time to add the right unit before the next review crunch.
24-month price protection
Multi-year planning can use published price protection so renewals feel like procurement work, not a hidden-uplift negotiation.
Buy Through the Path That Fits Procurement
Direct annual invoice
Aurora can close on a standard annual prepay invoice when procurement wants the cleanest path.
AWS Marketplace and private offer
Marketplace and private-offer channels stay available when buyers want procurement consolidation without changing the product scope.
Command deployment package
Command includes a mandatory deployment package and premium support minimum because the product motion is infrastructure-adjacent, not a lightweight add-on.
No hidden trust or reviewer surcharges
Aurora keeps the common buyer pain points explicit: no approved-domain tax, no viewer-seat tax, and no per-question tax.