A new home for online communities
Your data
should be
yours.
Jolt lets people share posts, files, and encrypted content without handing ownership to one platform. Change the app, switch relays, or host it yourself; your identity stays yours.
- Your identity
- Belongs to you
- Your links
- Keep working
- Your content
- Can have many copies
- Your apps
- Remain replaceable
01 / Why
When an app disappears,
your community shouldn’t.
Today, one company usually holds your account, your posts, and the list of people who know you. That makes leaving painfully expensive.
the app keeps your account,
your content, and your connections
- 01Your identity only works inside that app.
- 02Your links depend on its servers.
- 03Your audience lives in its database.
- 04Leaving often means starting again.
you keep the identity;
apps simply ask to use it
- 01Your identity exists outside any one app.
- 02Your links point to content you control.
- 03Many computers can keep copies available.
- 04You can change the interface without leaving.
02 / How it works
Alice shares.
Bob opens.
Jolt does the difficult work quietly in the middle: remembering who published something, finding a copy, and checking that nobody changed it.
Alice publishes
She shares a post, a file, or something encrypted.
Jolt proves it
Her identity leaves a tamper-evident note saying what she shared.
The network carries it
Alice, a friend, or a relay can provide a copy.
Bob opens it
His Jolt verifies Alice's signature and checks the fetched bytes against their content fingerprint.
Alice can change apps without losing her identity, her links, or her community.
Under the hood, signatures prove who published something and content fingerprints prove that the bytes are unchanged.
03 / Architecture
Two ways in.
One local authority.
Spoke gets a tightly scoped session. Console gets trusted admin access. Only the Jolt daemon holds your keys, signs changes, stores content, and joins the network.
Protocol series · seven experimental drafts
The protocol,
layer by layer.
Signed paths are the base. The RFC series also specifies device authority, multi-writer state, encrypted access, community membership and discovery, and the capability boundary between apps and the local daemon.
04 / Status
You can try it today.
It is still early.
Jolt can already publish, find, verify, and privately share content. Spoke uses it for profiles, posts, threads, and private messages. Setup and everyday use still need polish.
- Create and use a Jolt identity
- Publish content under stable links
- Fetch content from other nodes
- Approve what each app may do
- Share encrypted private content
- Use relays for discovery and availability
- Using one identity across several devices
- Easy invitations and first-time setup
- Clear recovery when a device is lost
- Rules for public relays
- Platform signing and notarization
- Independent security review
05 / Apps
Built on Jolt.
Owned by you.
Two apps already speak the protocol, and they prove the point: the same identity, the same content, the same connections, reachable from more than one interface. Both are open source and built with the Jolt SDK.
01
Spokesocial
Profiles, posts, threads, and encrypted private messages between Jolt identities. The reference for what a social app looks like when the network, not the app, owns the graph.
Visit site →
02
Pasteypastebin
Share the paste, keep the keys: public and encrypted snippets published under your identity, with stable links that outlive any single machine.
Visit site →Jolt Console · v0.3.21
Choose your platform.
Jolt Console includes the local node and the controls for identities, apps, relays, and published content. This release was published on 5 August 2026.
Early builds are not yet signed for every operating system. macOS may require you to allow the app in Privacy & Security.
Release notes ↗