Managed NATS with JetStream on Hetzner and UpCloud
BasePilot provisions and operates NATS servers with JetStream on the European cloud providers Hetzner and UpCloud, in your own cloud account or on your own servers, from Germany: for messaging, streams and key-value buckets. The NATS engine is currently offered as a beta.
Operated from Germany. Billed per node and hour. No minimum term.
shop-x7k2f
NATS 2.11
Connection string
tls://app@
Nodes
- n1.shop-x7k2f.nats.basepilot.deMemberHealthy
- n2.shop-x7k2f.nats.basepilot.deMemberHealthy
- n3.shop-x7k2f.nats.basepilot.deMemberHealthy
NATS at a glance
What a NATS cluster on BasePilot consists of.
- Versions
- 2.11, 2.10
- Default version
- NATS 2.11
- Port
- 4222
- Nodes per cluster
- 1 to 3
- Replication
- Full mesh of equal nodes
- Backups
- Scheduled snapshots of every stream
- Point-in-time restore
- No
- Major version upgrades
- No
- Availability
- Beta
What managed NATS includes
Specific to NATS. Monitoring, maintenance windows, access control and hourly billing come with every cluster.
JetStream included
Streams, consumers, key-value buckets and object store buckets are available on every cluster.
Clustered over the private network
The nodes of a multi-node cluster form a full mesh with mutual TLS. Clients connect to any node over TLS and learn about the others.
One or three nodes
JetStream needs a majority of the nodes. Run a single node, or three for availability: a two-node cluster loses JetStream while one node is down.
Users with subject permissions
Users are admin, read-write or read-only, which determines what they may publish, subscribe to and delete. Changes apply without a restart.
NATS commands in the browser
The studio runs a subset of the nats CLI: publish, request and subscribe, and manage streams, consumers and key-value buckets.
Stream backups
Scheduled snapshots of every stream, messages and configuration included, are stored in object storage and can be restored into a new cluster.
Built and operated in Europe
BasePilot is a German service on European infrastructure. You decide in which data centre each cluster runs.
- Operator in Germany
- BasePilot is developed and operated in Erfurt, Germany. Contracts are governed by German law.
- European cloud providers
- The servers come from Hetzner (Germany) and UpCloud (Finland). You choose the data centre location for every cluster yourself, for example in Germany or Finland.
- Data processing under the GDPR
- We process the data in your databases solely on your behalf and on your instructions. A data processing agreement under Art. 28 GDPR is available on request.
- Analytics only with consent
- This website measures visits only if you agree; without your consent it sets no cookies. The console uses only technically necessary cookies.
Questions about managed NATS
Short answers on versions, operation and limits.
- Which NATS versions does BasePilot offer?
- NATS 2.11, 2.10. New clusters use NATS 2.11 by default.
- How many nodes should a NATS cluster have?
- One or three. JetStream needs a majority of the nodes to operate, so a two-node cluster loses JetStream while one node is down.
- Are core NATS messages backed up?
- No. Core NATS messages are not persisted. Backups contain the JetStream streams, which include key-value and object store buckets.
- Can I create several accounts?
- No. Every user of a cluster belongs to one application account with JetStream enabled.
- What does beta mean for NATS?
- The NATS engine is provided for evaluation: it may still contain defects and may change. We recommend not using it for business-critical data yet.
Other engines
BasePilot operates these engines in the same way.
Start with your first cluster
Create an account, choose an engine, a size and a region, and connect within minutes.