Perimattic
ManageStacks · DevTools

Managed NATS Hosting — production-ready from $16 a month

Cloud and edge native messaging server for pub/sub, request-reply, and streaming. Deployed on your own dedicated instance in AWS, Azure, or GCP, kept patched, backed up, and monitored by ManageStacks — standard NATS, no lock-in.

NATS on ManageStacks is the open-source, cloud and edge native messaging system deployed to your own AWS, Azure, or GCP region, with flat per-app pricing from $16 a month ($30 on the Standard production plan). Engineers connect microservices and devices with publish-subscribe and request-reply messaging, as an alternative to Amazon SNS and SQS, Google Pub/Sub, and Azure Service Bus.

Daily backups includedAWS · Azure · GCPData export any time24×7 SRE available
NATS logo
NATS
Cloud and edge native messaging server for pub/sub, request-reply, and streaming
The application

What does NATS do, and why do teams deploy it?

NATS is a messaging system for connecting applications, services, and devices. Clients publish messages on subjects and other clients subscribe to them, with patterns that include publish-subscribe, request-reply, and queue groups that share work across consumers. Subjects are simple dot-separated names, which keeps routing easy to reason about.

The nats-server is written in Go and ships as a single small binary. The optional JetStream layer adds persistence, so messages can be stored in streams and replayed, and it also provides key-value and object storage. Servers can be clustered together. ManageStacks provisions the server with durable storage for JetStream, SSL, and backups so applications can connect right away.

  • Subject-based publish-subscribe messaging between services
  • Request-reply pattern for synchronous-style service calls
  • Queue groups to distribute messages across worker instances
  • JetStream persistence for replayable streams and durable consumers
  • Built-in key-value and object stores on top of JetStream
  • Clustering and leaf nodes for connecting edge deployments
Developer working with code and version control on a laptop
DevTools

Cloud and edge native messaging server for pub/sub, request-reply, and streaming

Open-source alternative

NATS as a self-hosted alternative to Amazon SNS, Google Cloud Pub/Sub and Azure Service Bus

Instead of paying per-seat fees to a SaaS vendor, teams self-host NATS to keep full control of their data and infrastructure. ManageStacks removes the operational overhead — you get the cost and privacy benefits of open source with the reliability of a managed platform.

Replaces Amazon SNSReplaces Google Cloud Pub/SubReplaces Azure Service Bus
Pricing

What does managed NATS hosting cost?

Flat per-app pricing, in your chosen AWS, Azure, or GCP region. No per-user pricing — a busy deployment costs the same as a quiet one.

Starter

$16/app/mo

Staging and internal tools. Dedicated instance, TLS, daily backups, managed upgrades.

Standard

$30/app/mo

Production workloads. Adds monitoring, staging environment, region choice, priority support.

Business

$50/app/mo

High-traffic and compliance workloads. Adds a high-availability replica and same-day support.

24×7 SRE retainer

$499/mo

Round-the-clock on-call across every hosted application, for teams that need a pager answered at 3am.

The honest answer

When is self-hosting NATS the right answer instead?

“Managed hosting is not always the correct call.”

Self-host when a platform team already runs the infrastructure and on-call rotation to operate NATS at genuinely low marginal cost. Self-host when compliance requires an air-gapped or on-premises deployment that no hosted option can satisfy. And self-host when the deployment depends on heavy customisation with a fast internal build-deploy loop, because an internal release process will beat any managed change process.

For everyone else — teams whose engineers have better things to do than shepherd upgrades — managed hosting is cheaper than the hours it replaces.

Infrastructure

Which cloud should NATS run on — AWS, Azure or GCP?

For most workloads, the choice of cloud matters less than proximity: run NATS in the same cloud and region as the applications and data it talks to, because every request between them adds a round trip. The underlying compute performs equivalently across AWS, Azure, and GCP.

In practice, an existing cloud footprint decides it. All plans support all three clouds, and moving regions later is a scheduled migration, not a rebuild.

AWS logo
AWS

Deepest managed-service catalog, default when there's no existing footprint

Azure logo
Azure

Best fit for teams already on Microsoft 365 or Entra ID

GCP logo
GCP

Strongest for data/analytics-adjacent workloads

Circuit board macro representing underlying infrastructure
Multi-cloud

Every plan supports AWS, Azure, and GCP — region choice included.

FAQ

Common questions about NATS on ManageStacks

What is NATS on ManageStacks?

NATS is a lightweight messaging system for connecting services and devices. ManageStacks deploys and maintains the server in your own cloud account, with storage, SSL, and backups configured, so your applications exchange messages over infrastructure that you control.

How does NATS compare to Amazon SNS and SQS?

SNS and SQS are managed AWS messaging services. NATS is a self-hosted server that covers publish-subscribe, queueing through queue groups, and request-reply in one system, and it runs the same way across clouds, which avoids tying messaging to a single provider.

What is JetStream in NATS?

JetStream is the persistence layer built into the NATS server. It stores messages in streams so consumers can replay them or resume after downtime, and it also offers key-value and object storage. Core NATS without JetStream delivers messages without storing them.

Can I migrate from another NATS server to ManageStacks?

Yes. Applications only need the new server's address and credentials. Configuration such as accounts and users can be reused, and JetStream stream definitions can be recreated, with data moved by mirroring or restoring a backup, so you retain your messaging setup.

How do NATS clients authenticate?

NATS supports several methods, including tokens, username and password, and credentials based on signed JWTs through its account system. These let you separate teams or applications into accounts and limit which subjects each one can publish to or subscribe on.

Run NATS without carrying the pager

Subscribe through your AWS, Azure, or GCP marketplace. We handle provisioning, SSL, monitoring, backups, updates, and security. From $16/mo.