Does Furge check my database after it applies a change?

Yes. Right after Apply, and whenever you press Check it now in History, Furge checks your live database itself. It confirms every table Furge manages has row level security, Furge's rules, field limits and role checks as they were applied, and says anything changed outside Furge since (a rule added in Supabase that opens every row, row level security switched off, a field limit dropped, a grant taken away, a role check rewritten). Then it reads each table as a signed-out visitor, a signed-in person with no role, someone with each role and someone who owns rows, and compares what each sees with what Furge's rules give them. It's read-only: the database refuses any write during the check, and only counts come back, never a record or anyone's id. Each requirement it confirms is Verified, with what was seen; one your database shows doesn't hold is Failed, with why. Where it can't tell yet (a table with no rows, nobody with a role), it says so and leaves it Applied. Changes (adding, changing, deleting) aren't tried on your real rows: for those, Furge checks its rule is there exactly as applied and tested.

Steps

  1. Turn on Developer at the top of the studio (or press Shift+D) and open Backend.
  2. Open History: under the version that's live, On your database says what the check found.
  3. Press Check it now to check again, for example after changing something in Supabase.

Also asked as

Related

Still stuck? Ask Furge Help, the round chat button at the bottom right, or contact the Furge team.

← All of Furge's docs