synrc/n2o

Health v2 · maintenance only

Flags: no_license

Adoption not part of the score

1341 stars · 167 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

N2O is an embeddable message protocol loop library for WebSocket, HTTP, MQTT, and TCP servers written in Erlang. It provides process management, a virtual nodes ring for request routing, sessions, frame encoding (JSON/BERT/ASN.1), and unified APIs for message queues and caching backends.

Use cases

• build a real-time websocket chat server in erlang
• run application logic inside an mqtt broker as an emq plugin
• implement rpc over message queue with tcp or udp endpoints
• add websocket push messaging to a cowboy web app
• build iot backends speaking mqtt-sn or coap
• manage distributed processes with a hash ring of virtual nodes

When to choose

• you are building real-time websocket or mqtt applications on the erlang/otp stack
• you want a tiny (~700 LOC) embeddable protocol loop rather than a heavyweight framework
• you need multi-protocol endpoints (websocket, mqtt, tcp, udp) with one unified message loop
• you want pluggable pubsub backends like gproc or syn and formatters like json or bert

When to avoid

• your team does not work in erlang or elixir
• you need a conventional request/response web framework with routing, templating, and a large ecosystem
• you require a permissively documented, mainstream license - the license is marked NOASSERTION despite ISC claims
• you need extensive community support, as the project is niche with a small user base

Facets

framework · maturity active

websocket http-server message-queue caching serialization rpc middleware web-framework web-development backend iot microservices elixir windows self-hosted mqtt tcp udp bert cowboy emq pubsub erlang protocol-loop hash-ring real-time messaging linux macos web-server

Member repositories

For agents

markdown · JSON · MCP: product_card(name="synrc/n2o")