One uniform surface — bend, move, save — across ten storage backends and four transports. Your data, encrypted on your key, portable between apps, worth money to the people generating it. Not the platforms hoarding it.
For twenty years, the deal was simple: bring your attention, bring your work, bring your audience — we'll keep the data, we'll set the rules, we'll take the margin. The scarcity wasn't in the storage or the compute. It was in the lock-in. Your followers couldn't follow you out. Your records couldn't move. Your messages lived on someone else's server. That's the moat.
Three verbs — receive, read, observe — over a uniform surface. No schema migrations. No platform lock-in. Ship in an afternoon.
Apps talk over HTTP, WebSocket, gRPC, MCP — all from the same Rig. Humans and agents read the same surface. No protocol fork to ship.
Ed25519 signatures prove authorship. Client-side encryption keeps the server blind. Your key, your data, your audience — portable between any app.
Your stack should compose the way your team does — small, fast,
owned.
SaveClientwrangler deploy
The web's heavy. Frameworks fight you. Cloud bills sneak up.
deno install for the bnd CLI
Every list, every post, every channel you make on a
Most stacks pin you to a database, a cloud, a transport, a permission model.
Adding a feature should not require migrating a database. In
// add a capability to an existing rig
rig.bend("comment://*", /* program */);
rig.on("comment://*", /* handler */);
rig.move.http(8080); // already servingEd25519 identity. X25519 envelopes. RFC 8785 canonicalization. The data is signed and encrypted before it leaves the device. The network operator cannot read what it stores — so it cannot sell it, leak it, or be served a subpoena for it. Privacy is a property of the data, not a policy.
hash://sha256/… over canonical bytes
EntityStore is the contract: put, get,
list, delete. Memory, Postgres, SQLite, Mongo,
Elasticsearch, S3, FS, IPFS, localStorage, IndexedDB — all the same
surface. Multi-store writes broadcast. Reads try each in order.
Swap substrates by config, not by rewrite.
const store = multi([
indexedDb({ name: "local" }),
httpStore({ url: "https://firecat" }),
]);
await store.put(entity); // → both
await store.get(uri); // → first hit wins
receive what came in. read what's there.
observe what changes. That's the entire surface.
It works in-process. It works over HTTP and WebSocket. It works
over gRPC for service meshes, MCP for agents. Ship a new flow:
write the program, write the handler, choose the surface. The
rest is already correct.
Receive what came in. Read what's there. Observe what changes. The same surface in-process, over the wire, and for agents. Here's a tiny one.
// b3nd-core gives you the foundation. b3nd-save the store.
// b3nd-move the surfaces (http, ws, grpc, mcp).
import { Rig } from "@bandeira-tech/b3nd-core";
import { sqlite } from "@bandeira-tech/b3nd-save";
import { http } from "@bandeira-tech/b3nd-move";
const rig = new Rig({ store: sqlite("./.b3nd") });
// classify incoming messages by their URI shape ...
rig.bend("note://*", (uri, payload) => ({
code: "note.created", payload,
}));
// ... and react. pure functions in, Output[] out.
rig.on("note.created", (msg) => [
{ code: "save", payload: msg.payload },
]);
await http(rig, { port: 8080 });
// → ready over http, ws, mcp. one rig, three doors.// the surface is symmetric.
// in-process, http, ws, mcp: same three verbs.
import { httpClient } from "@bandeira-tech/b3nd-move";
const app = httpClient("https://app.example");
await app.receive([
"note://2026/06/20/first",
{ title: "build, share, own" },
]);
const n = await app.read("note://2026/06/20/first");
for await (const n of app.observe("note://*")) {
render(n); // live, signed, content-addressed.
}deno install -A -gf jsr:@bandeira-tech/b3nd-cli/bnd
docker run ghcr.io/bandeira-tech/b3nd/b3nd-node:latest
bnd push --to firecat
bnd push packages your rig, signs the manifest with
your key, ships it to the network, and gives you a live URL.
No build pipeline. No CI. No "what region should I pick."
The same surface runs locally and on the wire.
The Rig speaks MCP natively. Every capability you ship to humans is already available to agents — same verbs, same shapes, same content-addressed I/O. No second protocol. No second backend. No "agent SDK" tacked on. Just three verbs over a uniform surface, every door you open opens both ways.
receive · read · observe. Predictable enough for tools to compose, free enough for agents to invent.
hash://sha256/… over RFC 8785. Agents can quote, cite, and reference without forgery.
Every message is Ed25519-signed. Agents act on their own keys. Audit trails are free.
No whitepaper. Live testnet. Published packages. Apps you can use this afternoon.
The public B3nd network. Running now. Your apps deploy here.
testnet-evergreen.fire.cat →b3nd-core · b3nd-move · b3nd-save · b3nd-canon · b3nd-cli. One import each.
jsr.io/@bandeira-tech →Lists for the things you love. Audience-portable, end-to-end encrypted, with a built-in attention marketplace that pays out to you.
soon · v0.0.1 alphaThe capture-anything CLI. URLs, notes, snippets — saved on a personal b3nd-save store at ~/.k3p/data. We use it daily.
We run
Small rewards, often, in crypto, paid directly. No 30% house cut on the way out. If you're an entry-level builder — or a "new script kid" wielding AI — this is the right place to ship your first app on a real, paying network.
Public motion, public dates. Every line below is a thing we're shipping, not a roadmap promise.
Open testnet hosting B3nd nodes. Public endpoints, free-tier deploy targets, fair-use throttling.
The lighthouse app — lists, audience, attention marketplace — opens its waitlist to the early-signal list first.
One brief, one week, five prize categories. Best video demo · serious business · funniest · community choice · your language.
Well-specified work. Small-and-often payouts in crypto. Documented in the open.
Tier-2 events once the community machine is running steadily. DevPost / MLH / ETHGlobal / lablab.ai tracks.
One Deno install gets the bnd binary on your path. Works the same on macOS, Linux, Windows.
deno install -A -gf jsr:@bandeira-tech/b3nd-cli/bnd
Pick a store, declare a handler, choose a transport. One file. No CI, no config, no schema migrations.
bnd init my-app && cd my-app
One command. Live URL. Already speaking HTTP, WebSocket, and MCP. You're on Firecat.
bnd push --to firecat
Software has spent a decade getting more complicated to do fewer things — more dependencies, more renderers, more opaque platforms, more rented data. The interesting work has been sitting underneath, in the wiring: how data moves, where it persists, what proves it's yours.
b3nd is what falls out when you make that wiring explicit. Three verbs. One Rig. A small, uniform surface that agents can use as easily as humans. Storage that's portable. Identity that's cryptographic. A network whose economics flow to the people doing the work.We're building it in the open. If you're a builder, a creator, or anyone tired of the moats — get on the list. We'll bring you in as the doors open.
One email. We tell you when the first sprint goes live, when new apps open to the network, and when the bounty board posts work that pays. Nothing else.