Creating the first decentralized, secure global utility, powered by NATS.io, to connect all digital systems, services and devices. #ConnectEverything

San Mateo, CA
We are seeing a bunch of innovative companies settle on this pattern.
MQTT was built to get data off a device over a thin, unreliable link. It does that well, and Ignition already speaks it. Carrying forty sites, two regions and every application in the company is a different job. Keep MQTT at the edge and add a @nats_io backbone behind it.
2
4
952
MQTT was built to get data off a device over a thin, unreliable link. It does that well, and Ignition already speaks it. Carrying forty sites, two regions and every application in the company is a different job. Keep MQTT at the edge and add a @nats_io backbone behind it.
1
2
9
1,272
Ignition publishes Sparkplug B into a NATS cluster sites. Sites link outbound to one enterprise hub, apps can ask a site for what they need, and the history stays at the site. We're at ICC in Sacramento this week w/ h @InductiveAuto community. Stop by booth 45 to talk @NATS_io!
1
2
227
Synadia retweeted
Happy Friday #NATSioFanClub! #ICYMI NATS v2.15 has been released this week 🌟 Check out our summary blog post about the release, then go kick the tires. We ♥️ community feedback and hearing how you are using NATS to do cool stuff. nats.io/blog/nats-server-2.1…
1
2
9
508
A new queue means a change ticket. Edge sites go dark when the uplink does. The other cloud is a standby nobody has tested. All three are messaging problems. We're spending 90 minutes on each one this October. Three live workshops, free, led by the engineers who maintain NATS: October 8 — Your Legacy Broker Is on Borrowed Time "Move off Solace" is a decision, not a plan. How topics, queues and guaranteed messaging map onto NATS, and how a phased cut-over actually works. You'll leave with a concept-mapping cheat sheet and a migration checklist. October 14 — Your MQTT Broker Is Holding You Back Keep MQTT, add the backbone. Devices connect unchanged to the built-in MQTT endpoint, one namespace spans your sites, and data survives a site outage instead of leaving with the uplink. October 20 — Your Standby Cloud Won't Save You Where JetStream replicas and mirrors belong, why three clouds keep quorum where two can't, and what happens when an entire cloud goes dark. Each session is built on a use case we help enterprises ship every week. Register: synadia.com/lp/enterprise-na…
1
3
11
389
Excited to attend this one in person. Some good conversations on @nats_io as the central nervous system with MQTT and other OT protocols as the last mile connectivity. Also be fun to chat a bit about SynapseMQ.
Replace your MQTT broker! 𝘞𝘪𝘵𝘩𝘰𝘶𝘵 replacing MQTT devices at the edge. That's what we'll be talking about next week at ICC - @InductiveAuto's annual user conference! If you'll be in Sacramento, stop by to learn how you can replicate what @Verrus and Christopher Coco have built by integrating @NATS_io with Inductive Automation's Ignition SCADA platform - instead of relying on MQTT as their bridge from edge site to cloud
2
5
725
Replace your MQTT broker! 𝘞𝘪𝘵𝘩𝘰𝘶𝘵 replacing MQTT devices at the edge. That's what we'll be talking about next week at ICC - @InductiveAuto's annual user conference! If you'll be in Sacramento, stop by to learn how you can replicate what @Verrus and Christopher Coco have built by integrating @NATS_io with Inductive Automation's Ignition SCADA platform - instead of relying on MQTT as their bridge from edge site to cloud
1
7
946
Feels a bit strange replacing products I designed in the 90s with @nats_io, but we have learned so much and networks and intelligent connections to its have changed as well. Looking to modernize your system, I’d like to hear from you. DMs open.
Replying to @nats_io
See what a migration from TIBCO EMS to NATS looks like - and how our experts can help synadia.com/blog/tibco-to-na…
2
9
889
Moving off TIBCO RV is the easy part. Subjects, wildcards, and request-reply basically carry right over to @nats_io. EMS is the bigger lift. There's no drop-in JMS adapter, so it's an application migration too. Fortunately, our team knows a thing or two about TIBCO products...
1
1
5
282
Synadia retweeted
Having AI understand a system deeply and have the data to drive insights and conclusions is the future of all software systems.
Is @nats_io in your critical path? Will your on-call eng recall the nuances of NATS during an incident? With Insights, you don't have to find out!
4
10
1,010
Is @nats_io in your critical path? Will your on-call eng recall the nuances of NATS during an incident? With Insights, you don't have to find out!
1
3
6
1,529
Granular data on your entire NATS system - that never leaves your env! - means Insights is ready for whatever questions you or your AI agents might have. synadia.com/insights
2
202
Synadia retweeted
Summer is winding down, so settle in with some light NATS reading 📰 NATS Monthly for August '26 is here! What's inside 👀 📌NATS v2.14.5 released! 📌Two new NATS guest posts 📌NATS @opentelemetry Collector, and more! synadia.com/newsletter/nats-…
1
1
7
515
Earlier this year, we surveyed 500 engineers about their edge systems. We didn't ask any questions about @NATS_io, Kafka, or MQTT. We focused on how they felt about their edge deployments:
1
3
9
358
We think the results above speak for themselves! No broker is more capable or more trusted for edge to cloud use cases than @NATS_io
1
1
84
Synadia retweeted
As more intelligence moves to the edge more folks discover what is missing. @synadia specializes in bringing a consistent infrastructure and security stance for connectivity, micro-services, streams and KV stores between cloud and edge. Even more important as Agentic AI starts migrating to the edge.
The next competitive advantage isn’t putting AI at the edge. It’s operating it without humans constantly stepping in.
2
11
931
Why do more than 2 in 3 edge computing teams say they'd overhaul their current edge setup if given the chance? Could it be the "glue code" tax? 62% of edge teams spend more time maintaining glue code and integrations than supporting new products or capabilities
1
4
5
409
Or maybe it's that 70% of teams say edge requirements from the business are outpacing their ability to keep up. We surveyed 500 edge practitioners to better understand the state of edge computing in 2026. So what would (or should) they build differently the second time around?
1
88