Asopitech VS
NATS vs Alopex Chirps
NATS subject-based messaging and JetStream persistence, compared with Alopex Chirps.
Updated: Oct 13, 2026
What NATS is
NATS is an open source messaging system. Applications connect to a NATS server and exchange messages by subject, without knowing each other’s network addresses.
How it works
- Server: the NATS server routes messages. It is one binary, and clustering, JetStream, MQTT and WebSocket are configuration on the same process.
- Core NATS: messages reach only subscribers connected at the moment of publication.
- JetStream: a persistence layer adds at-least-once delivery and replay.
Main features
- Publish-subscribe, request-reply, queue groups.
- JetStream streams, consumers, a key-value store and an object store.
- Official clients for many languages.
Limits
Applications connect to a NATS server, and a cluster of servers has to be operated.
How it differs from Alopex Chirps
Both carry messages between nodes.
NATS delivers messages by subject through a server. Alopex Chirps is a library embedded in the application, and nodes talk to each other directly over QUIC. Messages are addressed by node ID, and the list of peers and their liveness come from gossip membership. Raft consensus is in the same library, so work whose order must line up can go through consensus.
Try Alopex Chirps to send messages directly between nodes without a server in between. Start from the quickstart on GitHub.