68 / 100

Comet pricing teardown

https://www.comet.com/site/pricing

A developer-first, open-core pricing page that leads with two $0 entry points and a single $19/mo paid tier, then jumps to a custom Enterprise plan. The ladder is clear for individuals and small teams, but the $19 anchor looks oddly low, pricing never reflects growth for teams, and the page's own jargon (spans, Opik vs. MLOps) adds friction. Strong on transparency and free-entry anchoring; weak on annual billing, trust signals above the fold, and an enterprise anchor price.

Tier structure

Open Source

$0

Free Cloud

$0

Pro Cloud

$19/mo

Enterprise

Custom

Value metric

Hybrid: flat monthly price with span-volume and retention limits, plus overage add-ons

How limits scale

Spans per month Unlimited (self-hosted) → 25k → 100k → Unlimited
Team members Not capped (self-hosted) → 10 → 50 → Unlimited
Span data retention Unlimited (self-hosted) → 60 days → 60 days (extendable to 400) → Custom

Escalation logic

Two free entry points (self-hosted and hosted) feed into a single flat-priced Pro plan with 4x the spans and 5x the seats, then Enterprise unlocks unlimited usage, SSO, compliance, and SLAs. Upgrade triggers are volume (spans), team size, and security/compliance needs.

Psychological anchors

  • Free tier as entry anchor — Two $0 plans (Open Source and Free Cloud) sit on the left, so $19 for Pro reads as a trivial step up and removes any reason not to start.
  • Highlighted recommended plan — Pro Cloud carries a 'POPULAR' pill badge, a gradient/elevated card, and the only filled-blue 'Start Free Trial' button among the plan CTAs, pulling attention to the paid conversion path.
  • Enterprise 'Custom' as high anchor — Large 'Custom' headline in the price slot signals a premium tier, though without a number it anchors weakly.
  • Low-friction price point — $19/month is an impulse-buy price that lets teams expense it without approval, supporting bottom-up adoption.
  • Differentiated CTA hierarchy — CTA labels match intent per tier: 'GitHub' for OSS, 'Get Started' for Free, 'Start Free Trial' for Pro, 'Contact Us' for Enterprise.
  • Cumulative 'Includes everything in X plus' framing — Pro and Enterprise cards use 'Includes everything in the previous plan plus:' to make each step up feel additive and scannable.
  • Product-line toggle (Opik / MLOps) — A pill toggle at the top switches between two product pricing tables, keeping a complex two-product catalog on a single page.

What this page is optimizing for

Primarily self-serve, bottom-up developer adoption (free OSS and free cloud, instant-start CTAs, transparent $19 price), with Enterprise as a sales-assisted expansion path. The open-source GitHub CTA as the first plan reinforces community-led growth rather than immediate revenue capture.

Red flags

  • No monthly/annual toggle or annual discount is visible; Pro is only offered monthly, leaving easy cash-flow and retention gains on the table.
  • The $19 Pro price looks very low relative to its stated limits (100k spans, 50 seats) and has a huge gap to a fully custom Enterprise plan, with no mid-market step for teams that outgrow 100k spans but don't need Enterprise.
  • Value metric (spans) is jargon the page only explains in an FAQ and tooltips; buyers can't easily predict their span volume or cost, and overages ($5/100k spans, $29/100k for extended retention) are buried in the lower comparison table.
  • Pro Cloud's retention (60 days) is identical to the Free plan, so the visible upgrade value above the fold is just volume and seats — weak differentiation until the user reads the comparison table.
  • Because the Open Source plan is unlimited and free, it cannibalizes paid cloud plans for technical teams, and the page does little to justify why to pay for cloud over self-hosting.
  • Two products on one page (Opik and MLOps) with overlapping plan names (Free/Pro/Enterprise) and a different Pro price model ($19 per user vs. $19 flat) create confusion about what a plan actually costs.
  • No customer logos, testimonials, or security badges appear near the plan cards; compliance claims (SOC 2, HIPAA) are only listed in Enterprise text.
  • The page is extremely long, with a very large feature-by-feature comparison table, which makes the decision harder rather than easier for casual evaluators.

Best-practices scorecard

What works · 4

  • Clear recommended tier — Pro Cloud is badged 'POPULAR' and has the only filled primary-color CTA among plan cards.
  • Visible prices — Three of four plans show explicit prices, including both free tiers and $19 Pro; only Enterprise is custom.
  • FAQ or objection handling — A Q&A section covers Comet vs. Opik vs. MLOps, how to get started, self-hosting, plan differences, and what a span is.
  • Clear CTAs per tier — Each tier has a distinct, intent-matched CTA (GitHub, Get Started, Start Free Trial, Contact Us), with the Pro CTA visually emphasized.

Half measures · 3

  • Value metric matches usage — Spans scale with LLM usage, which aligns with customer value, but the unit is opaque and the Pro plan's flat price plus overages is hard to forecast.
  • Tier differences are scannable — Cards show clear three-line limits and 'everything in X plus' lists, but real differences (overages, retention add-ons, Ollie access) require scrolling a very long comparison table.
  • Trust signals present — Compliance certifications (SOC 2, ISO, HIPAA, GDPR) are listed under Enterprise, but there are no logos, testimonials, or review badges near the pricing cards.

What's missing · 1

  • Annual discount offered — No annual billing option or discount is shown; Pro is monthly-only.