coExploro
All samples

Product teardown

Supabase product teardown

A curated sample showing what coExploro observes about onboarding, pricing cues, and UX signals.

Illustrative public sample. coExploro is not affiliated with Supabase.

Sample output

Overall score 90/100

PM 91

UX 88

Summary Card + findings

Category
Backend-as-a-service on Postgres
Published
2026-08-18
Updated
2026-08-18
Visit product

Summary Card

The shareable readout before the full canvas.

This public version uses the same compact card pattern as private teardowns: one score, four persona signals, and the strongest findings compressed into a card a product team can forward.

Read the methodology

Overall score

90/100

Confidence

high

PM

91/100

UX

88/100

coExploro

Supabase

teardown · captured 2026-08-10

90
Overall score · good
high confidence
PM
91
MKT
94
UX
88
DSG
88

Top findings

  • Competitor names are treated as entry points, not comparisons.
  • The headline proof metric is a public repository star count.
  • The tier comparison runs to several hundred cells.
coexploro.com/teardowns/supabaseView full teardown

Findings

What the personas surfaced.

Marketing

High impact

The proof metric is one developers already read

A public repository star count in the primary navigation swaps conventional logo-cloud credibility for a signal the target audience knows how to interpret without explanation.

high confidence

PM

High impact

Competitor names appear as footer destinations

The footer carries "Switch from Firebase" and "Switch from Neon" as their own links, alongside audience paths for AI builders, agencies and startups. Rival product names are treated as navigation, not only as comparison content.

high confidence

UX

High impact

The tier comparison runs to hundreds of cells

Four tiers spanning $25 to $599 per month are compared across a table of roughly 760 cells, measured in the live DOM. Every capability is listed rather than summarised.

high confidence

Design

Medium impact

Pricing and its calculator compete for attention

An interactive usage calculator directly under the tier grid doubles the decisions on one screen: clarity for a curious reader, load for a scanning one.

mid confidence

FAQ

Public sample notes.

Is this a live Supabase project scan?

No. It covers three pages that were publicly visible on 10 August 2026. No project, private data or share link is involved.

Why is confidence high here and mid on other samples?

All six UX dimensions were observable in this capture. Where a loading state never appears in frame, perceived performance goes unscored and confidence drops a band. It is a property of the run, not a verdict on the product.

What does high confidence mean here?

That all six UX dimensions were observable in this capture. Most runs land a band lower because perceived performance needs a loading state to appear in frame. It describes the evidence available, not the quality of the product.

Next

Run the same format on a product you care about.

Start a teardown