Program status · Updated 2026
Honest current state.
We would rather show you what is real than what looks impressive. Four categories: shipped, in flight, designed but not yet built, and to be decided.
ShippedIn flightDesignedTo be decided
Shipped
Working and in the codebase. Not vaporware.
| Status | Item | Description |
|---|---|---|
| Shipped | MCP memory server | Local-first persistent memory for AI coding agents. Runs as an MCP server on your device. Stores facts, decisions, tasks, and references across sessions and agent vendors. |
| Shipped | Coordinator + mesh control plane | FastAPI coordinator handling peer attestation, signaling, mesh enrollment, and blinded inference dispatch. Privacy invariants enforced at the schema level and tested in CI. |
| Shipped | WireGuard mesh sidecar (Go) | Go sidecar embedding userspace WireGuard. STUN endpoint discovery, UDP hole-punch, DERP relay fallback for symmetric NAT. Cross-network smoke tested on a 4-machine heterogeneous fleet (Mac arm64, Linux x86_64, Windows x86_64). |
| Shipped | Electron desktop app + React frontend (Hearth) | Polished local app: chat, memory browser, agent observability dashboard, mesh management. Ships with the Python inference sidecar and the mesh sidecar embedded. |
| Shipped | Blinded inference dispatch | Coordinator-side dispatch strips member_id before forwarding jobs to contributor peers. Enforced by schema, since the message type has no identity field, and by a privacy lint in CI. |
| Shipped | DERP relay (network-operated) | Single-region relay on Fly.io. Implements the DERP wire format. JWT-authenticated. The relay sees encrypted bytes only: no plaintext, no member identity. |
| Shipped | Pinned instructions (ambient memory) | Mark a memory as pinned and the retriever always injects it, regardless of query. Standing rules like "always use pnpm" or "deploys after 6pm" stay in the agent's context without depending on semantic match. Available via the desktop UI, the local API, and the MCP memory_pin tool. |
| Shipped | Hard-delete + retrieval quality upgrade | memory_delete now permanently removes the row and its embedding: delete means gone, not just inactive. Embedder upgraded to bge-small-en-v1.5; precision@1 on adversarial pairs doubled from 0.40 to 0.80 with no regression on broad recall. |
| Shipped | Memory-wedge demo videos | Two narrated demo videos: the memory wedge (Demo A) and an agent-in-the-loop showing a real Claude Code session retrieving a memory mid-task with the agent dashboard lighting up (Demo C). Built with an automated Playwright + ElevenLabs pipeline; capture and recompose at will. |
In flight
Active work. These are the current blockers for public launch.
| Status | Item | Description |
|---|---|---|
| In flight | NLnet NGI Zero Commons grant application | Application submitted before the May 23 internal target (June 1 hard deadline). Funds: external security audit of the mesh protocol, 12 months of DERP relay hosting, and signed cross-platform installers. |
| In flight | Single-binary distribution (Launch B) | PyInstaller bundling the Python sidecar + electron-updater auto-update infrastructure + signed installers for Mac (arm64 + x86_64), Windows (x86_64), Linux (x86_64 + arm64). Unsigned local rebuild verified May 29. The remaining lift is code-signing (Apple Developer + Windows SignPath/Azure) and the auto-update channel. This is the launch blocker; no public launch until binary distribution is clean. |
| In flight | Credit ledger | Per-member accounting of inference served and consumed. Feeds two downstream systems: non-transferable compute credits that offset your own usage, and the forward-looking contributor governance distribution. |
Designed, not yet shipping
The architecture and approach are settled. Engineering has not started or is not the current priority.
| Status | Item | Description |
|---|---|---|
| Designed | Company + network foundation formation | Founder-led Delaware C-corp for the software and commercial side, plus a foundation that stewards the network and its governance token. Charter mission commitments: no user-data sale, no training without opt-in, local-first by default. Requires a startup attorney plus token counsel; legal workstream in progress. |
| Designed | Member accounts + network governance | Account sign-up flow, subscription for hosted backup and priority routing, and the staged network-governance mechanism over a bounded parameter set (model curation, routing, treasury, fees). Target: v0.5. |
| Designed | Contributor governance distribution | A forward-looking distribution that gives sustained contributors a share in the network governance token. Structure being designed with securities counsel; deliberately not a linear payout for compute served, and not published in specifics yet. Target: post network launch. |
| Designed | Multi-region DERP | Second relay region to eliminate the single-region SPOF for DERP-heavy users (T-Mobile Home Internet, Starlink, cellular). Post-launch, once network growth warrants. |
| Designed | External security audit | Commissioned review of the mesh protocol + DERP implementation + privacy invariants by a qualified external firm with WireGuard/P2P experience. Funded by the NLnet grant if awarded. |
To be decided
On the map. Not yet designed in detail. Dates are genuinely unknown.
| Status | Item | Description |
|---|---|---|
| To be decided | Public access opens | Date TBD. Blocked on: signed binary distribution, company and network-foundation formation, member-auth infrastructure, and the governance-distribution paperwork. We will not open public access before these are in place. |
| To be decided | Cross-household compute (Phase G network) | Inference requests routed not just within a household mesh but across the full member-operated network. Requires member-auth and ACL infrastructure first. This is the core promise: shared compute at network scale, owned by no single party. |
On dates: we have an internal submission target of May 23 for the NLnet grant and a hard deadline of June 1. Beyond that, everything else on the designed and TBD list has no public commitment date. We will publish dates when we have confidence in them.
On the launch blocker: public public launch comes after signed binary distribution, company and network-foundation formation, and member-auth are in place. We are not opening public access before those are ready.
On what we do not know yet: the grant outcome, the pace of the legal workstream, how fast the installer pipeline moves. We will update this page when things change.
Read the full vision and the values behind it.
Manifesto