en-decrypt

Field-level encryption API

Field-level encryption API

The encrypted value stays with you. Keys stay with us.

Encrypt private strings through an API. We return one value for one column. You never handle keys. Decrypts are free.


    

This demo runs in your browser and returns one envelope. Production looks the same: one envelope in one column. Demo keys are not production keys. Encrypts you do not use still count — they go in your bank, including on Free (up to two months). Never lose what you pay for.

Never lose what you pay for.

Unused encrypts stay in your bank

Each month you get included encrypts. What you do not use moves to an account bank — Free included, up to two months of the included amount (20,000). Paid plans have no bank cap. A busy month on a paid plan takes from the bank before we charge overage. Free cannot spend the bank to pass its hard cap. After you upgrade, the bank is there to use. The bank does not expire while the account is open.

  1. 1

    You get included encrypts

    Each plan includes a monthly allotment. Decrypt, update, and delete stay free.

  2. 2

    Leftovers go in the bank

    At month end, unused included encrypts move to your account — including on Free, up to two months’ worth. They stay yours after you upgrade.

  3. 3

    Busy months use the bank first

    On a paid plan, extra encrypts come from the bank before overage. Free cannot spend the bank past its hard cap.

Never lose what you pay for.

The usage dashboard

Each month you get included encrypts. Unused ones bank on your account, including on Free — up to two months (20,000). A busy month on a paid plan takes from the bank before overage. Free cannot spend the bank past its hard cap. Named keys keep their own daily counts. Set an alert on any key.

  • 1. You get included encrypts

    Each plan includes a monthly allotment. Decrypt, update, and delete stay free.

  • 2. Leftovers go in the bank

    At month end, unused included encrypts move to your account — including on Free, up to two months’ worth. They stay yours after you upgrade.

  • 3. Busy months use the bank first

    On a paid plan, extra encrypts come from the bank before overage. Free cannot spend the bank past its hard cap.

  • Alerts on a named key

    Set a number on any API key you created. When that key’s encrypts this month pass the number, the dashboard records an alert.

  • 30 days · Free

    A month of daily encrypt and decrypt counts.

  • 90 days · Launch and Growth

    A quarter of daily counts, still split by API key.

  • 365 days · Business and Capacity

    A full year of daily counts.

History is the dashboard window, not a copy of the envelopes you store.

Questions teams ask

What is a field-level encryption API?
You send a private string. You get one encrypted value. Store it in the same column. Keys stay with us.
Do decrypts count toward my plan?
No. Only encrypt operations are billed. Decrypt, update, and delete are free.
Is there a free plan?
Yes. 10,000 encrypts and 1,000 strings, demo keys only, card required before membership.
What happens to encrypts I do not use?
Never lose what you pay for. Unused included encrypts move to an account bank, including on Free — up to two months of the included amount (20,000). Extra encrypts on a paid plan come from the bank before overage. Free cannot spend the bank to pass its hard cap. After you upgrade, the bank is there to use. The bank does not expire while the account is open. If you cancel, encrypted values and the unused-encrypt bank stay for 90 days unless you choose to delete them immediately.
Can I get an alert when one API key is used too much?
Yes. Set a number on any named key for encrypts this month, for active strings that key holds, or both. When a number is passed, the dashboard records an alert.
What is 30, 90, or 365 day history?
How far back the usage dashboard keeps daily encrypt and decrypt counts, split by named API key. Free keeps 30 days, Launch and Growth keep 90, Business and Capacity keep 365. It is not a copy of the envelopes you store.
Can I encrypt a whole object as one string?
Yes. Encrypt a JSON object or JWT as one plaintext so one encrypt covers many fields.