NSQ
At #8 of 13 in our message queue software ranking, NSQ is summed up in the catalogue as: Distributed messaging platform with no central broker, written in Go.
A vendor never writes its own entry here, NSQ included, although paid placement exists; see the disclosure for how links are marked.
Visit NSQ See it in the message queue software ranking
NSQ at a glance
| Headquarters | Not stated by the vendor |
|---|---|
| Best for | Go-friendly teams wanting a simple self-run queue without a single broker |
| API | Not covered by the sources we used |
| Deployment | Cloud or hosted |
| Pricing model | No price or plan on the pages read; MIT-licensed binaries to download |
| Free plan | Paid only, as far as we recorded |
What is NSQ?
NSQ is a messaging platform that the project homepage calls realtime and distributed. Its design avoids a central broker: nodes run side by side, and the homepage says the topology has no single point of failure and scales horizontally without centralised brokers. It supports publish-subscribe and load-balanced delivery, ships an admin UI, and comes as binaries with no runtime dependencies.
The features page states that messages are delivered at least once, which means a consumer can see the same message twice and has to cope with that. Messages are held in memory and are not durable by default, but beyond a high-water mark they are transparently kept on disk. The project is written in Go, the GitHub repository names the MIT licence, and the only attribution on the homepage is NSQ Authors. A company, legal entity and country are not stated on the pages we read, and we found no mention of a hosted or commercial service.
NSQ key features
- No central broker. The homepage describes distributed and decentralised topologies without single points of failure, scaling horizontally without centralised brokers. Capacity is added by running more nodes rather than by enlarging one machine.
- Runtime discovery with nsqlookupd. The features page names nsqlookupd as the discovery service that lets consumers find producers while the system runs. Consumers therefore need no hard-coded list of producer addresses, which keeps node changes simple.
- Publish-subscribe and load balancing. Both delivery styles are listed on the homepage. A topic can fan out copies to several channels, while consumers on one channel share the work, so one design covers broadcast and work-queue patterns.
- At-least-once delivery. The features page promises that each message is delivered at least once. Duplicates are possible, so consuming code should be written to tolerate seeing a message twice, which the pages we read leave to the user.
- Disk spill past a high-water mark. Messages are not durable by default, but past a high-water mark they are transparently kept on disk. This bounds memory use under a backlog, though it is not the same as guaranteeing every message survives a crash.
- nsqadmin and TLS. nsqadmin is named as the cluster administration interface, and the features page lists transport layer security support. The default configuration is described as sane and bounded, which lowers the tuning needed on day one.
- Client libraries and open protocol. Official Go and Python clients are named, with many community libraries for most major languages. A TCP protocol specification is linked so a team can write its own client for a language that lacks one.
Who NSQ suits
- A Go team building an internal job pipeline. The software is written in Go and ships an official Go client, so a team already on that stack can run producers and consumers without adding a second language runtime or a heavy broker cluster.
- An operations group that wants no single broker to fail. Because nodes find each other through nsqlookupd and the design avoids central brokers, losing one node does not take down the whole system. The group still has to plan for duplicate delivery.
- A developer prototyping on a laptop. Binaries have no runtime dependencies and run on Linux, macOS, FreeBSD and Windows, or through Docker and Homebrew. A prototype can start within minutes, without an account or a licence key.
Getting started with NSQ
The installation page offers several routes. Pre-built binaries are listed for Linux (amd64, arm64), macOS (amd64, arm64), FreeBSD (amd64) and Windows (amd64). An official Docker image is the container route, Homebrew covers macOS, and a source build with make needs Go 1.17 or later. The page lists version 1.3.0 as the current stable release, with 1.2.1 kept as an older archive.
A typical first run means starting nsqlookupd, one or more nsqd nodes and nsqadmin, then pointing a client at them. The pages we read do not set out that sequence step by step, so expect to follow the project's own guides. Official Go and Python clients are the quickest way to publish and consume a first message.
Verdict: NSQ
NSQ avoids a central broker: nodes advertise through nsqlookupd and consumers find producers at runtime, with an admin UI called nsqadmin. Delivery is at least once, and messages are not durable by default, spilling to disk only beyond a high-water mark.
The GitHub repository names the MIT licence. Neither a company nor a country is named on its pages, and no hosted service or vendor support is mentioned.
In our message queue software ranking NSQ stands at #8 of 13: Eclipse Mosquitto sits directly above it and ZeroMQ directly below. Challengers hold places 1 to 3 where a category has them; the number here is a place in the order, not a mark out of ten.
The vendor states no country of establishment, so NSQ is left out of the regional count for this list.
Strengths and limits of NSQ
- NSQ avoids a central broker: nodes advertise through nsqlookupd and consumers find producers at runtime, with an admin UI called nsqadmin.
- Catalogue tag: Go binaries.
- Best for: Go-friendly teams wanting a simple self-run queue without a single broker.
- Catalogue tag: At-least-once.
- Decentralised is among the traits we single out for it.
- A crashed node can lose queued messages, since durability is not the default setting.
- The pages read name no company, legal entity or country, and mention no hosted or paid offering.
- Less suited to: Buyers who need guaranteed ordering, a vendor contract or a managed service.
NSQ pros and cons in practice
- Binaries with no runtime dependencies make a first install quick on four operating systems.
- The MIT licence named on GitHub removes licence cost and procurement.
- Runtime discovery through nsqlookupd avoids a fixed list of producer addresses.
- A documented TCP protocol allows a custom client where no library exists.
- Messages are not durable by default, so memory-only data can be lost if a node stops.
- At-least-once delivery means consumers must handle duplicates themselves.
- No company, support contract or hosted service is named on the pages we read.
- Official clients exist only for Go and Python; other languages rely on community libraries.
NSQ in practice
The installation page lists pre-built binaries for Linux, macOS, FreeBSD and Windows, a Docker image, Homebrew and a build from source that needs Go 1.17 or later, with 1.3.0 shown as the stable release.
Official client libraries exist for Go and Python, with community ones for most languages and a TCP protocol specification for custom clients.
Delivery supports both publish-subscribe and load-balanced consumption, and TLS is listed.
Paying for NSQ
Charging model: No price or plan on the pages read; MIT-licensed binaries to download.
The homepage names no price and no paid plan, and the installation page states neither a licence nor a cost. The licence comes from the GitHub repository nsqio/nsq, which names the MIT licence, so using the software carries no licence fee. What you pay for is the infrastructure you run it on and the staff time to operate it. The pages we read mention no hosted or managed NSQ service, and no vendor support contract or paid tier. That means support comes from documentation and the community, not from a company you can call. Because no company is named, there is also no sales contact or quote process to go through. Budget therefore centres on servers, disk and monitoring, and on engineering effort to handle duplicate messages and the not-durable-by-default behaviour in your own code.
Source: the pricing material on nsq.io, as read for Best Message Queue Software in 2026 and last reviewed on 15 November 2026.
NSQ: data and security
NSQ runs where you install it, so your messages stay on your own machines and no vendor receives them. The features page lists transport layer security support and describes the default configuration as sane and bounded. Messages are not durable by default, and only beyond a high-water mark are they kept on disk, so a node that stops can lose messages held only in memory.
The pages we read name no compliance certifications, no encryption-at-rest feature, no audit log and no access control model, so any such requirement has to be met by the surrounding system. No company or country of establishment is stated, and the only attribution is NSQ Authors, so there is no data processing agreement to sign.
Integrations and ecosystem
Integrations the vendor names (9):
- Go client
- Python client
- Community client libraries
- TCP protocol specification
- Docker
- Homebrew
- nsqlookupd
- nsqadmin
- Linux, macOS, FreeBSD and Windows binaries
NSQ fact sheet
| Product | NSQ |
|---|---|
| Vendor website | nsq.io |
| Head-to-head pages | Not paired so far |
| Headquarters | Not stated by the vendor |
| Gaps in our records | headcount, funding and customer count |
| Primary guide | Best Message Queue Software in 2026 |
| Catalogue tags | Decentralised, At-least-once, Go binaries |
| Alternatives page | None yet |
| Price visibility | Model recorded, no figure |
| Rank there | #8 of 13 |
What to look at instead of NSQ
The choice below rests on shared catalogue tags, price model, free plan and region, with rank distance as the tie-break.
- Eclipse Mosquitto (#7 of 13): Light MQTT broker from the Eclipse Foundation, for small boards and servers. Suits: Embedded and edge deployments that need a small, standards-based MQTT broker.
- ZeroMQ (#9 of 13): Aimed at: Developers building messaging directly into their own application code or services.
- Apache RocketMQ (#10 of 13): A good match for: Java teams wanting ordered messaging they run and tune themselves. (United States)
- IBM MQ (#13 of 13): Enterprise messaging with exactly-once delivery, from mainframe to cloud. Watch out: the standard subscription needs a minimum one-year term, priced per virtual processor core. (United States)
Also ranked in
| Guide | Position |
|---|---|
| Best Message Queue Software in 2026 | #8 of 13 |
Questions about NSQ
9 answersWhere does NSQ stand among message queue software?
Position 8 of 13 is where NSQ sits among message queue software.
Which country is NSQ from?
The vendor pages we reviewed state no country of establishment for NSQ, so we do not give one.
Is NSQ the right fit for me?
Go-friendly teams wanting a simple self-run queue without a single broker. Less suited to: buyers who need guaranteed ordering, a vendor contract or a managed service.
What else should I look at besides NSQ?
Start with Eclipse Mosquitto, ZeroMQ, Apache RocketMQ and IBM MQ. You will find each one reviewed in the message queue software ranking.
Is NSQ free, or what does it charge?
Our catalogue records NSQ’s pricing as: No price or plan on the pages read; MIT-licensed binaries to download. On free access, a paid plan is required, per our records.
Does NSQ need a central broker?
The homepage says it scales horizontally without centralised brokers and avoids single points of failure. Nodes advertise themselves, and consumers find producers through nsqlookupd.
Can a message be delivered twice?
Yes. The features page states at-least-once delivery, so a consumer can receive the same message more than once and should be written to cope with that.
Which licence applies?
The nsqio/nsq repository on GitHub names the MIT licence. The installation page itself states neither a licence nor a cost.
Is there a company behind it?
The homepage footer reads 2023 NSQ Authors. No company, legal entity or country is named on the pages we read, so there is no vendor to contact for support.
NSQ: sources
Read from the vendor’s own pages on 14 November 2026.
- nsq.io: Description, topology, pub-sub and load balancing, admin UI, clients, footer attribution
- nsq.io/overview/features_and_guarantees.html: At-least-once delivery, durability, high-water mark, nsqlookupd, nsqadmin, TLS
- nsq.io/deployment/installing.html: Binaries, Docker, Homebrew, source build, version 1.3.0, absence of price
- github.com/nsqio/nsq: MIT licence
How we rank
The same four questions are asked of every message queue software product: time to value, real cost, the way out and the intended buyer. NSQ ends up at #8 among 13. Read the editorial process for the method and where paid visibility fits in.