kolo docsbeta

Roadmap

What comes next for Kolo: a local bridge, large groups, a web edge, Bluetooth LE between nearby peers, a JavaScript SDK and apps. No dates, and everything is still beta.

On this page

Everything in Kolo is beta. Every library is at v0.x, and the API of any of them may change before v1.0.0.

This page lists only what is ahead. What exists today is on the Libraries page. There are no dates here, and nothing below fixes an API: names and shapes can change while the work is done.

The examples that exist today are on Built with Kolo.

Each item has one of three statuses:

  • Planned we intend to build it and we know what it is for.
  • Exploring we are still working out whether to build it, and in what form.
  • Future an idea we want to keep in sight; nothing is researched or planned yet.

Each item also shows its topic: Local bridge, Groups, Web edge, Nearby peers, Network, SDKs or Apps.

Planned

Today you use Kolo from Go, inside the same process as your app. The local bridge is for a program that is not written in Go, or that runs as a separate process on the same computer.

  • kolo-ipc PlannedLocal bridge a channel between a Kolo process and another program on the same computer, open only to the same user. With it, an interface written in another language can use a peer that runs next to it.
  • kolo-rpc PlannedLocal bridge requests and answers over that channel. The other program asks the Kolo process to do something and gets a result back, without writing its own message framing.
  • A chat app PlannedApps a chat app for everyday use, built on the Kolo libraries. The chat in the tutorial is there to teach; this one is meant to be used.
  • kolo-gossip PlannedGroups a library to spread small messages to many members of a topic without a relay: each member passes a message on to a few others until every member has it. It follows the libp2p GossipSub specification, version 1.1 (a Candidate Recommendation) with the IDONTWANT rule of version 1.2 (a Working Draft), with Kolo's own wire format, and every message is signed by the key of the device that wrote it. Planned, with no code yet. We will say how large a group it carries, and what it protects against, only after our own simulation and tests.
  • kolo-mls PlannedGroups end-to-end encryption for groups, by the MLS standard (RFC 9420, architecture in RFC 9750), cipher suite 0x0001 (X25519, AES-128-GCM, SHA-256, Ed25519). The aim: a person who is removed from a group reads nothing sent after the removal reaches the group. What they received while they were a member stays with them. Planned, with no code yet. We will say how large a group it carries, and what it protects against, only after our own simulation and tests.

Exploring

  • kolo-http ExploringWeb edge a way for a browser or any HTTP client to reach what a peer serves. A browser tab cannot open the UDP connections that peers use, so it needs a peer that answers HTTP for it.
  • kolo-ble ExploringNearby peers connections over Bluetooth LE between peers that are near each other. The aim is the same small connection that the upper layers already take (Conn, as in kolo-sync and kolo-braid), so sync, pins, blobs and braids would work over it unchanged. Not started. The name follows how Kolo names a library after what it is: kolo-transport is QUIC, and a Bluetooth link is something else. Nothing about the design is decided. One possible design runs the existing encrypted stack over a Bluetooth packet link; another needs a handshake of its own, and a security review before any code. How nearby peers would find each other, and what someone nearby could observe, are open questions.
  • JavaScript SDK ExploringSDKs a thin client for JavaScript and TypeScript. On a desktop it talks to a Kolo process through the local bridge (kolo-ipc and kolo-rpc), and on the web it talks to kolo-http. The peer itself stays in Go.
  • Documentation MCP server ExploringSDKs a public MCP endpoint that AI coding tools can connect to in order to search and read the Kolo documentation. Not started. Today every page of these docs has a Markdown version, in English, Spanish and Portuguese, and the site publishes llms.txt and llms-full.txt for each language.
  • Key rotation in a chat ExploringApps a new conversation key after a member is removed. Removing a member is not revocation today: the removed member keeps the key and can still read new messages from the pins.
  • Multi-device accounts ExploringApps one person on several devices in the example programs. The library part is done and published: kolo-id has the 24-word recovery phrase, the person key and device certificates, kolo-invite links a new device by invite, and the devices package of kolo-braid keeps the roster of a person's devices in a group. No example program uses them yet, so in the examples a person on two devices is still two members.
  • Moderation tools for rooms ExploringApps tools for the admins of a room. Today an admin can approve requests and remove a member, and nothing more.
  • Mobile examples ExploringApps mobile examples for iOS and Android that teach how to build with Kolo: the chat first, then share, board and meet. Not started. To research first: how to ship Go code with the Kolo libraries inside a phone app, using public phone APIs only, and the camera and microphone permission flows that the meeting example needs.

Future

  • IPv6 FutureNetwork Kolo libraries work over IPv4 today: addresses, entry nodes, relays and the DHT use IPv4 only, and IPv6 forms are refused on purpose. Supporting IPv6 is a future item with no plan or date.

The road to 1.0.0

These are the conditions for a v1.0.0. They are criteria, not dates.

  • The public API of each library has been reviewed and frozen.
  • Validation on macOS, Linux and Windows is complete for every library.
  • The security model is written down for every library.
  • The docs and the examples are complete.

When we know of something that blocks a 1.0.0, it is listed in these docs: see Limits and Security.

Until then, everything in Kolo is beta (v0.x): every library, with an API that may change before v1.0.0.