rypt

Not yet independently verified. The launch date rests on the maker’s own launch post of 25 September 2026, in which the maker asks for people to test the service, and on terms that took effect the same day. The security claims are the vendor’s own, and no independent report of the product was found. We will update this when it can be confirmed, and remove this note.

rypt is an encryption API from x6c LLC, a West Virginia company, shown by its maker on 25 September 2026, the same day its terms of service took effect. An application sends plaintext to one HTTPS endpoint with a bearer token and receives ciphertext, and does the reverse to decrypt, so a developer can encrypt a database field without setting up key rings or cloud permissions. It can also wrap, unwrap and rewrap data keys, accepts additional authenticated data to bind a value to a row, file or tenant, and writes an append-only audit record of every operation on a key. Keys are held in Google Cloud’s key management service in the us-central1 region: free and extra keys are stored wrapped under a hardware-protected root key, while paid Software and Hardware keys are dedicated keys. Pricing on its own page is per key: one free key with 10,000 operations a month, then $3, $10 and $35 a month per key with 50,000, 100,000 and 250,000 operations included and metered charges beyond. The service states that it is not zero-knowledge — plaintext reaches rypt to be encrypted and rypt holds the keys — and its terms give no uptime guarantee. A buyer should weigh that against a key management service in its own cloud account, and note that rotating the free key makes data encrypted under its earlier version undecryptable.