A minimal protocol for self-hosted chats
Apron is a minimal open protocol for self-hosted chat. The core is JSON over any transport (such as WebSocket), kept small enough that a server can be written in ~100 lines, with optional incremental capabilities — rooms, threads, bots, reactions, mentions, presence, and more — that degrade gracefully so you only build what you need. The project ships reference server implementations in Go, TypeScript (Cloudflare Worker), Python, and Bun, plus clients for the web, macOS, terminal, and bots, along with a JSON Schema and wire test fixtures.
A tiny JSON-over-any-transport core (e.g. WebSocket) with a simple request/response message format like {"method": "auth", "params": {...}}.
Rooms, threads, DMs, replies, mentions, reactions, presence, bots, and more can be added as optional capabilities with graceful fallbacks — build only what you need.
A Go reference server with every capability, a TypeScript Cloudflare Worker server (runs the public demo on the free tier), and single-file minimal servers in Python and Bun with no dependencies.
A SvelteKit web client, a macOS client (SideTable), a terminal TUI client (whisk), and a GitHub pull-request notification bot, all interoperable with any Apron server.
The spec is published in Markdown via llms.txt, with a JSON Schema and wire fixtures to test implementations against; writing a bot takes two frames (auth + message).
Designed for self-hosted chat — point the web client at your own server or run the reference implementations yourself.
Run one of the reference servers (Go, Cloudflare Worker, or a one-file Python/Bun minimal server) or write your own following the spec — the core is small enough for ~100 lines of code.
Join any server with an existing client (web, macOS, terminal) or build your own; clients and servers interoperate via the JSON protocol and test fixtures.
Start with the tiny core (auth and messages) and adopt optional capabilities — rooms, threads, reactions, bots, presence — with graceful fallbacks when a feature isn't supported.
A minimal protocol for self-hosted chats. The core is JSON over any transport (such as WebSocket), simple enough to write a server in ~100 lines, with optional capabilities like rooms, threads, bots, and reactions.
The tiny core handles auth and messages; optional incremental capabilities add rooms, threads, DMs, replies, mentions, reactions, presence, and bots, with graceful fallbacks so you build only what you need.
Use the public demo at web.apron.chat (server: wss://server.apron.chat/), or point the Apron web client at your own server. Ready-made demo scenarios include team chat, family chat, and a support desk.
A Go reference server (apron-server-go) with every capability, a TypeScript Cloudflare Worker server (apron-server-cloudflare) that runs the public demo on the free tier, and single-file minimal servers in Python and Bun covering one room, guests, and history.
The SvelteKit web client behind the live demo, a macOS client called SideTable, a terminal TUI client called whisk, and a GitHub pull-request bot — or you can build your own client or bot.
Two frames: one auth message and one message posting, e.g. {"method": "auth", "params": {"scheme": "token", ...}} followed by {"method": "message", "params": {"body": {"text": "Deployed v1.4.2"}}}.
Yes — apron.chat/llms.txt links the spec in Markdown, the servers, clients, a JSON Schema, and wire fixtures to test implementations against.
The site's FAQ addresses this question directly (along with topics like encryption, comparisons to XMPP/Matrix/IRCv3 and Slack/Discord/Zulip, and how AI was used) — see the FAQ on apron.chat for the project's answers.