Your devices.Your own cloud.
Havenfold turns the devices a family or a small business already owns into their own end-to-end encrypted cloud, with no accounts and no centre.
Havenfold demo · a real run
✓Started 2 devices: Alex's phone, Maya's phone (no accounts: each device makes its own keys)
✓Alex created family "Rivera" (a new signed ledger on Alex's phone)
✓Maya opened Alex's QR code; both phones showed the same 5 pictures
✓Both confirmed; Maya joined as a parent (168 ms)
✓Alex wrote a note; it appeared on Maya's phone in 27 ms: "Wi-Fi password is on the fridge"
✓The box keeps a sealed copy of the note but has no key for it
Every device is a separate process running the real core, on a local testnet (127.0.0.1). Pictures and timings change from run to run.
No accounts
Identity lives on the device. No server knows who you are.
Face to face
People join in person: a QR code, the same 5 pictures, signatures.
No centre
No main device or server. When one is lost, the community keeps working.
Sealed end to end
Relays only carry sealed envelopes. Even we cannot see your content.
Why
A drawer of devices that still work.
Most homes and small shops have an old laptop, a retired phone, a tablet nobody uses. Meanwhile their photos, documents and passwords live with cloud companies, and when a service shuts down or raises its prices, the data goes with it.
Havenfold gives each device a role. Each task runs on one device, and the largest task a community can run is always shown.
Your phones
Member devices. They approve, sign and hold vault shares. They are never workers.
An old laptop
Converted to Linux, it becomes the worker: OCR, backup and later transcription, in a container without network access.
An old Android phone
A box that keeps the community reachable, or an edge device such as a camera or a screen. Never both.
A Family Box
A Linux machine that stays on and holds sealed copies and vault shares. It never votes and never sees content.
How it works
People vote. Devices never do.
Every community, a family or a team, has a signed, hash-chained ledger of members, devices, roles and collections. Boxes, workers and cameras take part in no decision, so a stolen device cannot take over the community.
- 01
Create a community
The first phone makes a new signed ledger. No sign-up, no password reset, no server that knows who you are.
- 02
Join face to face
One phone shows a QR code, the other scans it. Both screens show the same 5 pictures, both people confirm, and a parent signs.
- 03
Share sealed records
Each change is encrypted and signed. Devices merge changes field by field and reach the same state in any order. When someone leaves, a new key epoch starts.
- 04
Hand work to a spare device
A phone gives a job to a worker. The worker checks it against the ledger, runs it without network access, returns the result and deletes its copy.
What Havenfold is not.
Devices share work, but Havenfold never pretends they are one giant computer. A cloud provider is only an optional accelerator the user chooses.
Not a cluster operating system
It does not merge the RAM and CPUs of several devices into one machine.
Not a cloud service
Data stays on the community's own devices.
Not an account system
There is no sign-up and no server that knows who you are.
Not a surveillance tool
Adults cannot be monitored in secret. No face recognition database, no per-employee tracking.
Not a new cryptosystem
Only libsodium and the widely used Holepunch libraries, with well-known algorithms.
Status
Written down first, then built.
More than 35 RFCs define the protocol, the layers and their limits, and the code follows them. It is tested on two runtimes. It has not been used for real yet.
Pre-alpha. Do not use Havenfold for real data. Interfaces and formats may change until the first tagged release.
Roadmap
Five phases, one core.
Phase 0 · Done
Founding
Founding document, the base RFCs and the repository. More than 35 RFCs approved.
Phase 1 · Now
Home Machine v0
Record, task and event packages, node software, OCR and backup tasks, erase mode. Next: real homes.
Phase 2 · Now
First product apps
Apps built on the core in separate repositories; transcription and local language model tasks.
Phase 3
Vault and expansion
Vault release, Installer USB for everyone, Windows, macOS and Raspberry Pi workers, an independent security audit.
Phase 4
Opening and hardware
Container apps, a local service tunnel, Home Assistant integration and dedicated boxes.
Built on Havenfold
Products on the same core.
Eser Teknoloji's products are built on Havenfold. They are separate, closed products; Havenfold is the open core underneath.
Open source
Several licenses, on purpose.
- Published code will not be relicensed under a more restrictive license.
- A free feature will not be moved to a paid tier.
- If the project is sold, the trademark and the repository go to a foundation.
- No patent applications: innovations are published openly. Contributions use the DCO; there is no CLA.
MPL-2.0
Core, phone package, node, installer
Ship the core inside a closed product; changes to the core's files must be published.
Apache-2.0
SDK, test vectors, task images
Anyone can implement Havenfold without hesitation. Includes a patent grant.
AGPL-3.0
Server-side reference code
The service receiver today; later the Mailbox and the relay.
CC BY 4.0
Documentation
The founding document, the RFCs and the guides.
Questions or contributions?
The repository is open on GitHub. Read the code, open an issue, or write to us about the project, the protocol or the licenses.