cryptomator

cryptomator/cryptomator

Cryptomator for Windows, macOS, and Linux: Secure client-side encryption for your cloud storage, ensuring privacy and control over your data.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 16, 2026
today
Ship score
90/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 16,061 → 16,297 (Sep 1 – Oct 13, 2026)
+170 stars in the 28 days to 2026-10-13

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
16.3K
Forks
1.5K
Open issues
281
Watchers
207
Primary language
Java
Created
Feb 2, 2014
Owner
cryptomator · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 33 startups in the directory ship primarily in Java.

Topics

#cloud-storage#crypto#cryptography#cryptomator#encryption#java#privacy#security

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 92%, self-hostable 25%, hosted offering 21%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-16This is the badge for cryptomator/cryptomator, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/cryptomator/cryptomator.svg)](https://ossean.com/cryptomator/cryptomator)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.