No payment keys on your servers
Your app calls /v1/proxy with its own API key. The gateway adds the provider's key to the request, so a stolen server holds nothing you need to rotate in a panic.
A sealed vault and API gateway for developers. Store each key once; the gateway adds it to your apps' outgoing calls, so a leaked app server leaks nothing worth stealing.
The problem
One leaked environment file, and the attacker holds them too.
Features
Your app calls /v1/proxy with its own API key. The gateway adds the provider's key to the request, so a stolen server holds nothing you need to rotate in a panic.
Each connection can allow only certain routes, a number of calls per minute and an amount per day. A refused call never reads the secret.
Every file is encrypted in 64 KiB chunks with its own key. Delete a workspace and its key is destroyed, so even old copies become noise.
Every key, secret, file and outside call is recorded with its request ID, each event chained to the one before by an HMAC.
User pools give your app passwords, tokens you verify with public keys and refresh tokens that work once. Feature flags turn things on for a share of users.
Your keys stay in the vault. Your apps only ever hold a key you can revoke at any time.
How it works
Save your payment provider's key as a secret. It is encrypted at once, and from then on nobody can read it back.
Create a connection to the provider's API with a policy: only these routes, at most this many calls and this much money a day.
Your app sends the request with its own API key. The gateway checks the policy, adds the provider's key and passes the answer back.
$ curl -X POST \ https://gateway/v1/proxy/payments/charges \ -H "Authorization: Bearer $APP_KEY" \ -d '{"amount": 1849}'201 {"id": "ch_7f3a91", "status": "succeeded"}# the payment key was added by the gatewaySecurity you can check
Every change runs the full test suite and three security scanners before it can merge.
Questions
No. Secret values are write only: no route in the API or the dashboard returns one. The only code that decrypts a value is the gateway adding it to an outgoing call. If you forget a value, rotate it.
Point the calls you make to the outside API at /v1/proxy/<connection>/... on the gateway and send your app's own API key. The gateway adds the provider's key and returns the provider's answer.
Revoke it in the dashboard and it stops working on the next request. Until then, rate limits for each key and the connection's policy cap what it can do, and every call is in the audit log.
The vault starts sealed. Its master key exists only in memory, so after a restart three of five key holders must each give their share before secrets, file downloads or sign in work again.
Each file is encrypted before it reaches the disk, in 64 KiB chunks with its own random key. That key is wrapped by your workspace's key in the vault, and file names are kept out of the stored data.
Its encryption key is destroyed first, so every secret and file key in it can never be decrypted again, even from a backup copy. Then its data, connections, user pools and flags are removed.
Yes. The audit log lists every sensitive action with its outcome, request ID and source IP. Each event carries an HMAC over the one before it, so an edited or deleted event breaks the chain.
No. There is no billing and no card to enter. Create a workspace and every feature is available.
Free, no card needed. Your workspace is ready as soon as you sign up.
Create your workspace