HAVEN
Humanely Attuned Virtual Ecosystem Nexus

Human sentric ecosystem

HAVEN is open infrastructure for a digital life on human terms. Your identity, your data and your relationships are held by you, shared by choice, and backed by cryptographic proof, not by blind trust in a platform.

Conference Bank Hospital University Shop you
From chain to network

A richer, more empowering internet

On today's platforms, value flows one way: people give their data in, the platform keeps it, and the value flows out to whoever pays. Every new service starts from zero, behind its own wall. In HAVEN, people hold their own data and connect directly, so value can be created at every connection, and what you bring to one service can be reused, with your consent, in the next. Lots more value is generated.

Value chaintoday's platforms
Advertisers & data buyers Advertisers & data buyers $$ sold on$ $ $sold on$ $ $ Platform A extracts the value Platform B starts from zero no portability yourdatayourdata people
People at the bottom supply the data. The platform extracts the value and sells it on. Each silo rebuilds who you are from scratch, and you can't take it with you.
Value networkHAVEN
Conference Bank Hospital University Shop you
No centre to capture the value. People and services connect directly, and every connection create value for both sides.
Six principles

What it means to build on human terms

Distributed

Nobody sits in the middle, so there's no single company, server or switch that everything depends on. Your information lives with you, in your own cell, and travels straight to the people and services you choose. Nothing has to pass through someone else's hands, and if one part drops out, the rest carry on.

Individual-centric

You are the starting point, not the product. Services come to your data, with your permission. Your data doesn't go to them.

Open source

Every line is public, licensed MIT / Apache 2.0 and CC-BY, and stewarded by Digipomps, a Norwegian foundation. You don't have to trust it blindly, because you can inspect all of it.

Portability

Your identity, data and relationships move with you. Leaving a service doesn't mean leaving your history behind, and the next service doesn't start from zero.

Digital sovereignty

Having full control and ownership over your own data, infrastructure, and technology choices, independent of external vendors or foreign legislation.

Trust

Verifiable credentials are digital proofs, like a stamped certificate in your pocket. A trusted party signs a claim about you, such as a ticket or a degree. You hold it and show only what's needed, and anyone can check it's genuine without calling the issuer.

See how trust is proven →
Together, without being watched

Collective digital consciousness

Every person is their own cell. Some choose to share a small part of what they know, and together it forms a picture none of them could see alone. Nobody collects it on their behalf, and nobody watches from outside.

01Yours first. Everything starts in your own cell and stays there unless you decide otherwise.
02Share a little, on your terms. You pick what to add, and you can take it back.
03Seen by those who give. The picture is visible to the people who helped make it, not to a platform.
the sharedpicture shared by choice kept private
Trust you can verify

Not promises. Proofs.

Platforms ask you to trust their terms. HAVEN replaces roles and server permissions with capabilities and contracts: explicit, scoped grants that are cryptographically signed. Anyone involved can check who asked, what was granted, why, and for how long.

  1. 01A request carries its purpose. Every action states the intention behind it.
  2. 02You grant exactly what's needed. The grant is limited in scope and time, and signed with your key.
  3. 03Both sides keep the proof. The proof can be checked later by anyone involved, with no server needed.
Contractsignature verified ✓
fromcell · community key 7d02…e19c
tocell · service key 31bb…04af
purposeSuggest people working on the same topics at this gathering
capabilityread · interests
scopethis domain only
expiresafter 3 days
signature9f3a 1c7e 44d0 …… b812 c21e

Illustrative example. Field names follow HAVEN's contract model; the values are made up.

Under the surface

Small at the core. Human at the top.

At the heart of HAVEN is CellProtocol, a deliberately tiny, explicit and deterministic model for identity, authorisation, data flow, events and collaboration. It has no hidden magic and no implicit state, so the same input gives the same behaviour across time, machines and networks.

PurposeIntentions, goals and reasons for every action. It lets people collaborate without surveillance or scoring.
Contracts & capabilitiesAccess that is explicit, auditable and cryptographically justified, in place of roles and server-side permissions.
Domain identityA different key in every community and no global user ID, so nobody can link your life together across them.
EnvelopesEvery message is sealed in an envelope that can travel over any transport, online or off.
CellProtocolA minimal, deterministic core with stable semantics and behaviour that can be replicated and audited.
Envelopes travel over WebSocket QUIC WebRTC shared file system radio links USB sticks offline bundles

Built from Cells

HAVEN is built from Cells: self-contained units of state and behavior whose entire public surface is explicit.

Meddle contractAll state access goes through get/set, and every call carries an Identity. There are no side doors.
InterceptorsBehavior is added by registering get/set intercepts on the first keypath segment, then routing inside the cell.
FlowCells publish changes as FlowElements through a validated emit(). Replay lets late subscribers catch up.
ResolverLifecycle and capability-based access control are enforced centrally, not per app.
TransportBridges (WebSocket, IPC and others) move payloads between runtimes but never define their meaning.
SkeletonUI is serialized as data over flow, so Swift, web and other renderers can draw the same surface.

Because every cell honors the same contract, independently built cells compose into larger systems.

one feed outlistens to many

It works where the network doesn't, for the people who need it most.

Humanitarian work

Coordinate in the field, sync when there's a link.

Emergency preparedness

Keep working in closed or disconnected environments.

Education

Learning systems that don't depend on stable internet access.

Local communities

Own the digital infrastructure you gather around.

Open, and built to last

Infrastructure that outlives any company. Including ours.

HAVEN is developed in the open, in public repositories, and stewarded by Digipomps, a Norwegian non-profit foundation. It is designed for a lifespan of 30 years or more, so it won't disappear because a commercial actor changes strategy. It belongs to everyone who uses it.

MIT Apache 2.0 CC-BY Digipomps foundation · org. no. 922 135 134
Explore the code on GitHub Read the CellProtocol spec

Join the foundation

Leave your email and we'll be in touch about how to take part in HAVEN and the Digipomps foundation. We only use it for that. Prefer to write to us directly? kjetil@digipomps.org.