58 / 100

Hasura pricing teardown

https://hasura.io/pricing

Hasura DDN's pricing page is built around a novel 'per active model' usage metric that scales with actual API usage rather than seats, which is well-suited to developer-centric supergraph workloads but requires significant cognitive effort to estimate costs. The three-tier structure (Free → Base → Advanced) follows a logical escalation from individual developers to multi-team federated architectures, but the absence of a highlighted/recommended plan, no annual discount toggle, and no visible price calculator leaves self-serve buyers without enough confidence to convert quickly. The page is thorough and technically credible but under-optimized for conversion.

Tier structure

DDN Free

$0/mo

DDN Base

starting at $5/active model/mo

DDN Advanced

starting at $30/active model/mo

Value metric

per active model per month (model accessed >1,000 times/month)

How limits scale

Supergraph developers 1 → Unlimited → Unlimited
Observability retention (traces) 15 minutes → 30 days → 30 days
API performance metrics retention 15 minutes → 30 days → 30 days
Model & field usage statistics Not available → 30 days → Custom
Multi-repo CI/CD No → No → Yes

Escalation logic

Tiers escalate from a solo-developer free tier to a single-team paid tier to a multi-team federated tier, with each step unlocking collaboration depth and security/compliance features. The 6x price jump from Base to Advanced ($5 → $30 per model) is steep and the upgrade trigger (multi-repo CI/CD, independent subgraph development) is narrow, targeting a specific enterprise use case.

Psychological anchors

  • Free tier as entry anchor — DDN Free at $0 with unlimited API requests and autoscaling lowers the barrier to entry dramatically, pulling developers into the ecosystem before any payment friction.
  • Usage-based 'active model' metric — Pricing is per active model (>1,000 calls/month), meaning costs scale naturally with product growth rather than punishing early-stage users — a developer-friendly framing.
  • Private DDN as enterprise anchor — A 'Private DDN' section with 'Contact sales' and no public price acts as a high-end anchor, implying a tier above Advanced exists for security-sensitive enterprises.
  • Logo social proof — NASA, OpenAI, Siemens, and Airbus logos appear immediately below the plan cards, lending enterprise credibility to the page.
  • Asterisk footnote on pricing — The '*' on 'active model' pricing is explained in a footnote (>1,000 calls/month threshold), which softens sticker shock but adds cognitive load.

What this page is optimizing for

The page is primarily optimized for developer self-serve adoption via the free tier, with a secondary goal of enterprise lead generation through the Private DDN 'Contact sales' path. The detailed feature comparison table and FAQ signal a technically sophisticated buyer who self-educates before converting.

Red flags

  • No highlighted or 'most popular' plan — all three tiers are visually equal weight, removing the decoy effect and leaving buyers without a clear recommendation.
  • No annual billing toggle or discount offered anywhere on the page, missing a standard 17-20% conversion lever and ARR acceleration tool.
  • The 'per active model' metric is non-intuitive; without a cost calculator or example scenario, buyers cannot estimate their bill, increasing drop-off risk.
  • The 6x price jump from Base ($5/model) to Advanced ($30/model) is steep with a narrow upgrade trigger (multi-repo CI/CD), creating a gap that may push teams to stay on Base longer than intended.
  • DDN Base and DDN Advanced share identical observability retention (30 days), weakening the differentiation story between the two paid tiers.
  • Security features like Dedicated VPC, SSO, and HIPAA compliance are marked with asterisks on both Base and Advanced but are only available via Private DDN (contact sales), making the feature matrix misleading.
  • No pricing FAQ visible in the main flow — the FAQ section is minimal and buried at the bottom, leaving key objections (e.g., 'what counts as an active model?') unanswered inline.
  • CTAs are generic ('Start building', 'Start free trial') with no differentiation by persona or use case, reducing relevance for different buyer segments.

Best-practices scorecard

What works · 1

  • Trust signals present — Enterprise logos (NASA, OpenAI, Siemens, Airbus), SOC2 Type 2, GDPR, and HIPAA compliance badges provide strong credibility signals.

Half measures · 5

  • Visible prices — Free and starting prices are shown, but 'starting at' with a non-intuitive per-model metric makes true cost opaque without a calculator.
  • Value metric matches usage — Per-active-model pricing aligns well with API-centric workloads but is unfamiliar to most buyers and requires explanation, adding friction.
  • Tier differences are scannable — The detailed comparison table is comprehensive but very long; the top-of-page plan cards do highlight key differentiators, though the asterisk-heavy security section is confusing.
  • FAQ or objection handling — A FAQ section exists but contains only a few questions; the most critical objection ('how much will I actually pay?') is not addressed with an example or calculator.
  • Clear CTAs per tier — Each tier has a CTA ('Start building', 'Start free trial') but they are generic and do not reinforce the value proposition of each specific tier.

What's missing · 2

  • Clear recommended tier — No plan is visually highlighted, badged as 'most popular', or otherwise recommended — all three cards receive equal visual treatment.
  • Annual discount offered — There is no annual billing toggle or mention of an annual discount anywhere on the page.