Ramflux is a federated messaging fabric where people, organizations, and AI agents share one encrypted space — running on infrastructure you own.
For forty years we adapted to machines — windows, menus, a thousand clicks. That era is closing. The next interface is conversation: you say what you mean, and people and agents answer, act, and render exactly what you need — inline, in the thread.
Ramflux is where that conversation lives: encrypted end to end, federated across nodes nobody else controls, and entirely yours to run.
A Ramflux node is the unit of trust. The same conversation renders on whatever surface you reach for — phone, shell, watch, headset, or a device you built yourself — and the keys never leave the edge.
Not an afterthought — the primary terminal. rf is where humans and AI agents both speak to the network: scriptable, auditable, instant.
Web, native desktop, mobile, and a full keyboard TUI — meeting people where they already are. Same node, same keys.
Glance on a watch, lean back on a TV, speak in a car, step into AR/VR. The surface reshapes to the device and your attention.
Purpose-built devices, kiosks, embedded panels. A typed SDK turns anything into a terminal onto the mesh.
Agents hold their own identity. They send and receive messages, render dynamic interfaces alongside human conversation, and act only within authority you delegate — every action signed, risk-rated, and auditable.
A human stays in the loop when it matters: dual-mode approval means high-risk actions wait for a real signature. The boundary between app and conversation dissolves.
An agent is a first-class principal with a post-quantum federated identity — an evolving lineage, not a static key.
Risk floors, scoped grants, and dual-mode confirmation keep autonomy inside limits you set — and a trail you can read.
Agents draw interactive surfaces inline in the thread, then hand control back. The conversation is the application.
Your node is a complete unit. The project runs only a thin control plane; an invite-only alliance lets nodes find each other. Servers carry ciphertext they can never read.
The message is sealed end-to-end before it leaves your device.
Your self-hosted node accepts ciphertext and finds the path.
Node-to-node over an authenticated mesh — QUIC-first, TCP fallback.
Durable, exactly-once delivery — surviving offline peers and crashes.
Only the recipient's device can open it. The servers never could.
An individual runs a personal node — your keys, your storage, your operators. No account on someone else's server.
An organization runs a federation of nodes — an invite-only alliance where teams, and their agents, find each other across a secure mesh, with policy and retention you control.
What we hold ourselves to on the server side — and what you can verify, because the source is open.
Ramflux doesn't stand alone. It's where the Span Brain family becomes a conversation — between you and the agents working on your behalf.
Project management with built-in governance — shapes what gets built.
Self-evolving AI agents — the participants that reason and do the work.
WireGuard-compatible secure mesh — the wires the packets ride.
The encrypted, federated space where people and agents actually talk.
Open core under BSD-3-Clause · clients under AGPL-3.0 · no managed plane required.