
Who's behind GuardLayer
I'm Viktor Emil Stevanovic, and I build GuardLayer on my own.
Why I started
AI tools made it possible to ship a working app in a weekend. Security didn't get faster at the same rate. When I started reading public Supabase projects, I kept finding the same few mistakes: tables anyone can read, policies that only check that someone is signed in while anyone can sign up, users who can make themselves admin, and database functions that anonymous visitors can still call.
It isn't only vibe-coded apps. Hand-written projects by careful developers have the same holes, because the defaults are easy to get wrong and nothing warns you. The app works, so it looks fine, until someone looks at the database instead of the UI. I saw a way to help: a check that looks where the leaks actually are.
Helping before selling
Besides building the product, I read public repositories and report what I find privately to the owners, with the exact fix, before anything is said in public. I've sent more than 25 of these reports so far. Some teams shipped a fix the same day, and two agreed to let me write up what happened. Kagelin credits GuardLayer in its v1.51.1 release notes.
What I hold GuardLayer to
- Read-only. The live check reads policies, grants and settings, never your rows.
- Nothing kept. Code and snapshots are checked in memory and discarded.
- Honest about limits. GuardLayer reports problems and confirms fixes. It doesn't silently block anything, and a scan doesn't replace a review.
Get in touch
Questions, a security hole you'd like a second pair of eyes on, or feedback on the tool: write to contactsolvion@gmail.com. I read and answer everything myself.
Check your own project
Connect Supabase read-only and see what an outsider could reach. About a minute, free.
Check my Supabase project