Simple pricing for
every team size

Every state-changing operation (encrypt, decrypt, sign, key create/delete, ECDH derive) returns a tamper-evident JWS-signed receipt containing the actor, key reference, resource fingerprint, timestamp, and a cryptographic signature. Receipts are verifiable offline via the published JWKS — no call back to cloakapps required.

No. Start with just Cloak Files or Cloak KMS individually, then add more products as your needs grow. The bundle plans exist because teams often end up needing more than one product — bundles save 30–40% over individual purchases.

Keys stored in HSM plans never leave the hardware security module as plaintext. Cryptographic operations (sign, encrypt, decrypt) happen inside the HSM boundary. Even Cloak staff cannot extract your keys. Shared HSM plans use a multi-tenant partition; dedicated plans give you an isolated hardware partition.

Yes. Every product exposes MCP tools that any MCP-compatible AI agent (Claude, Cursor, custom LLM apps) can call. Operations require a human-approved policy before the agent executes. The Agent Business plan adds per-agent budget limits and a full audit log of every agent action.

Server-side PDF signing uses Adobe AATL-compliant certificates on all paid Batchsign plans. The Enterprise plan includes a dedicated AATL certificate in your organisation's name for maximum legal standing. Free and Starter plans use shared certificates.

Cloak operates on AWS Singapore (ap-southeast-1) with an optional EU region. Files are encrypted before leaving your network — Cloak never receives plaintext files. Metadata and audit receipts are stored in Cloak's Cassandra cluster. Enterprise customers can opt for on-premises deployment where no data leaves their network.