Apron Chat Protocol: A Minimal JSON Chat Protocol for Self-Hosted Servers

Apron is a minimal protocol for self-hosted chat, published at apron.chat by Hacker News user shazow. Its central claim is a deliberate trade-off: the core is small enough that a working server can be written in roughly 100 lines, while optional capabilities extend it to rooms, threads, bots, reactions, and more.

The project was posted as a Show HN and, at the time of writing, had 30 points and no comments on the Hacker News thread.

The protocol is JSON over any transport, including WebSocket

Apron does not define its own framing or transport. Messages are JSON objects sent over any transport, with WebSocket given as the example. The core is tiny, and additional capabilities are optional and incremental, with graceful fallbacks so a client or server can ignore features it does not implement.

The project's stated design principle is "build only what you need."

A session in the published example looks like this. The server advertises itself first:

{"method": "server", "params": {"apron": 10, "auth": ["guest"]}}

The client then authenticates:

{"method": "auth", "id": "c1", "params": {"scheme": "guest", "name": "Ada"}}
{"id": "c1", "result": {"you": {"user_id": "guest_1234", "name": "Ada"}}}

And sends a message:

{"method": "message", "id": "c2", "params": {"body": {"text": "Hello"}}}
{"method": "message", "params": {"room_id": "general", "from": {"user_id": "guest_1234"}, ...}}
{"id": "c2", "result": {"message_id": "1724803200042"}}

Three structural details are visible in that exchange. Requests carry a method and an optional id; responses echo the id and carry a result. The server handshake advertises "apron": 10 alongside the supported authentication schemes, and the example uses a guest scheme with a display name. Message IDs in the example are millisecond-style numeric strings such as 1724803200042.

Apron is designed to be read and implemented by AI agents

The project publishes an agent-oriented entry point at apron.chat/llms.txt. That file links the specification in Markdown, the reference servers, the clients, a JSON Schema, and wire fixtures to test against.

This is a notable choice for a chat protocol: rather than pointing implementers only at prose documentation, Apron ships machine-checkable artifacts — a schema and wire fixtures — so that a generated client or server can be validated against the actual message format.

The public demo shows three deployment shapes

The site hosts a public demo server and an Apron Web client that can be pointed at any server. Three scenarios are presented to illustrate the range of the protocol:

  • Team chat. Rooms, threads, direct messages, bots, replies, mentions, a terminal, reactions, and presence.
  • Family chat. Private rooms, threads, replies, reactions, avatars, and typing indicators.
  • Support desk. A swarm of bots, one thread per ticket, and a single answer shared across all of them.

These scenarios are the project's argument that a minimal core does not cap the feature ceiling: presence, typing indicators, threads, and reactions are all reachable as optional capabilities layered on the same JSON message shape.

Servers and clients are separate, replaceable pieces

Apron is structured so that servers and clients are independent. The site lists reference server implementations intended to be run or modified for specific use cases, and clients that can join any server. The stated goal is that a user can join any server with a preferred client, or build a new one.

Because the protocol is JSON over a generic transport and the core is deliberately small, the reference implementations function as starting points rather than as the only supported stack.

The FAQ lists the questions the project expects to be asked

The Apron FAQ, hosted in the project's GitHub repository, addresses a set of recurring objections. The published question list is:

  • Who are you?
  • Why did you make the Apron Chat Protocol?
  • Is there encryption? Is it safe?
  • Why not XMPP/Matrix/IRCv3/etc?
  • Why not Slack/Discord/Zulip/etc?
  • Why another standard? XKCD 927!
  • How was AI used to create Apron? Is it slop?
  • Is Apron a business?
  • Why is it named Apron?
  • Ok fine, how can I try it?

The presence of the XKCD 927 question — the comic about competing standards — and the "Is it slop?" question indicates the author anticipates two specific criticisms: that a new chat protocol adds fragmentation rather than reducing it, and that an AI-assisted project may not be a serious engineering effort. The answers themselves live in the linked FAQ rather than on the landing page.

What the source material does not establish

The landing page and the Hacker News submission do not state a license, a governance model, a security or encryption design, or a version history beyond the "apron": 10 value in the handshake example. The Hacker News thread had no comments at the time of collection, so there is no community discussion, counterargument, or maintainer response to synthesize here. Readers evaluating Apron for production use should consult the specification, JSON Schema, and wire fixtures linked from apron.chat/llms.txt, and the FAQ in the GitHub repository, rather than relying on the landing page alone.

Sources