Developer platform pricing

Ship Aegir into your product with pricing that starts free and scales with authentication and age-verification volume.

Beta-1 keeps the developer commercial story straightforward: real credit-card billing through Stripe, visible plan tiers, and placeholders for ACH, Net 30, and Aegir Safe until those rails are ready. The active package surfaces are NuGet and NPM.

Growth

100,000 / month

$5 / month

Step into a larger monthly envelope without changing the basic developer flow.

  • 100,000 monthly transactions.
  • Straightforward monthly pricing.
  • Good fit for early production-style usage.
Growth+

500,000 / month

$25 / month

A larger recurring tier for teams that want room before overage-sensitive pricing matters.

  • 500,000 monthly transactions.
  • Simple flat price for Beta-1 clarity.
  • Good fit for growing products with predictable volume.
Scale

1,000,000 / month

$100 / month

The first seven-figure transaction tier in the standard pricing grid.

  • 1,000,000 monthly transactions.
  • Flat price before custom or larger-volume scaling.
  • Useful for teams preparing for serious production traffic.
Large volume

5,000,000+ / month

~$5 per 100k

A larger-volume pricing path for products that outgrow the standard starter tiers.

  • Visible scalable pricing language for Beta-1.
  • Intended to connect later into custom commercial handling.
  • Makes it clear that Aegir can grow beyond the starter ladder.
Enterprise volume

1,000,000,000+ / month

~$4 per 100k

Reserved for the largest transaction profiles and future enterprise handling.

  • Enterprise-scale pricing indicator.
  • Kept visible so the sales page does not imply an artificial ceiling.
  • Later contracts and admin/commercial tooling will refine the real workflow.
Payment methods

Beta-1 turns on credit card and shows the rest honestly as upcoming rails.

  • Credit card is the only Beta-1 payment rail intended to be active.
  • ACH remains visible as a placeholder for a later phase.
  • Net 30 remains visible as a placeholder with later suspension logic.
  • Aegir Safe remains visible as coming soon and inactive.
Developer workflow

The sales page should connect directly into signup, login, and later billing-aware dashboard flows.

  • Developers should be able to evaluate pricing before being forced into the dashboard.
  • The free tier should flow naturally into account creation or developer login.
  • Later checkout work can connect this page into Stripe without reshaping the pricing story.
Package surfaces

Phase 1 focuses on the package surfaces developers can actually use now.

  • .NET / NuGet and TypeScript / NPM are the active Phase 1 package surfaces.
  • Java remains out of the immediate Phase 1 delivery path.
  • The sales page should make the active package story clear before checkout or login begins.
Sales-page exits

Developers should always know what to do next.