Supabase-style dashboards are bloated and enterprise SQL tuners require onboarding and DB access. Devs just want to paste a query and its EXPLAIN output and get an answer in seconds.
Indie developers and small backend teams on serverless Postgres
Free single-shot analysis as top-of-funnel; Pro at $9-19/mo for history, exportable index DDL, schema-aware suggestions and shareable report links
Supabase-style platforms keep adding features, making slow-query debugging a deep multi-panel hunt. Devs need a one-off plan reading, but are pushed toward heavy DBA-oriented tools.
A minimal SQL execution-plan analyzer for developers on Supabase / Neon / self-hosted Postgres: paste a query and its EXPLAIN output, get bottleneck nodes, cost breakdown and candidate index suggestions in 30 seconds.
Debugging is a maze: users dig through Supabase Dashboard log/perf panels and then read raw EXPLAIN text themselves. Tools like pganalyze and EverSQL target DBAs and enterprises — heavy onboarding, DB connection required, high pricing. The real scenario is a one-off slow query: paste the SQL and plan, immediately learn which node is expensive and which index to add.
Indie developers, full-stack engineers and 1-5 person backend teams on serverless Postgres (Supabase, Neon, Railway); plus freelancers who need fast performance tuning for client deliverables.
Medium-strong signal: Supabase's user base is large and growing, slow queries are a frequent recurring pain, and LLMs plus frontend visualization make explaining EXPLAIN cheap. A free zero-friction entry point can feed a paid tier.
No pricing clues in the source — inferred: free single-shot analysis (SEO/virality engine), Pro at $9-19/mo for history, copyable index DDL, shareable report links and schema-aware suggestions.
Medium. Parse Postgres EXPLAIN (FORMAT JSON) into a node tree, roll up actual time and cost bottom-up, highlight the hottest node, then extract candidate index columns from WHERE / JOIN / ORDER BY. Key challenge: no real data distribution, so suggestions are candidates, not guarantees. Extending to MySQL / SQL Server multiplies the work.
Signals: 2 · Source: competitor_gap