Your apps call any API without ever holding the key

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.

Create your workspaceFree, no card needed
  • 256 bit AES on every secret and file
  • 3 of 5 key holders to unseal
  • Every change in a chained audit log

The problem

Every app server holds the keys to your payment provider

One leaked environment file, and the attacker holds them too.

Keys in every app

  • Each server and laptop has a copy of the live payment key
  • A leak means rotating the key everywhere, in a hurry
  • Nothing stops a stolen key from charging any amount

Keys in the vault

  • Apps hold only their own API key, which you can revoke
  • The gateway adds the provider's key to each call and never returns it
  • Policies cap routes, calls and amounts before the key is read

Features

What changes when the keys leave your apps

  • 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.

  • Limits before the key is touched

    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.

  • Files nobody can read from the disk

    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.

  • A log that shows when it was edited

    Every key, secret, file and outside call is recorded with its request ID, each event chained to the one before by an HMAC.

  • Sign in and rollouts for your own users

    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

Three steps, and the key never leaves the vault

  1. Store the key once

    Save your payment provider's key as a secret. It is encrypted at once, and from then on nobody can read it back.

  2. Connect it and set limits

    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.

  3. Your app calls through

    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 gateway
Your app only ever sends its own API key, which you can revoke.

Security you can check

Built, tested and scanned by its own pipeline

Every change runs the full test suite and three security scanners before it can merge.

automated tests run on every change
900+
security scanners in CI: Gitleaks, Semgrep, Trivy
3
key holders needed to unseal the vault
3 of 5
routes that return a secret value
0

Questions

What people ask before they move their keys

Can anyone read a secret back after I save it?

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.

What does my app need to change?

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.

What happens if an app's API key leaks?

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.

What happens when the server restarts?

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.

How are files stored?

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.

What happens when I delete a workspace?

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.

Can I see who did what?

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.

Does it cost anything?

No. There is no billing and no card to enter. Create a workspace and every feature is available.

Stop handing payment keys to your apps

Free, no card needed. Your workspace is ready as soon as you sign up.

Create your workspace