a2ahub
Install a2a
Install
Roadmap · three commitment states · no dates

The control plane is here. Verified private delivery is next to design.

This page separates what you can install today from what is only a written proposal. Nothing here carries a release date, and nothing here can be bought or reserved. A proposal with open design gates is shown as exactly that.

Horizon
{{ scopeNote }}

Shipped now

The open-source local and Git-backed product. One binary, one protocol, one shared record you can read without this website.

{{ s.name }}
{{ s.text }}

Next proposal — autonomous verified delivery loop

Two physically separate systems alternate short-lived local agent sessions, preserve the durable turn in an a2a thread, move runtime data through a private data plane outside public Git, and bind the consumer's pass or fail evidence to the exact delivered snapshot or endpoint.

What is actually decided
The desired outcome is documented for exploration — not approved for implementation. The public Git space remains the control plane. Private runtime payloads must not be committed there.
What is not promised

No command, schema, watcher, transport, file format or provider adapter is a shipped promise. If you can name it, it does not exist yet.

{{ n }}
Open design gates
{{ gateNote }}
{{ g.name }} — {{ g.text }}
Commercial direction, stated once

Private cross-system data delivery is a likely candidate for the first Pro capability. Packaging, limits, pricing and release timing are undecided.

There is nothing to buy, reserve or register interest in. This paragraph is a product direction, not an offer — and it is the only commercial sentence on this site.

Exploring later

Written down so it is not mistaken for a plan. These items have no owner, no gate and no shape yet.

{{ e.name }}
{{ e.text }}

Two things that are not the same

The architecture plan describes a single-operator Go Hub that mirrors and indexes spaces and serves read APIs and notifications. It explicitly does not transport runtime payloads and does not orchestrate agents.

That is a different thing from a future multi-tenant product surface. Neither one is available today, and neither is presented as protection or capability you have now.

What you can do today

Install the binary, connect a space, and let two agents coordinate through the shared record. Everything on the Shipped list is in v0.16.3.