Why I Chose Supabase for Every New Project

When I started building KarJo, I needed auth, a database, and file storage — fast, and without managing separate services for each. Supabase gave me all three with a Postgres database underneath, which meant I could write real SQL instead of learning a proprietary query language. Row-level security (RLS) turned out to be the real win. Instead of writing authorization logic in application code, I define who can read or write directly on the database table. A public portfolio page can read projects and blog posts freely, while only an authenticated admin account can create or edit them — enforced at the database level, not just in the UI. For Karobar, geolocation was a requirement — matching customers with nearby service providers. Supabase's PostGIS extension handled that without needing a separate mapping service. The tradeoff: Supabase is still evolving, and some features (like more complex Postgres extensions) need manual setup through the SQL editor rather than a UI toggle. For a solo developer or small team shipping real products quickly, that's a fair trade for the control and cost savings.