Buying guide

Understand Pricing, Terms, and Rollout without a Procurement Maze

Aurora keeps the buying motion legible: annual-prepay default, named add-on units, flexible procurement channels, included enterprise controls, and a separate Command path when in-environment proof is in scope.

Include Procurement in the Walkthrough See How Pricing Works

Use this page when legal, procurement, or finance wants the rules stated clearly before the technical evaluation is done.

Annual-Prepay Model Stated Up Front:
Aurora publishes commercial mechanics before the demo, not after.
Enterprise Controls Named, Not Hidden:
Procurement knows whether SSO, SCIM, exports, diffs, and auditability require an upgrade before the eval starts.
Command Has Its Own Commercial Path:
Command deployment, premium support, and environment-boundary pricing stay separate from the standard software motion.
Add-On Units Published and Named:
Operators, frameworks, review projects, vendors, users, connectors, and Command scope expand through named units.

Aurora controls workspace showing export-safe controls, review state, and procurement-safe output posture.

Procurement-safe proof posture

At a Glance

Procurement-Safe Proof Posture

Named enterprise controls, reviewer-safe export paths, and a commercial model procurement can explain internally without translation.

enterprise-control summary audit-period export posture procurement-ready output map

How Procurement Usually Moves

Align Channel, Controls, Commercial Terms, and Support Expectations Early

Aurora shortens procurement by making the buying path, included controls, expansion rules, and Command deployment terms visible before legal review starts.

Choose the Commercial Path

Self-serve, sales-assist, or quote-only based on footprint, Command scope, and procurement constraints.

Pricing mechanics

Review Included Controls

Aurora names the enterprise controls mature procurement teams expect in the base product.

Enterprise controls

Pick the Transaction Path

Direct annual invoice, AWS Marketplace, or private offer. The product packaging stays the same regardless of channel.

Procurement path

Separate Command Deployment Terms

When Command is in scope, deployment, premium support, and boundary terms stay explicit instead of hidden in a blended quote.

Command for regulated environments

Clear Renewal and Add-On Terms

Renewals, true-ups, and add-on pricing stay simple enough to approve without guesswork.

Pricing policies

What This Solves

Why Procurement Slows Down Even When the Product Fit Is Real

Buying friction appears when pricing rules, enterprise controls, export posture, and premium exceptions stay partially explained.

Expansion Rules Are Vague

Aurora publishes common units and thresholds so procurement knows how growth changes the deal.

See pricing mechanics

Enterprise Controls Show Up Late

Aurora names the control surface buyers expect instead of relying on generic enterprise-grade language.

See Enterprise Controls

Command Gets Blended into the Wrong Motion

Aurora keeps regulated and hybrid Command on a separate commercial path so procurement understands the different terms.

See regulated-environment proof

What This Produces

The Commercial Artifacts Procurement Teams Use

Deals move faster when procurement reviews the commercial model and platform posture without translating sales language.

Sample deliverable

PDF

Pricing and expansion map

A plain-language summary of base platform, modules, add-ons, thresholds, and expansion units.

What reviewers get

Base platform terms
Named expansion units
Quote-only boundaries

Sample deliverable

PDF

Enterprise-control summary

A procurement-safe outline of identity, export, auditability, and reviewer-safe control posture.

What reviewers get

SSO and SCIM stance
Export and diff posture
Auditability controls

Sample deliverable

PDF

Channel and invoicing path

A clean explanation of direct, invoice, marketplace, and private-offer options plus the Aurora-managed billing workflow behind them.

What reviewers get

Channel fit
Commercial path
Contracting notes

Sample deliverable

PDF

Command commercial addendum

The separate deployment and premium-support motion when regulated or hybrid Command is in scope.

What reviewers get

Deployment package
Premium support minimum
Boundary and scope notes

Pages Procurement Uses

The Pages That Usually Shorten Internal Review

Public surfaces procurement, legal, security review, and finance reference while the deal moves.

01Pricing

The public module catalog, plan anchors, and inclusion promises.

Explore pricing

02How pricing works

The thresholds, add-on units, true-ups, renewals, and channel mechanics in plain language.

Explore pricing mechanics

03Enterprise Controls

The named identity, auditability, and export controls Aurora includes in the paid product story.

Explore Enterprise Controls

04Regulated and hybrid Command

The Command path for teams whose technical proof needs to stay inside the environment boundary.

Explore regulated-environment proof

Common Procurement Questions

The Commercial Topics Aurora Brings Forward Early

Topics that matter once the buyer wants to understand how the commercial model behaves under real growth.

Renewals and Commercial TermsAurora explains annual renewal terms, add-on unit behavior, and commercial path options before finance asks twice.Reviewer-Safe OutputsEnterprise controls, reviewer operations, and export posture sit together so procurement sees the buying workflow clearly.Marketplace and Private OfferAurora routes the same product scope through the channel procurement prefers without changing the product logic.

Questions Procurement Asks

Plain-Language Answers for the Commercial Review Team

Common questions once the buyer is serious and internal review starts.

Does Aurora publish real pricing or just anchor copy?

Aurora publishes list pricing for Platform Core, major non-Command modules, and common expansion units. Procurement sees the commercial shape before a private quote exists.

Are enterprise controls included or hidden?

Aurora includes named enterprise controls in the paid plan. The goal is to remove late-stage procurement friction, not create another surprise upsell.

Why is Command handled separately?

Command changes the deployment, support, and environment-boundary burden. Aurora keeps that motion separate so the standard software path stays clean and the Command path stays honest.

Can Aurora work through our preferred channel?

Yes. Aurora supports direct annual invoice, AWS Marketplace, or private-offer procurement while preserving the same core pricing logic. The tenant billing state stays authoritative inside the product; accounting systems remain reconciliation targets.

Live walkthrough

Bring Your Commercial and Procurement Questions to One Call.

Share finance, procurement, or legal concerns alongside product fit questions. We walk through the cleanest buying path without hiding the harder parts of the deal.

Request a 15-Minute Walkthrough

How Aurora pricing works

Share a framework, buyer request, questionnaire, or renewal packet. We'll show how Aurora handles it.