When people started upgrading to PRO

I should ve felt great.

Instead, I felt Supaguard still wasn t feature-packed enough.

Hey Product Hunt

Over the last few hours, a lot more people signed up than I initially expected thank you for the incredible response

Because of that growth, I pushed a quick but important update:

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 upcoming improvements

• Direct influence on what we build next

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.

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.

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.