BenchRank
#8 in Secrets & Key ManagementUpdated 2026-08

Cryptomator

by Cryptomator · Client-side AES-256 encryption for files held in any cloud

BenchRank score

43.6 — BenchRank score out of 100

Screenshots of Cryptomator

Homepage · Cryptomator

Homepage of Cryptomator

Overview

Cryptomator encrypts cloud-stored files on the client side. You set a password on a folder, called a vault, and open it as a virtual drive; files moved onto that drive are encrypted automatically, filenames included, using AES with a 256-bit key. Cryptomator Hub adds centralised key management, user and group management, and audit logs for teams.

Best for
Individuals and teams wanting client-side encryption of files kept in any cloud storage service
Pricing
Desktop use is free, mobile apps and desktop dark mode are one-off purchases from €29.99 per platform, and Cryptomator Hub Standard is €12.00 per seat per month excluding VAT, with a free self-hosted Community edition and custom Enterprise pricing.
Runs on
iOSAndroidmacOSLinux

Strengths and trade-offs

Strengths

  • Open source, with independent security audits noted
  • Encrypts file contents and filenames with AES 256-bit keys
  • Works with any cloud storage; unlimited vaults on the free plan
  • Self-hosted Hub Community edition is free for 5 seats

Trade-offs

  • Android and iOS apps are separate one-off €29.99 purchases per platform
  • Dark mode on desktop is a paid upgrade from €29.99
  • Free individual plan comes with community support only
  • Hub Enterprise pricing is not published; you must contact sales

How Cryptomator markets itself

A structured read of the promise, proof and page design on Cryptomator’s captured homepage.

Homepage capture

“Protect your Cloud Data”

  • Angle: Security / trust-led
  • Hero: Illustration

Pricing

Published plans and prices from Cryptomator’s own pricing page.

How this score is made up

Each dimension is scored out of 100 and combined into the headline score using fixed weights.

  • MCP support

    Whether an agent can drive the product through the Model Context Protocol, and how much setup that takes.

  • API quality

    Public API surface: machine-readable spec, official SDKs, documented auth, errors, rate limits and versioning.

  • Documentation

    Publicly reachable docs — coverage, freshness, code samples and machine readability.

  • Agent friendliness

    How readable the site is to an automated client: llms.txt, structured data, server-rendered content, crawler access.

  • Pricing transparency

    Whether real prices are published, self-serve signup exists, and usage costs are knowable without a sales call.

  • Customer sentiment

    Third-party ratings, shrunk toward the catalogue mean by review volume and corroborated across independent sources.

  • Changelog

    A public, dated record of what shipped and when — the clearest signal that a product is still alive.

  • Marketing site structure

    Whether the site answers a buyer's questions: clear positioning, the pages that matter, and accessibility.

  • Page speed

    How fast the site loads for real visitors: Chrome UX Report 75th-percentile LCP, INP and CLS, with a Lighthouse mobile run standing in where a site has too little traffic for field data.

  • Operational trust

    Status page and incident history, security disclosure, compliance and data-processing documentation.

Measured, but not part of the score

Useful to know, but not a mark for or against the product — so these do not affect the ranking.

  • Openness

    Source availability, self-hosting, data export and open standards. Scored and shown, but not part of the composite — paid SaaS is not worse for being paid SaaS.

  • Maintenance

    Release cadence and repository activity. Scored and shown, but not part of the composite — it is only measurable for open repositories.

This doesn’t look right — report a problem with Cryptomator’s score

Where this comes from

The Cryptomator pages BenchRank reads when it scores the product — its documentation, release notes, status and security pages, and its repository where there is one.

Alternatives in Secrets & Key Management

  • Ranked 1

    71.4 — BenchRank score out of 100

    Infisical

    Infisical · Secrets, certificate and privileged access management for developers

    Best for: Engineering teams wanting secrets, certificates and privileged access managed on one platform

  • Ranked 2

    66.7 — BenchRank score out of 100

    Unkey

    UnKey · API deployment, gateway and observability on one platform

    Best for: Teams that want API deployment, key auth, rate limiting and logs from a single vendor

  • Ranked 3

    61.8 — BenchRank score out of 100

    Vault

    HashiCorp Vault · Secrets management and encryption as a service via UI, CLI or HTTP API

    Best for: Security and platform teams storing secrets, issuing database credentials and encrypting data

See all 17 alternatives to Cryptomator

Is this your product?

Claim Cryptomator to manage its profile. Claiming lets you suggest edits to the descriptive fields — it never changes scores or rankings.

Claim this business

Report a problem with this page

Report an issue with Cryptomator