Portable identity
Keep the same cryptographic identity across nodes, devices, and applications.
RESONANCE
Own the route.
User-owned routing infrastructure
for humans, machines, and AI agents.
Run encrypted relay nodes.
Keep portable cryptographic identities.
Build communication apps
without centralized trust.
Open protocol Replaceable nodes Portable identity Fallback-ready
Product proof
Run your own communication node.
The first version of Resonance is not another chat app. It is a routing primitive: a CLI, a relay node, and portable cryptographic identity.
$ resonance init
$ resonance node start
$ resonance send @alice "hello"
$ resonance inbox
$ resonance migrate --to node-bEncrypted relay
Route packets through nodes that do not own plaintext or user identity.
Node migration
Move between self-hosted, community, or managed nodes without losing reachability.
Architecture
The node routes. The user owns.
A Resonance identity is a cryptographic keypair, not a phone number, workspace, username, or corporate account.
A Resonance node can relay, store, and forward encrypted packets. It should not own the user’s identity, plaintext, or social graph.
The route can change.
The identity persists.
The infrastructure is replaceable.
Stack
The Resonance stack.
Resonance Protocol
Open routing protocol for portable identity and encrypted delivery.
Resonance Relay
Software nodes that can run on a laptop, VPS, server, or data center.
Resonance Gateway
Physical nodes for homes, teams, labs, and communities. Local routing, mailbox storage, and sovereign reachability.
Resonance for Agents
Communication identities for AI agents, tools, devices, and services.
Long-term roadmap
The Phases
Phase 1 — Relay
The network begins as software.
Launch the CLI and open-source relay. Developers can create identities, run nodes, route encrypted messages, and prove that communication can move through infrastructure that does not own the user.
Phase 2 — Mesh
Independent nodes become a routing network.
Users, teams, and developers can run private, public, or managed relays. Applications can build on top of Resonance for secure delivery, alerts, internal communication, device messaging, and agent coordination.
Phase 3 — Gateway
The network gains metal.
Move communication infrastructure into physical space with plug-and-play Resonance Gateways for homes, offices, labs, and communities. Local routing, encrypted mailbox storage, and edge-owned reachability.
Phase 4 — Fallback
The network survives degraded infrastructure.
Integrate low-bandwidth fallback transports: LoRa, radio, local mesh, satellite links, and other channels for critical encrypted packets when normal infrastructure fails, is censored, overloaded, or untrusted.
Phase 5 — Sovereign Layer
The network becomes a communication substrate.
A global layer of software relays, managed nodes, physical gateways, fallback transports, and developer applications for humans, machines, and AI agents.
Use cases
Built for communication that cannot depend on platform trust.
The future communication backbone will not be owned by one app, one cloud, one carrier, or one government.
Resonance is building the routing layer for infrastructure people can run, inspect, replace, and extend.