FlowFuse · Yndira-E · Mar 20, 2026 · Mar 20, 2026 · Mar 20, 2026 · Mar 20, 2026
diff --git a/src/blog/2026/01/eliminate-opc-ua-bottleneck-ai-agents.md b/src/blog/2026/01/eliminate-opc-ua-bottleneck-ai-agents.md
@@ -8,6 +8,10 @@ authors: ["sumit-shinde"]
 image: 
 tags:
 - flowfuse
+cta:
+  type: contact
+  title: Turn Your Industrial Data Into Instant Answers
+  description: If you want a single platform to reliably connect OPC UA servers, devices, and data systems—and make that data usable by both people and AI—FlowFuse provides the foundation.
 ---
 
 OPC UA servers store everything. Finding anything takes hours.
@@ -99,4 +103,4 @@ This isn't about replacing people with automation. It's about making the data in
 
 And it's not limited to OPC UA. FlowFuse's MCP approach works the same way across any industrial system—MQTT brokers, Modbus devices, SQL databases, REST APIs, whatever protocols you're running. Same natural language interface, same investigation capabilities, different underlying systems. The infrastructure you have becomes the infrastructure you can actually use.
 
-***If you want a single platform to reliably connect OPC UA servers, devices, and data systems—and make that data usable by both people and AI—FlowFuse provides the foundation. [Contact us to learn more](/contact-us/)***
+
diff --git a/src/blog/2026/01/how-to-integrate-node-red-with-git.md b/src/blog/2026/01/how-to-integrate-node-red-with-git.md
@@ -8,6 +8,10 @@ authors: ["sumit-shinde"]
 image: /blog/2026/01/images/integrate-nr-with-git.png
 tags:
   - flowfuse
+cta:
+  type: demo
+  title: See FlowFuse in Action
+  description: FlowFuse brings Git-style version control, DevOps pipelines, and team collaboration to Node-RED. See how teams are shipping flows with the same discipline as software.
 ---
 
 If you've been using Node-RED in production, you already know the pain points. Flows get complex. Teams grow. Someone makes a change that breaks production at 2 AM. You need to roll back, but which version was working? Who approved this deployment? How do you keep your dev environment in sync with production?
@@ -154,6 +158,4 @@ This bidirectional workflow solves several common challenges. Teams can commit f
 
 ## Conclusion
 
-FlowFuse simplifies everything about running Node-RED at scale—deployment, security, scaling, and team management. Git integration bridges the gap between FlowFuse's DevOps features and your existing development infrastructure. Your flows stay version-controlled, your team stays synchronized, and your operations stay simple.
-
-Want to see how FlowFuse makes Node-RED production-ready? [Book a demo](/book-demo/) and we'll walk you through the entire platform and all its features.
+FlowFuse simplifies everything about running Node-RED at scale—deployment, security, scaling, and team management. Git integration bridges the gap between FlowFuse's DevOps features and your existing development infrastructure. Your flows stay version-controlled, your team stays synchronized, and your operations stay simple.
diff --git a/src/blog/2026/01/kepware-opcua-better-alternative.md b/src/blog/2026/01/kepware-opcua-better-alternative.md
@@ -9,6 +9,10 @@ authors: ["sumit-shinde"]
 image: /blog/2026/01/images/kepware-alternative.png
 tags:
   - flowfuse
+cta:
+  type: contact
+  title: Evaluate Your Options Before New Ownership Does It For You
+  description: FlowFuse connects your PLCs, historians, and cloud systems without per-tag penalties or vendor lock-in. See how teams are cutting Kepware costs while gaining more capability — before your next renewal.
 ---
 
 Kepware isn't chosen, it's assumed. It appears in budgets like line items for electricity or insurance. No one questions it. No one compares it. It just... goes in.
@@ -108,5 +112,3 @@ Kepware functions reliably. That's not disputed. But reliability alone doesn't j
 Evaluate alternatives now from strength. Or negotiate renewals later from weakness under new ownership terms.
 
 Kepware won through early dominance and ecosystem lock-in. That's separate from being the right architecture for current operations.
-
-***If this resonates, let's talk, FlowFuse structures connectivity differently. [Contact Us](/contact-us).***
diff --git a/src/blog/2026/01/node-red-history-community-industrial-iot-flowfuse.md b/src/blog/2026/01/node-red-history-community-industrial-iot-flowfuse.md
@@ -8,6 +8,10 @@ image: /blog/2026/01/images/node-red-story.png
 keywords:
 tags:
  - node-red
+cta:
+  type: sign-up
+  title: Ready to Take Node-RED to Production?
+  description: FlowFuse gives Node-RED everything enterprises need — fleet management, version control, security, and DevOps pipelines. See how teams are scaling from one instance to thousands.
 ---
 
 In late 2011, Nick O'Leary was a "plumber" of the digital age. As part of IBM's Emerging Technology Group, he spent his days building experimental projects that pushed the boundaries of what connected systems could do. But there was a problem: for every new experiment, he found himself writing the same boilerplate code over and over — the tedious "wiring" work needed to make different systems talk to each other.
@@ -181,5 +185,3 @@ What amazes me most is the community's generosity. People don't just solve probl
 If this story touched you, please share it. Someone out there might need the reminder that the impossible is usually just the not-yet-possible.
 
 Thank you for reading, and happy New Year!
-
-If you're facing scaling challenges that led to FlowFuse's creation, [reach out to us](/contact-us/).
diff --git a/src/blog/2026/01/opcua-vs-mqtt.md b/src/blog/2026/01/opcua-vs-mqtt.md
@@ -9,6 +9,10 @@ image: /blog/2026/01/images/opcua-vs-mqtt.png
 keywords: MQTT vs OPC UA, MQTT protocol, OPC UA protocol, industrial communication, IIoT architecture, OPC UA PubSub, MQTT Sparkplug
 tags:
  - flowfuse
+cta:
+  type: contact
+  title: Stop Choosing Protocols. Start Mapping Requirements.
+  description: FlowFuse connects both MQTT and OPC UA natively, so you don't have to pick sides. See how teams are building industrial data architectures that use the right protocol for every data flow.
 ---
 
 The question itself is broken.
@@ -254,5 +258,3 @@ The right question isn't "MQTT or OPC UA?"
 It's "MQTT where? OPC UA where? Both where?"
 
 Answer that based on your requirements, not vendor marketing.
-
-***If you're figuring out how to connect legacy equipment, new sensors, and cloud systems and the answer isn't obvious, we get it. We work through these architecture questions with teams every day. Want to talk through your specific setup? [Get in touch](/contact-us/).***
diff --git a/src/blog/2026/01/what-is-system-integrator.md b/src/blog/2026/01/what-is-system-integrator.md
@@ -26,6 +26,10 @@ meta:
       answer: "Modern system integrators use platforms like Node-RED for visual, flow-based integration and tools like FlowFuse for enterprise management at scale. These enable faster development, support multiple protocols without custom drivers, provide centralized control across deployments, and make systems easier to maintain and modify compared to traditional custom-coded point-to-point integrations."
     - question: "How long does a typical system integration project take?"
       answer: "Project timelines vary significantly based on scope and complexity. Simple integrations connecting a few machines to a cloud platform might take weeks, while comprehensive facility-wide projects integrating legacy equipment with modern enterprise systems can take months. Good integrators provide realistic timelines during planning and account for potential delays from equipment availability, testing windows, and unforeseen technical challenges."  
+cta:
+  type: contact
+  title: Build Integrations Once. Deploy Them Everywhere
+  description: FlowFuse gives system integrators the platform to scale Node-RED across hundreds of sites without custom code on every project, and gives manufacturers the visibility to trust what's running on their floor.
 ---
 
 Most factories don't get built all at once. They evolve. Someone buys a robot in 2018. A conveyor system gets added when production ramps up. Last year, a vision system showed up because quality was slipping. Every piece from a different vendor, every piece with its own manual, its own software, its own way of doing things.
@@ -154,8 +158,4 @@ Whether you're trying to understand what system integrators do, evaluating one f
 
 If you're a system integrator, FlowFuse helps you build integrations once and deploy them everywhere (across hundreds of sites, thousands of devices, without writing custom code for every project). Our platform gives you the tools to scale faster, reduce project complexity, and deliver more value to your clients.
 
-[Learn about our partner program](/partners/referral-sign-up/)
-
-Need a system integrator for your project? We work with experienced integrators who understand modern integration challenges (from legacy equipment to Industry 4.0 initiatives). Whether you're connecting your first machine to the cloud or standardizing integrations across multiple facilities, we can connect you with the right partner.
-
-[Contact us](/contact-us/)
+[Learn about our partner program](/partners/referral-sign-up/)
diff --git a/src/blog/2026/01/why-modbus-still-exist.md b/src/blog/2026/01/why-modbus-still-exist.md
@@ -8,6 +8,10 @@ image: /blog/2026/01/images/why-modbus-wont-dia.png
 keywords: Modbus, industrial automation, PLC, OPC UA, EtherNet/IP, MQTT, legacy systems, industrial protocols, factory automation, FlowFuse
 tags:
  - flowfuse
+cta:
+  type: demo
+  title: Modernize Without the Rip and Replace
+  description: FlowFuse connects your legacy Modbus devices to modern systems without replacing what already works. See how teams are bridging old and new infrastructure on the same platform. 
 ---
 
 Modbus is 47 years old and has no built-in security. By every measure, it should have been obsolete a decade ago. OPC UA, EtherNet/IP, MQTT, Profinet: modern protocols with semantic modeling, encryption, and real-time capabilities arrived backed by billions in vendor investment and industry standardization efforts.
@@ -115,5 +119,3 @@ The result is a patchwork that reflects industrial reality rather than protocol
 This approach proves that Modbus survives not because it's technically superior, but because it solves real problems with minimal friction. The protocol succeeded by being simple enough that anyone can implement it, cheap enough that everyone does, and reliable enough that nobody has to think about it.
 
 FlowFuse is the industrial data platform designed to bridge this gap between legacy Modbus registers and modern enterprise systems. Our platform provides the connectivity and security layers needed to transform aging infrastructure into a secure, data-driven operation. 
-
-***[Book a FlowFuse Demo](https://flowfuse.com/book-demo/)** today to see how we can help you modernize your operations without the "rip and replace" headache.***
diff --git a/src/blog/2026/02/edge-ai-is-80-percent-pipeline-and-20-percent-ai.md b/src/blog/2026/02/edge-ai-is-80-percent-pipeline-and-20-percent-ai.md
@@ -9,6 +9,10 @@ image: /blog/2026/02/images/edge-ai-is-80-20.png
 tags:
   - flowfuse
   - ai
+cta:
+  type: sign-up
+  title: Build the Plumbing That Makes AI Actually Work
+  description: FlowFuse is the operational layer that takes Node-RED to production — device management, snapshot deployments, ONNX-based AI inference, and DevOps pipelines built specifically for the factory floor.
 ---
 
 The model is the easy part. I know that is not what you were told. But it is true, and somewhere between your third deployment and your first production fire, you will stop arguing with it.

diff --git a/src/blog/2026/02/getting-started-with-canbus.md b/src/blog/2026/02/getting-started-with-canbus.md
@@ -8,6 +8,10 @@ authors: ["sumit-shinde"]
 image: /blog/2026/02/images/canbus-tutorial.png
 tags:
 - flowfuse
+cta:
+  type: contact
+  title: Take CAN Bus From Dev to Production
+  description: FlowFuse makes it simple to deploy, monitor, and maintain Node-RED flows across your entire edge fleet, same flows, any hardware, any scale. Get in touch to discuss your project.
 ---
 
 If you work with vehicles, industrial automation, or embedded systems, you've likely encountered **CAN bus**, the communication backbone that connects ECUs, sensors, controllers, and actuators in real-world environments. The challenge isn't just reading CAN data; it's getting that data into your dashboards, cloud platforms, databases, or industrial control systems.
@@ -302,5 +306,3 @@ By combining SocketCAN with FlowFuse, you've eliminated much of the complexity t
 The real power of this approach becomes clear when you consider scalability. The same FlowFuse flows work identically whether you're testing with a virtual CAN interface on your laptop or deploying to production hardware with physical CAN controllers. The abstraction layer provided by SocketCAN means your application logic remains stable even as your hardware requirements evolve.
 
 Once you've connected to your CAN bus, the possibilities expand significantly. You can build real-time monitoring dashboards to visualize CAN data, send telemetry to cloud platforms for analytics and storage, or bridge CAN networks with virtually any other protocol or system. FlowFuse's extensive ecosystem of nodes and integrations supports connections to databases, MQTT brokers, REST APIs, industrial protocols, and more, making it straightforward to integrate your CAN infrastructure into larger IoT and automation workflows.
-
-*Managing Node-RED across multiple edge devices or looking for a platform that makes connecting and scaling easier? FlowFuse makes it simple to deploy, monitor, and maintain your infrastructure at scale. [Get in touch](/contact-us/) to discuss your project and see how we can help.*
diff --git a/src/blog/2026/02/mapping-mtconnect-streams.md b/src/blog/2026/02/mapping-mtconnect-streams.md
@@ -8,6 +8,10 @@ authors: ["sumit-shinde"]
 image: /blog/2026/02/images/mtconnect.png
 tags:
 - flowfuse
+cta:
+  type: contact
+  title: Connect Your CNC Machines to Live Dashboards
+  description: FlowFuse makes it simple to collect MTConnect data, build real-time dashboards, and integrate shop floor equipment with your broader systems, no custom code required. Get in touch to discuss your project.
 ---
 
 Most manufacturing facilities run MTConnect agents on their CNC machines, but the XML data these agents produce isn't directly usable. You receive streams of timestamped measurements, state changes, and condition flags wrapped in hierarchical XML structures. Converting this into a functional dashboard means solving three problems: retrieving the data reliably, parsing it correctly, and routing specific values to the right display components.
@@ -166,6 +170,4 @@ Below is the complete flow configuration. If you've successfully built the dashb
 
 Your MTConnect dashboard is now live, pulling real-time machine data and displaying it through visual widgets. The setup you've built here works the same way across any MTConnect-compliant machine in your facility.
 
-This is what FlowFuse does—it makes connecting to equipment, collecting data, transforming it into useful formats, and visualizing it on dashboards straightforward. Beyond basic monitoring, you can log production metrics to databases for trend analysis, set up automated alerts when machines enter fault states, integrate shop floor data with MES or ERP systems, and build event-driven workflows that respond to machine conditions. For production environments, FlowFuse Enterprise provides role-based access control, audit logging, high availability infrastructure, and dedicated support—giving you the operational controls needed to run manufacturing applications reliably across multiple facilities.
-
-Want to deploy this across your facility? [Contact us](https://flowfuse.com/contact-us/) to discuss your manufacturing monitoring requirements.
+This is what FlowFuse does—it makes connecting to equipment, collecting data, transforming it into useful formats, and visualizing it on dashboards straightforward. Beyond basic monitoring, you can log production metrics to databases for trend analysis, set up automated alerts when machines enter fault states, integrate shop floor data with MES or ERP systems, and build event-driven workflows that respond to machine conditions. For production environments, FlowFuse Enterprise provides role-based access control, audit logging, high availability infrastructure, and dedicated support—giving you the operational controls needed to run manufacturing applications reliably across multiple facilities.
diff --git a/src/blog/2026/02/modbus-tcp-vs-modbus-rtu.md b/src/blog/2026/02/modbus-tcp-vs-modbus-rtu.md
@@ -7,6 +7,10 @@ authors: ["sumit-shinde"]
 image: /blog/2026/02/images/modbus-rtu-vs-tcp.png
 tags:
   - flowfuse
+cta:
+  type: sign-up
+  title: Stop Debugging Modbus at 2 AM
+  description: FlowFuse supports both Modbus RTU and TCP across the full OT/IT stack, with the monitoring, logging, and fleet management to catch problems before they take down the line.
 ---
 
 Modbus shipped in 1979. It has outlasted every protocol that was meant to replace it, survived the transition from relay logic to microprocessors and modern SCADA systems, and is still running production lines today. That kind of longevity does not happen by accident. It exists because the protocol is simple, deterministic, and unambiguous, at least in its original form, a point I have discussed in more detail in a [separate article](/blog/2026/01/why-modbus-still-exist/).
@@ -102,5 +106,3 @@ If you are deploying TCP: isolate Modbus devices on a dedicated VLAN or network
 If you are maintaining a hybrid gateway architecture, resist the urge to rationalize it away. It is doing work.
 
 The two protocols make different guarantees, fail differently, and require different diagnostic skills when something goes wrong. Understanding that distinction before the system is designed costs nothing. Understanding it for the first time during an incident costs considerably more.
-
-*If you are working with either protocol in production, FlowFuse supports both [Modbus RTU](/blog/2025/09/using-modbus-with-flowfuse/) and [Modbus TCP](/node-red/protocol/modbus/) across the full OT/IT stack, so the protocol layer does not become another thing to solve. [Get started here.]({% include "sign-up-url.njk" %})*
diff --git a/src/blog/2026/02/motor-anomaly-detector-ai.md b/src/blog/2026/02/motor-anomaly-detector-ai.md
@@ -7,6 +7,10 @@ authors: ["sumit-shinde"]
 image: /blog/2026/02/images/motor-anomaly-detection-ai.png
 tags:
 - flowfuse
+cta:
+  type: demo
+  title: See How FlowFuse Catches Faults Before They Fail
+  description: Book a demo and see how FlowFuse brings sensor ingestion, AI inference, and real-time alerting together on the factory floor — no separate ML infrastructure required
 ---
 
 Bearing wear, shaft misalignment, and imbalance don't appear overnight. They develop over days or weeks, leaving a clear trail in vibration data long before any audible or thermal symptoms emerge. By the time a technician hears grinding or feels heat, the window for low-cost intervention has already closed.
@@ -533,5 +537,3 @@ Training data quality matters more than model architecture. A model trained on d
 False positives are inevitable in early deployment. External vibration from nearby equipment, transient load spikes, or sensor cable movement can all push the score above threshold momentarily. The rolling average window helps, but it doesn't eliminate them. Treat the first few weeks as a calibration period: log alerts, investigate them, and adjust `THRESHOLD_SIGMA` or the window size based on what you learn. The system improves with attention.
 
 Finally, anomaly detection is an early warning layer, not a maintenance strategy on its own. It tells you to look sooner, not what to do when you get there. Pair it with regular physical inspection, lubrication schedules, and, where possible, a domain expert who can interpret the alerts in context. Used that way, it earns its place. Used as a replacement for those things, it will eventually let you down.
-
-*Most motor failures are predictable. The vibration signature is there weeks before the damage is done. This guide shows how to capture that signal and act on it. FlowFuse brings the full pipeline together in one place: sensor ingestion, feature extraction, and custom-trained AI inference, without managing separate infrastructure. [Try it free]({% include "sign-up-url.njk" %}).*
diff --git a/src/blog/2026/02/mqtt-influxdb-tutorial.md b/src/blog/2026/02/mqtt-influxdb-tutorial.md
@@ -8,6 +8,10 @@ authors: ["sumit-shinde"]
 image: /blog/2026/02/images/mqtt-to-influxdb.png
 tags:
 - flowfuse
+cta:
+  type: sign-up
+  title: Build Pipelines You Can Actually Debug
+  description: FlowFuse turns MQTT-to-InfluxDB and every other IIoT integration into a visual flow. No custom scripts, no silent failures, no mystery at 2am. Start your free trial today.
 ---
 
 An MQTT to InfluxDB is one of the most common and most critical pipelines in IIoT. Every timestamped telemetry event that drives decisions on the floor needs to land somewhere it can be queried, trended, and acted on.