SupaLint Supabase table health sentinel

Find and fix drifting, unindexed, and misconfigured tables in Supabase projects

Problem

Many indie developers and small backend teams run on Supabase and iterate fast, so schemas quietly drift: missing indexes, mismatched field types, and RLS policies that were never configured. Problems only surface when queries slow down or permissions break. A Show HN tool dedicated to finding broken Supabase tables shows real demand.

Solution

Connect to a Supabase project and regularly scan schema and RLS policies for missing indexes, type conflicts, disabled RLS, and orphaned foreign keys, then suggest copy-pasteable SQL fixes. Read-only diagnosis and recommendations, no invasive migrations.

Users

Indie developers, small SaaS teams, and outsourced developers using Supabase

MVP

Read-only scan of schema and RLS; detect missing indexes, type mismatches, disabled RLS, and orphaned foreign keys; output copy-paste fix SQL; weekly health report; never touch actual row data

Revenue

Free single-project diagnosis plus paid multi-project or scheduled scanning; monthly plans for agencies managing client projects

Why now

Supabase has become the default database for indie devs and small teams but lacks a lightweight schema health tool. An indie dev can start in a weekend and iterate from there