Working with Supabase?

Supabase app insecure or acting up? We fix it.

Most Supabase projects that land on our desk were scaffolded by an AI app builder in an afternoon, then quietly shipped. The database works, sign-up works, and the row-level security policies are either missing or wide open. We go through the project table by table and fix the actual holes.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

supabase.log

still failing

What it is

Supabase at a glance

Supabase is an open-source backend-as-a-service: hosted Postgres with authentication, file storage, a realtime layer and edge functions wrapped around it, reachable from a browser or mobile app through a single client library. It was founded in 2020 by Paul Copplestone and Ant Wilson, and it markets itself as the open source Firebase alternative.

Under the covers it stitches together PostgREST for the auto-generated API, GoTrue for auth, a storage service in front of S3-compatible object storage, a realtime server that streams database changes over websockets, and Deno-based Edge Functions. It has become the default back end for Lovable, Bolt and several other AI app builders, which is why a lot of Supabase projects now exist that no human engineer ever reviewed.

Type
Backend-as-a-service on PostgreSQL
First released
2020
License
Apache 2.0, open source
Maintained by
Supabase, Inc.
Typically used for
Web and mobile app back ends, AI-generated apps, prototypes that need auth and a database fast

The honest version

Supabase pros and cons

No technology is all upside. This is where Supabase earns its place and where it tends to cause trouble.

Where Supabase is strong

  • A real database under the hoodUnderneath the client library is ordinary Postgres, so the SQL, extensions and tools your team already knows still apply.
  • Auth, storage and realtime in one placeSign-up, file uploads, websockets and server functions all ship together, which saves wiring four different services into a small app.
  • Generous free tierHobby projects and early prototypes fit inside the free plan without a credit card, which is why AI builders default to it.
  • Open source and self-hostableThe whole stack is Apache-licensed and can be run on your own servers if you ever need to leave the hosted product.
  • Good landing pad for AI-builder outputLovable, Bolt and Cursor all know how to target it, so the generated code at least talks to a sensible back end.

Where Supabase bites

  • Row-Level Security is easy to get wrongThe policies are powerful, but one missing policy on one table is enough to expose every row in it to the public anon key. AI builders frequently ship schemas with no policies at all.
  • Free projects pause when idleA hobby project that sees no traffic for a week gets paused, and anyone hitting the API during that window sees errors until someone logs in and resumes it.
  • Edge functions have cold startsThe Deno runtime spins up on demand, so the first call after a quiet spell is slow, and long-running work runs into the hard 150-second ceiling.
  • Pricing climbs quickly past the free tierDatabase egress, storage and bandwidth all meter separately, and an app that goes slightly viral can see the bill multiply before anyone notices.
  • Soft lock-in through the platform piecesPostgREST conventions, auth hooks and storage URLs all end up stitched into the client code, so leaving the hosted product is rarely a one-day job.
  • Extensions and versions you did not chooseThe platform decides which Postgres version runs and which extensions are available, and upgrades arrive on their schedule rather than yours.

Sound familiar?

Common Supabase problems we fix

The Supabase problems that bring people to us, and what you have once each one is fixed.

anon key returns every row

An AI builder left the database wide open

The generated schema has no row-level security policies, or has policies that effectively allow anyone with the public anon key to read and sometimes write every table.

Every table locked down, tested

auth.uid() is null

Logged-in users can't see their own data

Policies were written against auth.uid() but the request is reaching the database without a user JWT, so every check fails and the app looks broken.

Auth flow and policies agree

project paused

The project paused itself

A free-tier project with no traffic for a week gets paused, and clients get connection errors until it is manually resumed or moved to a paid plan.

Right plan for how it is used

Edge Function timeout after 150s

An edge function keeps timing out

Work that should have been a background job is running inside an edge function and hitting the hard execution ceiling.

Moved to the right place

egress 412 GB this month

The bill jumped without warning

A chatty client, unindexed queries pulling whole tables, or a public bucket serving large files without a CDN in front.

Traffic shaped, costs predictable

WebSocket closed with code 1006

Realtime drops subscriptions

Too many channels, a filter that does not match the publication, or a client that reconnects without backoff and gets rate-limited.

Subscriptions trimmed and stable

no backup newer than launch day

Nobody has taken a backup

The hosted daily backup exists, but nothing has ever been restored from it, and point-in-time recovery was never turned on.

Restores tested on a schedule

What we do

Supabase help, from audit to upkeep

Call us for a security review, or hand us the whole project.

Security audit
Every table, bucket and function walked through, with RLS policies written where they are missing and tested against the anon and authenticated roles.
AI-builder cleanup
Projects scaffolded by Lovable, Bolt or Cursor that work but are not safe to ship, brought up to a standard a human would sign off on.
Performance
Indexes, PostgREST query shapes and connection pooling, with measurements from before and after.
Self-hosting
Moving a hosted project onto your own infrastructure when the pricing or the compliance rules demand it.
Edge functions and integrations
Server-side work that belongs off the client, wired to Stripe, SendGrid or whatever the app actually needs.
Managed Tech
Monitoring, backups, upgrades and a team to call, on an ongoing basis.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Supabase alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Supabase questions

Something else? Call+1 737 727 7327

Why is my Supabase data publicly readable?

Almost always because row-level security is off on the table, or the policies on it allow the anon role to read everything. The public anon key is meant to be shipped to browsers, so the database itself has to enforce who sees what. We go table by table, enable RLS, and write policies that match how the app actually uses the data.

Why did my Supabase project get paused?

Free-tier projects pause after about a week with no activity. The project is not deleted, but the API and database stop responding until someone signs in to the dashboard and resumes it, or the project is moved to a paid plan that does not pause.

Can you fix auth and permissions on a Supabase app an AI builder generated?

Yes, and it is one of the more common things we are asked to do. We audit the schema, enable row-level security where it was skipped, write policies for the anon and authenticated roles, review the auth flow end to end, and give you a short written summary of what changed and why.

Should I self-host Supabase or stay on their cloud?

For most small and mid-sized projects the hosted product is the right answer. Self-hosting makes sense when the pricing has grown awkward, when compliance rules require the data to live somewhere specific, or when you need Postgres settings and extensions the hosted plan does not expose.

Why are my Supabase edge functions timing out?

Edge functions have a hard execution limit of 150 seconds and they cold-start after idle periods. Work that takes longer than that, or that should not block a user request at all, belongs in a background worker outside the edge runtime. We move it there and leave the function doing only what it needs to.

How much does Supabase help cost?

Estimates are free. Describe what the project does and what is going wrong, and you get a price before any work begins.

Free estimate

Supabase project worrying you?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.