COMMUNITY EDITION

Core0 on one machine, free

Coming soon. Community Edition has not been released yet. This page describes what it will be, and is published early so you know what to expect.

A self-hosted vault for personal data. Your application stores a token; the real value never leaves the machine you control. Core0 receives nothing, phones home to nobody, and has no vendor endpoint to compromise. Community Edition is that whole architecture on a single machine — meant for testing before you buy, and for running something small at home.

What you get

• PII tokenisation — field-level encryption, with the key layer separated from the data layer
• Tamper-evident audit log — every entry carries a sequence number and the hash of the one before it
• Data export — your records out, under your own export key, whenever you want
• Connector and API — the same integration surface as the paid editions
• Admin panel — record counts, service health, certificate expiry, audit search

Everything runs in containers on one node. The licence included runs for ten years.

The limits, plainly

150 new tokens per day. A hard cap, not a nag screen. Reads are not limited; only the creation of new tokens is. If you are protecting real customer data at any volume, you have outgrown this edition — which is what it is for.

One node means no replication and no failover: if the machine goes down, the vault is down until you bring it back. Everything else about the architecture is identical to Starter. ObsydiaFiles, the document store, starts at Pro.

What you need

• Ubuntu 24.04 LTS or 22.04 LTS, ideally a fresh install
• A static address on your network
• Internet access during installation, for the download

Hardware requirements are being measured and will be published here on release. Do not size a machine from guesswork until they are.

Installation is a single command that pulls what it needs and brings up the containers. From there the wizard runs in your browser — the same one the paid editions use, showing you the log as it goes. See what that looks like.

The key ceremony applies here too

At the end of the install, Core0 generates the master encryption key and splits it into three Shamir shares. Two of the three reconstruct it. The shares are displayed once, and nobody at Obsydia ever sees one — we cannot read your data and cannot be compelled to hand over a key we do not have.

The other side of that guarantee is blunt: lose two of the three shares and the data is gone, for you and for us. There is no vendor override, because a vendor override is exactly the thing this design exists to remove. Even at home, keep the shares apart — a password manager and two pieces of paper in different places is enough. All three in one drawer defeats the scheme entirely. If you want a copy that survives losing the vault, use the export.

When you outgrow it

Starter is the same software across three nodes, which is what makes the separation real: data and keys stop living on the same machine. Pro adds ObsydiaFiles. Enterprise adds replication and failover. Work out what a metered vault would cost you over the same year.

One email when it is downloadable

Nothing else, ever.