Evermesh is a video and music app. Browse and publish like you would
anywhere else — except every upload is signed and
content-addressed, so what you publish keeps
working even after the site that served it is gone. Verified in
your own browser before a frame plays. No company you have to
trust, including ours.
Experimental, not production-ready. There's no public
gateway yet and nothing to sign up for — the screenshots below are
the real apps, run against test data. See
honest status.
Scroll a gateway's mixed video-and-audio grid, or filter to just one.
Publish
Upload a video or track. Evermesh signs it and slices it into a content-addressed blob.
Verify
Every play checks the signature and re-hashes the bytes, client-side, first.
Take it offline
Pin what you care about in the desktop app; it plays with no network at all.
01
Three things make it survive
None of these depend on Evermesh, a gateway, or anyone in
particular staying online.
It's signed, not hosted
Every video and track is a small signed record plus a
content-addressed blob — proven by its own bytes, not by which
server handed it to you. Copy it anywhere and it still checks out.
Many doors, one pool
Independent gateways each index the same open pool of records,
under their own name and their own moderation call. Lose one
gateway and your media was never only there.
Kept by anyone who cares
The desktop app pins your library and re-verifies it locally, so
what you've saved keeps playing offline — no gateway, no
network, no company required.
That's the short version. Records, relays, chunk proofs, and the
rest of the mechanics are in the docs
→ Concepts.
02
Two real apps, not mockups
These are screenshots of the actual reference gateway and the
actual desktop client — the same code a gateway operator would
deploy, not a rendering of what it might look like someday.
The reference gateway — apps/gateway/web.
Every gateway that wants trademark compliance ships this
interface; operators re-skin the accent colour, not the layout.
The desktop client — crates/evermesh-node
(Tauri 2). Browses a gateway, verifies every manifest natively
in Rust, and pins video and audio for offline playback.
Both are rendered against test fixtures, because no Evermesh
gateway is deployed and there is no built desktop binary to run
against a live network yet — see what actually
exists. They show the real interfaces, not a running network.
03
However much you want to take part
Every rung below is optional, useful on its own, and reversible.
01
Viewer
runs: a browser
Watches or listens, with signatures and hashes verified client-side while it plays. No account, no setup.
02
Node
runs: a background app
Pins what you choose — your own uploads first — so it keeps playing offline. No domain, no public duties.
03
Gateway
runs: a public website
An independent site that indexes and serves its own selection, under its own moderation policy and jurisdiction.
A creator is just anyone with a key who publishes something —
including you; creators can run a node or a gateway too. A
foundation stewards the spec and the conformance suite, and runs
no servers of its own.
04
Where this actually stands
A page like this usually describes software that doesn't exist
yet. Here's the honest line, meant to stay uncomfortable while
it's still true.
Evermesh is pre-alpha. There's no public gateway, no
built desktop installer, and nothing to sign up for. Where code and
the spec disagree, the spec wins.
Built & tested
Protocol kernel — records, identity rotation, blobs and chunk proofs, all 27 record kinds.
The relay — sync protocol, subscriptions, gossip, blob sidecar.
Reference gateway — backend and web frontend: policy engine, ingest, the uniform UI shown above.
Desktop client — browses, verifies natively, pins for offline play.
Spec only — not built
Swarm / P2P retrieval — blob fetch today is the relay's HTTP sidecar only.
Live streaming — the record kinds validate; no ingest, no player.
Non-custodial keys — the reference gateway custodies keys server-side today.
Node-to-node seeding — the desktop client pins for its own owner only, not others yet.
Conformance: 189 deterministic vectors are replayed against
three independent runtimes — the Rust kernel, the WASM/TS
bindings, and a live relay. Zero failures anywhere; the WASM and
relay targets intentionally skip checks outside what they're each
responsible for (12 and 74 skips, by design, not by omission).
No, permanently. The spec has optional payment primitives so creators and gateways can charge for things if they want, but no protocol token exists or will exist.
Can something get taken down?
The substrate itself doesn't delete, but removal happens where it can actually be enforced: at the gateway that chooses what to serve, under its own jurisdiction. Moderation is a real, gateway-level job — see the gateway spec.
Can I use this today?
Not as a hosted product — no public gateway exists yet (see status). You can run your own relay and gateway from source today, or read the docs first.
Read the spec, or just clone it
Twelve normative spec files, a conformance suite, and reference implementations for the relay, the gateway, and the desktop client.
Code is MIT OR Apache-2.0; the specification is CC-BY-SA-4.0.
