Hanzo PubSub
NATS JetStream messaging
Managed NATS with JetStream for durable messaging. At-least-once delivery, key-value stores, object stores, and request-reply patterns. The backbone of Hanzo Cloud.
More Than Pub/Sub
Durable streams, key-value, object store, and request-reply in one system.
JetStream Streams
Durable, replicated message streams. Replay from any point. Retention by time, count, or size.
At-Least-Once
Acknowledged delivery with consumer groups. No message loss. Exactly-once deduplication.
Key-Value Store
Distributed KV built into NATS. Watch for changes. TTL expiration. History per key.
Request-Reply
Synchronous request-reply pattern. Service discovery. Load-balanced queue groups.
Object Store
Store and retrieve large objects via NATS. Chunked uploads. Watch for changes.
Auth & TLS
NKey and JWT-based authentication. TLS encryption. Per-subject authorization.
Publish and Subscribe
nc, _ := nats.Connect("nats://pubsub.hanzo.ai:4222")
js, _ := nc.JetStream()
// Create a durable stream
js.AddStream(&nats.StreamConfig{
Name: "EVENTS",
Subjects: []string{"events.>"},
Storage: nats.FileStorage,
Replicas: 3,
})
// Publish
js.Publish("events.user.signup", []byte(`{"id":"usr_123"}`))
// Durable consumer with ack
sub, _ := js.PullSubscribe("events.>", "my-service")
msgs, _ := sub.Fetch(10)
for _, msg := range msgs {
process(msg.Data)
msg.Ack()
}25% of compute goes back to open source
Every deployment is SBOM-verified. Contributors to NATS JetStream earn a share of compute revenue — transparent, on-chain, and customizable by the community.
25% of compute goes back to OSS authors
Every Hanzo deployment tracks software dependencies via SBOM. When your code powers compute on Hanzo, the authors get paid — automatically.