About Supaguard

Supaguard was built after repeatedly seeing the same problem across Supabase projects: accidental data exposure.

Not breaches. Not hacks.

Just small misconfigurations — public tables left open, relaxed RLS rules, or sensitive fields that quietly became accessible over time.

Even teams following best practices miss these things.

What it does

Supaguard acts as a second set of eyes for Supabase projects — focused on catching accidental exposure caused by configuration drift.

Public tables

Find tables/endpoints readable without auth

PII signals

Spot fields that look like sensitive data

Risky keys

Detect hardcoded or over-privileged keys

Why Supaguard exists

While working in application security and auditing SaaS products, I reviewed many real-world systems where sensitive data (PII, PCI, API keys) was exposed unintentionally. In most cases, developers simply didn’t realize it had happened.

Supaguard was created to act as a second set of eyes.

It scans Supabase projects and highlights:

  • Publicly accessible tables and endpoints
  • Potential exposure of PII or sensitive data
  • Risky or hardcoded keys

The goal isn’t to replace secure development practices — it’s to catch what humans miss.

Who’s behind Supaguard

I’m Vikas Anil Sharma, an offensive security leader and the founder of Agilehunt.

I’ve worked closely with startups and SaaS teams, helping them identify security gaps before they turned into incidents. My work has involved application security testing, business logic reviews, and helping teams understand how real-world attackers think.

I’ve also been recognized for contributing to security education and awareness, including a letter of appreciation for participating in workshops under India’s National Education Policy (NEP) focused on cybersecurity and digital sciences.

Supaguard is a direct outcome of that experience — built from real issues, not theoretical ones.

Built for developers

Supaguard is intentionally simple:

  • No complicated setup
  • No long onboarding
  • No noise

Connect your Supabase project, run a scan, and see what needs attention.

Our approach

Practical

Security should be practical — not overwhelming

Visible

Visibility beats assumptions

Preventive

Prevention is cheaper than response

Supaguard is continuously evolving based on real feedback from developers using it in production.

Get in touch

If you’re using Supaguard and have feedback, questions, or feature ideas, I’d genuinely love to hear from you — vikz@agilehuntlabs.com.

This product is built in public — and shaped by the community using it.