NATS
NATS is a lightweight, cloud-native messaging system for fast communication between applications, and this Helm chart deploys it to Kubernetes.
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
57/100 Fair
- Maintained
- 95last commit 2 days ago
- Popular
- 56667 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
- Security check
- 152 serious findings, 1 minor, CI, tests
Based on 4 of 5 factors.
Security check: 2 serious findings
- Uses github.com/jackc/pgx/v5 v5.7.1, which has a known critical vulnerability (Go)
- Uses github.com/jackc/pgx/v5 v5.7.1, which has a known critical vulnerability (Go)
Automated checks on commit a77a1dd, 30 Oct 2026. Not an audit.
Availability: platform listings confirmed today
- GitHub stars
- 667
- Open issues
- 69
- Last commit
- 2026-11-19
- Latest release
- nats-2.15.3
- License
- Apache-2.0
- Activity
- rising
Checked today - source: GitHub (nats-io/k8s)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Use localhost:4222 for a local NATS For a NATS server on the same machine, the examples connect to localhost:4222 (the local address and port). Use the correct address and port when your app connects, because a wrong or blocked port stops all message sending and receiving. source
- Test NATS with a simple message After starting your server, try connecting, subscribing to a subject (a named message channel), and sending one message. This quick check proves NATS is reachable and your client is pointed at the right place before you add services or storage. source
- Add the Helm repository before installing This is a Helm 3 chart. Add the official NATS chart repository with: helm repo add nats https://nats-io.github.io/k8s/. Then install the nats chart with Helm 3. source
Fetched 40 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
How do I install the NATS Helm chart on Kubernetes?
Add the NATS Helm repository and then install the nats/nats chart with Helm 3.
How can I self-host NATS with a production-ready setup on Dokploy?
One user packaged a production-ready NATS server as a Dokploy Compose setup. It included JetStream, token auth, browser WebSocket access, and Traefik routing.
Is there a self-hosted support option for NATS?
Synadia Platform can be deployed self-hosted or as a managed cloud. It includes expert support from the core contributors and maintainers of NATS.
Can NATS be used for a self-hosted federated file-sharing project?
One self-hoster built Nasefa, a file-sharing app for themselves and friends, using NATS. It was presented as a project for self-hosted, federated, and decentralized applications.
Answers sourced from dev.to, github.com, nats.io, www.reddit.com
Community
- NATS.io: Simple, Fast, Secure Messaging for Cloud Native ... - Reddit (reddit)
- Nasefa: File sharing with myself (and friends) using NATS - Reddit (reddit)
- NATS Stage 3 waiting time : r/ATC - Reddit (reddit)
- NATS Uk - passed stage 1 - if anyone has any questions let me know! (reddit)
Collected 48 days ago - public community threads