Skip to content
Get early access

Install

Cendarum is v0.1.0 and pre-launch. Nothing is code-signed or notarised, which means every installer we could hand you today would trip Gatekeeper on macOS and SmartScreen on Windows, and the instructions for getting past those warnings are exactly the instructions an attacker would want you in the habit of following.

For a product whose entire argument is “don’t trust us, check the architecture”, shipping an unsigned binary and telling people to right-click and choose Open is the wrong first impression. So we haven’t.

Signing, notarisation, and the installer matrix are on the roadmap. Until they land, access is by conversation: email us and say what you’d point it at.

A build for your platform, and a direct line to ask questions and complain. We are looking for around fifteen to twenty developers, because the thing we actually need to learn is whether the project-and-environment model matches how teams work — and that requires talking to people, not counting downloads.

Platform Status
macOS Full. Auto-lock responds to idle timeout, sleep, screen sleep, and screen lock
Windows The app and CLI work. Auto-lock on idle works; the sleep and screen-lock hooks are not wired up yet
Linux The app and CLI work. Same as Windows — idle timeout only

The idle timer is 15 minutes on every platform. The OS-level lock signals are what differ, and that difference is real rather than cosmetic: on Windows and Linux today, closing the lid does not itself lock your vault.

Cendarum keeps one encrypted file per machine. The desktop app and the CLI share it.

Platform Path
macOS ~/Library/Application Support/com.cendarum.app/vault.bin
Linux $XDG_DATA_HOME/com.cendarum.app/vault.bin
Windows %APPDATA%\com.cendarum.app\vault.bin

That file holds your public-key pins, sync version markers, and an encrypted copy of your account keys. It does not hold any secret value — see what works offline for what that implies, and the local vault file for what it means for a stolen laptop.

Set CENDARUM_DATA_DIR to point somewhere else if you want an isolated profile for testing.

Not available yet — the client repository isn’t public. Publishing it is on the roadmap, and the reason it matters is that it is the only way to verify the zero-knowledge claim rather than take our word for it. Until then, the security section is the most falsifiable thing we can offer: every cryptographic construction is written down, versioned, and named after the test that pins it.