Veristria

Ecosystem

Three surfaces where fast shipping goes quiet

Three independent security products for AI-assisted teams: exposed API keys in client-side JavaScript bundles, Supabase row-level security that has drifted from the schema, and Stripe Connect fee leaks. Each has its own domain, pricing and roadmap. What they share is a refusal to report anything they cannot prove.

Secret exposure

KeyDrift

Finds the API keys and secrets that AI coding tools leave behind in client-side JavaScript bundles.

keydrift.devAboutBlog
Backend posture

VibeGuard

Continuous RLS testing, schema-drift detection and security monitoring for Supabase backends.

usevibeguard.comAboutBlog
Revenue integrity

FeeGuard

Real-time detection and recovery of silent fee leaks in Stripe Connect platforms.

feeguard.devAboutBlog
Secret exposure

KeyDrift

Finds the API keys and secrets that AI coding tools leave behind in client-side JavaScript bundles.

The problem
Build-time environment variables inline their values into the JavaScript bundle. An .env file that is correctly git-ignored still ships its contents to every visitor, and no repository scanner will ever see it.
What it does
KeyDrift reads the JavaScript your site actually serves, not your source tree, and identifies Supabase, Stripe, OpenAI and AWS credentials in it — while recognising the publishable keys that belong there and are not leaks.
Who it is for
Solo founders and small product teams shipping AI-assisted frontends on Vercel, Netlify and similar.
How you can check it
Findings carry a masked prefix and a fingerprint. Live secrets are never stored, and the first scan needs no account.
Visit keydrift.devAbout KeyDriftKeyDrift blog
Backend posture

VibeGuard

Continuous RLS testing, schema-drift detection and security monitoring for Supabase backends.

The problem
Supabase makes the database directly reachable from the browser, and row-level security is the only thing standing between a public anon key and every row in the table. Policies drift as the schema does.
What it does
VibeGuard tests the policies continuously against the live project, detects schema drift as tables and columns change, and reports the specific query that returns a row it should not.
Who it is for
Teams building on Supabase, especially those whose schema is moving faster than their security review.
How you can check it
Every finding is a reproducible query. The free audit runs before any credential is connected.
Visit usevibeguard.comAbout VibeGuardVibeGuard blog
Revenue integrity

FeeGuard

Real-time detection and recovery of silent fee leaks in Stripe Connect platforms.

The problem
On a Stripe Connect platform, a refund, dispute or FX movement can leave the connected account paid while the platform absorbs the loss. Nothing errors; the money is simply gone.
What it does
FeeGuard reconciles charges, transfers, application fees and disputes in real time, flags the discrepancies, and can reverse the ones that qualify automatically.
Who it is for
Marketplace and SaaS platforms running Stripe Connect at enough volume that manual reconciliation has stopped being viable.
How you can check it
Each discrepancy links to the underlying Stripe objects, and the connection uses a restricted key scoped to the reads it needs.
Visit feeguard.devAbout FeeGuardFeeGuard blog

Coverage

Why three products rather than one platform

The three surfaces are genuinely different problems with different buyers, different credentials and different failure modes. Bundling them would mean asking a Supabase team to pay for Stripe reconciliation they will never use, and it would mean one product’s outage taking the other two down. They stay separate.

What they share is the parent: one contact address, one standard for what counts as a finding, and one set of writing. Questions about any of them reach us at info@getveristria.com.