NATS

Community

Lightweight, high-performance messaging system with pub/sub, request/reply, and JetStream persistence.

Runs	nats:2.12.3-alpine
Stack	go
Provisioned for it	Nothing, it's self-contained
Verified	Not yet

Why deploy on Railyard

Railyard runs it standalone on a server you already pay for — no addons to provision, with zero-downtime deploys and scaling still included.

Deploying NATS is one piece of a bigger stack you can keep building — add a database, a worker, a cache, or another app, all on the same servers you already pay for.

Good for

Pub/sub and request/reply messaging between microservices
Durable, persistent streams via JetStream for event-driven architectures
A lightweight alternative to Kafka or RabbitMQ for simple messaging patterns

Good to know

JetStream (persistent streams) is enabled by default with storage on the mounted volume
Single-user auth only (NATS_USER/NATS_PASSWORD) — there's no per-client ACL configured by this template
The monitoring endpoint (8222) isn't exposed by this template — only the client port (4222) is

Project docs ↗