I am Vadym Rozov, founder of BroLabel , where we are building BroSettlement : API-first, noncustodial MPC wallet, ledger, and settlement infrastructure for fintech, iGaming, and crypto-native platforms. A wallet transaction is not one synchronous request. It moves through policy checks, MPC signing, blockchain broadcast, confirmation, ledger posting, and client notification, and any of those stages may be delayed or fail independently. We selected NATS early in the architecture—not as a replacement for another broker, but to avoid coupling every service through synchronous calls as the platform grew. Read more...

Guest post by David Farah and Sven Jonscher, creators of Cotal . We build Cotal, the open standard for AI agents to work together in one shared space. Our first multi-agent prototypes taught us where the real difficulty lives: in the wiring between agents. Who can talk to whom? What happens to a message when the recipient is busy? Who is even online right now? Most frameworks settle those questions for you by imposing a single shape, usually a controller handing out work to workers that never talk to each other. Read more...

Agent systems are becoming distributed systems, and NATS already solves many of the communication problems those systems are rediscovering. NATS has long been a natural fit for distributed, heterogeneous systems. No matter where your devices run, what languages your services use, or how ephemeral your clients are, it gives them a simple way to find and talk to one another. It also easily bridges different cloud vendors, geographies, runtimes, or hardware—with an integrated security model that naturally extends everywhere NATS does. Read more...

When we released NATS Server 2.12 back in September, we reflected on the need for shorter and more routine release cycles. While we slipped slightly beyond the intended six months due to increased activity on AI security reviews and disclosures, we’re happy to announce the release of NATS Server 2.14 today. This release brings some new and welcome improvements, including first-class support for high-throughput publishing into JetStream, extended server-side message scheduling and correctness fixes for sourcing and mirroring with Interest and WorkQueue streams. Read more...

We are thrilled to announce that NATS Server 2.12 is here! 🎉 A successful 6-month release cycle When we released the 2.11 version of the server back in March, we mentioned in our release blog that the 2.10.x series was our longest yet, having reached 26 patch releases. With that, we have reflected on the need to be more predictable and transparent with our releases and have moved to a 6-month release cycle. Read more...

After replacing RabbitMQ with NATS, Sophotech saw major improvements in performance and simplicity — here are their takeaways: High-level overview Sophotech migrated their ~50-service cluster from RabbitMQ to NATS. The change cut p99 latency from ~150 ms to ~40 ms, reduced ops overhead from several hours a week to under one, and eliminated queue lag during bursts (minutes -> seconds). Simpler subject-based routing also removed the need for complex RabbitMQ topology, making the system easier to operate and scale. Read more...

Important Notice for NATS.io Users on Bitnami Helm Charts If you’re running NATS using Bitnami Helm charts, we strongly recommend migrating to the official NATS charts maintained by Synadia. Why migrate now? Bitnami is deprecating the majority of it’s community tier helm charts, including NATS Legacy Bitnami images stop receiving updates on August 28th Future access to NATS via Bitnami will require a paid Bitnami Secure Images subscription The solution: Switch to the official NATS Helm charts, maintained by the team at Synadia Read more...

Just added to Orbit.go is the new client-side implementation of a frequently requested feature: ‘ partitioned consumer groups ’ for NATS JetStream! This library is so named because what it implements is functionally equivalent to what Apache Kafka calls ‘consumer groups’ and how they implement partitioning, although the functionality is not unique to Kafka. It is purely implemented by the clients using the library but requires new server functionalities introduced with NATS server version 2. Read more...

We are thrilled to announce that NATS Server 2.11 is finally here! We want to extend a heartfelt thank you to everyone who contributed through discussions, issue reporting, code contributions, and testing early versions. ❤️ A Long Journey to 2.11 The 2.10.x series was our longest yet, having currently reached 26 patch releases. Throughout this extended period, our ongoing commitment to testing and quality assurance delivered excellent results, making 2.10.26 the most stable and reliable release to date. Read more...

This is the first part of a two-part series explaining how Vitrifi leverages NATS.io to build its Workflow Automation Platform. Some Background for Perspective At Vitrifi , we embarked on building a Workflow Automation Platform after discovering that existing solutions couldn’t meet our specific requirements. Our vision was clear - we needed a platform that would: Be fully BPMN 2.0 compatible Provide an intuitive interface for visually designing and simulating workflows Maintain a minimal footprint for deployment flexibility Dynamically scale task workers based on workload Support multi-cloud deployments with high resilience and scalability Process thousands of workflow states per minute with real-time status updates When existing open-source workflow solutions fell short, we took action. Read more...