Protect Your Supabase API Keys

Q: How do I protect my Supabase API key?

ShieldKey wraps your Supabase API key in a proxy token. Your real key stays encrypted — team members use revocable shield tokens that can be disabled in one click, without rotating the underlying key.

Q: Can I use ShieldKey with the @supabase/supabase-js SDK?

Yes. ShieldKey works as a drop-in proxy. Point your @supabase/supabase-js SDK at proxy.shieldkey.io and use a shield token instead of your real API key. No code changes beyond the base URL and key.

Q: What happens to my Supabase key if a team member leaves?

Revoke their shield token instantly from the ShieldKey dashboard. Your real Supabase key stays active — no rotation, no downtime, no re-deploying secrets across services.

Before & After

See how ShieldKey protects your Supabase integration with minimal code changes.

Before — raw Supabase key

import { createClient } from "@supabase/supabase-js";

const supabase = createClient(
  "https://abc.supabase.co",
  "eyJhbGciOiJ..."  // ← service role key (bypasses RLS)
);

const { data } = await supabase.from("users").select("*");

After — ShieldKey proxy token

import { createClient } from "@supabase/supabase-js";

const supabase = createClient(
  "https://proxy.shieldkey.io/supabase",
  "sk_shield_t_9a4d..."  // ← revocable proxy token
);

const { data } = await supabase.from("users").select("*");

What ShieldKey Does for Your Supabase Keys

Instant Revocation

Disable any team member's access to your Supabase key in one click. No key rotation. No downtime. No re-deploying environment variables.

Spend Limits

Set per-token spend caps so a compromised token can't run up your Supabase bill. Get alerts before limits are hit.

IP Allowlisting

Restrict each shield token to specific IPs or CIDR ranges. Even if a token leaks, it's useless from unauthorized networks.

Full Audit Trail

See every API call made through your Supabase key — who made it, when, from where, and what they accessed.

Zero-Knowledge Encryption

Your Supabase key is encrypted with AES-256-GCM. It's only decrypted in memory during request proxying — never stored in plaintext.

Team Access Control

Issue individual shield tokens to each team member. When someone leaves, revoke their token — everyone else keeps working.

FAQ

How do I protect my Supabase API key?

Add your Supabase key to ShieldKey's encrypted vault. ShieldKey generates a proxy token (starting with sk_shield_t_) that your team uses instead. Your real eyJ key stays encrypted and is never exposed to team members.

Can I use ShieldKey with the @supabase/supabase-js SDK?

Yes. Point your @supabase/supabase-js SDK at proxy.shieldkey.io and use a shield token instead of your real API key. The SDK works identically — ShieldKey transparently proxies every request.

What happens to my Supabase key if a team member leaves?

Revoke their shield token from the dashboard. Your real Supabase key stays active — no rotation, no downtime, no re-deploying secrets across services. Everyone else keeps working without interruption.

Does ShieldKey add latency to Supabase API calls?

ShieldKey's proxy adds less than 25ms at the p50. The proxy decrypts your key in memory, forwards the request, and streams the response back. For most Supabase API calls, this overhead is negligible.