Install nats-server with Homebrew, apk, apt, Nix, scoop, winget

Project links

• Homepage
• Repository

Commands and aliases

• nats-server

Project history

NATS was created by Derek Collison. NATS documentation says the acronym stands for Neural Autonomic Transport System and that Collison conceived it as a central-nervous-system-like messaging platform. A 2016 NATS blog post explains that it began as a central nervous system for a cloud control plane, initially without higher QoS guarantees beyond TCP/IP.

The nats-io/nats-server repository was created on 2012-10-29. NATS Streaming was announced on 2016-07-19 to add persistence and delivery guarantees as a layered service; later NATS Server 2.2 made JetStream the recommended persistence, streaming, and higher-guarantee option, while NATS Streaming became deprecated.

CNCF announced hosting NATS on 2018-03-15 at incubating maturity. The NATS FAQ says maintainership follows a governance process as part of CNCF, with Synadia engineers and community maintainers maintaining the server, streaming server, and official client libraries.

Adoption history

GitHub API data fetched on 2026-07-01 showed 20,126 stars and 1,856 forks, the largest upstream community signal in this batch. Homebrew's formula JSON generated on 2026-07-01 reported 8,660 installs over 365 days and 8,658 installs-on-request over 365 days, indicating that most Homebrew installs are direct requests rather than incidental dependencies.

NATS adoption is broader than the Homebrew formula because it is commonly run via Docker, Kubernetes, release archives, and cloud/edge deployments. The official install docs list command-line installer, Docker, Kubernetes, package managers, release zips, and source builds as normal installation paths.

How it is used

Developers run `nats-server` locally for development, as a service for production messaging, or in clusters. Core NATS handles publish/subscribe, request/reply, queueing, service/microservice communication, and subject-based addressing; JetStream adds persistence, replay, key/value, object-store-like patterns, and stronger delivery semantics.

Package nerds use the Homebrew package when they want a local broker-like service without container overhead: `brew install nats-server`, then run the binary and connect clients on the default client port. For production, the same binary is more often wrapped in service managers, Docker images, Helm charts, or managed deployment automation.

Why package nerds care

nats-server is significant because it is both the reference server and the operational heart of the NATS ecosystem. Unlike a client-only package, installing it gives developers a working messaging substrate for local integration tests, demos, and small deployments, while the same project scales into clustered cloud-native infrastructure.

Timeline

• 2012-10-29: nats-io/nats-server repository created on GitHub.
• 2016-07-19: NATS Streaming announced to add persistence and delivery guarantees.
• 2018-03-15: CNCF announced NATS as an incubating hosted project.
• NATS Server 2.2: JetStream became the recommended persistence and streaming option, while NATS Streaming was deprecated.
• 2026-06-29: nats-server v2.14.3 release published.
• 2026-07-01: Homebrew formula JSON listed stable version 2.14.3 and 8,660 installs over 365 days.

Related projects

• JetStream
• NATS Streaming
• Synadia
• CNCF
• NATS clients

Sources

• https://api.github.com/repos/nats-io/nats-server
• https://api.github.com/repos/nats-io/nats-server/releases?per_page=8
• https://docs.nats.io/nats-concepts/overview
• https://docs.nats.io/reference/faq
• https://docs.nats.io/running-a-nats-service/introduction/installation
• https://formulae.brew.sh/api/formula/nats-server.json
• https://formulae.brew.sh/formula/nats-server
• https://github.com/nats-io/nats-server
• https://nats.io/blog/introducing-nats-streaming/
• https://www.cncf.io/blog/2018/03/15/cncf-to-host-nats/