🚀 Free PRO for Next 100 Users — PHFREE100USERS
We’ve been running this with early users over the last few weeks and the response has been super encouraging 🙌 So far, 30+ users have signed up, actively using the product and sharing feedback that’s already shaping our roadmap. To get more real-world usage and honest feedback, we’re opening up FREE PRO access for the next 100 users. 🎁 What you get Full PRO features (no limits) Early access to...
We built Supaguard.pro without asking for your secrets 👀
One thing we wanted to be very clear about with Supaguard.pro: 👉 We don’t ask for service tokens, API keys, or credentials. Ever. Supaguard only looks at what’s already public on the internet. If an endpoint, config, or anon key is accessible without logging in, Supaguard can see it. If it needs authentication or a private token, Supaguard simply ignores it. Why we designed it this way Most...
🚀 We hit Top 10 on Product Hunt — and started building features users asked for
Quick update from the Supaguard launch 👋 We were lucky to land in the Top 10 on Product Hunt 🎉 — totally unexpected and honestly motivating. Even better was the feedback. One of the most requested features was real-time alerts, especially Slack notifications 🔔 when something sensitive is exposed. We’ve already started building Slack alerts so teams can catch accidental Supabase exposure as it...
I kept seeing Supabase apps accidentally leak data — so I built Supaguard a small scanner
I’ve been working with Supabase for a while and kept noticing the same issue across different projects: apps unintentionally exposing data. Not hacks — just things like: Tables left public during testing RLS policies changed once and never revisited Old service keys still active Even teams following “best practices” miss these occasionally. To solve this for myself, I built Supaguard — a small...
