INTEGRATION · SUPABASE
Your service-role key never leaves your project.
You deploy a small Edge Function in your own Supabase project. It exports the minimum entitlement fields and signs each snapshot. SubSync Guard verifies the signature and a one-time nonce.
What the connector exports
A narrow shape: customer or user identifier, entitlement state, plan or tier, and a complete-snapshot flag. No passwords, no payment data, no unnecessary fields.
- Customer or user identifier
- Entitlement state (active, inactive, trial, etc.)
- Plan or tier identifier
- Complete-snapshot flag and row count
- Capture timestamp
How signing works
The connector computes HMAC-SHA256 over timestamp, nonce, and raw body. SubSync Guard verifies the signature in constant time, checks the timestamp is within five minutes, and enforces nonce uniqueness with an atomic primary-key constraint.
- HMAC-SHA256 with a per-integration secret
- Timestamp TTL of five minutes
- Atomic nonce replay protection
- Body size limit of 5 MB and 50,000 rows
- Constant-time signature comparison
Deployment
An example connector is provided under examples/. It is a starting point, not a managed agent. The customer remains responsible for scheduling, monitoring, and securing their deployment.
Frequently asked
Does SubSync Guard receive my service-role key?
No. The connector runs in your project. Only the signed snapshot is sent.
What if the signature is invalid?
The request is rejected with no data written. The nonce is not consumed.
Can I use a database other than Supabase?
The connector contract is HTTP-based. Any system that can produce a signed JSON payload can integrate.