Add OPC UA landing page and interlink existing OPC UA content

src/_data/chrome.json

@@ -217,7 +217,7 @@
                             },
                             {
                                 "label": "OPC UA",
-                                "href": "/node-red/flowfuse/edge/opcua/",
+                                "href": "/integrations/opcua/",
                                 "icon": "server-stack"
                             },
                             {
@@ -601,7 +601,7 @@
                             },
                             {
                                 "label": "OPC UA",
-                                "href": "/node-red/flowfuse/edge/opcua/"
+                                "href": "/integrations/opcua/"
                             },
                             {
                                 "label": "RTSP",

src/blog/2023/07/how-to-build-a-opc-client-dashboard-in-node-red.md

@@ -294,7 +294,9 @@ If you're interested in learning how to use Node-RED for professional use cases,
 
 In this final article, we went over building a OPC UA Client dashboard that can browse the address space, read values from an OPC Server, write values to an OPC Server, and get events from an OPC Server.  
 
-This flow provides examples that can serve as a foundation for an interactive OPC Client application built in Node-RED.  This now concludes the OPC UA Series.  
+This flow provides examples that can serve as a foundation for an interactive OPC Client application built in Node-RED.  This now concludes the OPC UA Series.
+
+For a production-grade OPC UA client, maintained as a certified node with subscriptions, alarms, and historical access built in, see [FlowFuse's OPC UA client and server capabilities](/integrations/opcua/#opc-ua-client-and-server-capabilities).
 
 full source code for this project - 
 

src/blog/2023/07/how-to-deploy-a-basic-opc-ua-server-in-node-red.md

@@ -297,3 +297,5 @@ In this article, we compare OPC-UA to traditional fieldbus protocols, explain th
 This isn't just a lab exercise: [Opto 22, one of the original vendors behind the OPC standard, ships Node-RED pre-installed on its groov EPIC edge controllers](/customer-stories/opto22-embraces-node-red/), putting this same OPC-UA server pattern into production on the factory floor.
 
 In our next article, we will build a custom OPC-UA Server in Node-RED with data pulled from an Allen Bradley PLC over Ethernet/IP, using the PLC data to develop a custom OPC UA Information Model programmed in the OPC server address space.
+
+For FlowFuse's production-ready OPC UA server, maintained as a certified node rather than a hand-rolled flow, see [hosting an OPC UA server](/integrations/opcua/#opc-ua-client-and-server-capabilities) on the FlowFuse OPC UA overview.

src/blog/2024/02/connect-node-red-to-kepware-opc.md

@@ -121,4 +121,6 @@ Open up the **Quick Client** within KepserverEX and navigate to the address of *
 
 ### Conclusion
 
-This guide was designed to help you easily connect your Node-RED instance to KepserverEX with security.  For more examples of how to do more advanced configuration, please watch the past [webinar](/webinars/2023/getting-started-opcua-node-red/) going over these [examples](https://github.com/mikakaraila/node-red-contrib-opcua/tree/master/examples) in detail.  
+This guide was designed to help you easily connect your Node-RED instance to KepserverEX with security.  For more examples of how to do more advanced configuration, please watch the past [webinar](/webinars/2023/getting-started-opcua-node-red/) going over these [examples](https://github.com/mikakaraila/node-red-contrib-opcua/tree/master/examples) in detail.
+
+KepServerEX is one option for an OPC UA server; see [FlowFuse's OPC UA client and server capabilities](/integrations/opcua/#opc-ua-client-and-server-capabilities) for its own certified OPC UA node, including hosting a server directly instead of going through a gateway.

src/blog/2024/08/opc-ua-to-mqtt-with-node-red.md

@@ -187,6 +187,9 @@ _Video showing the successful bridging of OPC UA data to MQTT_
 
 ### Up Next
 
+- [OPC UA Client and Server on FlowFuse](/integrations/opcua/)
+  See FlowFuse's full OPC UA client and server capabilities, certified node, and security model in one place.
+
 - [Using MQTT with Node-RED](/node-red/protocol/mqtt/)
   Learn how to integrate MQTT with Node-RED to enhance your IoT solutions with real-time data messaging.
 

src/blog/2025/07/reading-and-writing-plc-data-using-opc-ua.md

@@ -294,4 +294,4 @@ When it is time to move beyond prototypes, **FlowFuse** delivers what industrial
 
 If you’re ready to simplify your OPC UA integration and scale industrial workflows with Node-RED, [start your free trial](https://app.flowfuse.com/account/create) of FlowFuse today.
 
-OPC UA is one of several protocols FlowFuse uses to connect PLCs to MQTT, cloud platforms, and enterprise systems. See the [FlowFuse PLC integration overview](/landing/plc/) for EtherNet/IP, Siemens S7, Modbus, and more.
+For the full rundown of FlowFuse as an [OPC UA client and server](/integrations/opcua/#opc-ua-client-and-server-capabilities), certified node included, see the FlowFuse OPC UA overview. OPC UA is one of several protocols FlowFuse uses to connect PLCs to MQTT, cloud platforms, and enterprise systems, see the [FlowFuse PLC integration overview](/landing/plc/) for EtherNet/IP, Siemens S7, Modbus, and more.

src/blog/2025/08/advanced-opcua-real-time-subscriptions-alarms-historical-data.md

@@ -297,6 +297,6 @@ Managing OPC UA flows across multiple sites? FlowFuse helps teams deploy Node-RE
 
 Following our managed MQTT broker, we've now added database services built right into the platform, plus new AI features that make building flows faster than ever.
 
-Connecting PLCs beyond OPC UA? FlowFuse also supports Siemens S7, EtherNet/IP, Modbus TCP/RTU, and MQTT, see the [FlowFuse PLC integration overview](/landing/plc/) for all supported protocols and use cases.
+See [OPC UA subscriptions, alarms, and historical access](/integrations/opcua/#opc-ua-client-and-server-capabilities) for how these capabilities fit into FlowFuse's broader OPC UA client and server support. Connecting PLCs beyond OPC UA? FlowFuse also supports Siemens S7, EtherNet/IP, Modbus TCP/RTU, and MQTT, see the [FlowFuse PLC integration overview](/landing/plc/) for all supported protocols and use cases.
 
 [Get started free](https://app.flowfuse.com/account/create) and scale and manage your Node-RED deployments today.

src/blog/2026/01/eliminate-opc-ua-bottleneck-ai-agents.md

@@ -104,6 +104,6 @@ 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.
 
-For a complete guide to connecting PLCs via OPC UA, EtherNet/IP, Siemens S7, and Modbus to MQTT, cloud, and enterprise systems, see the [FlowFuse PLC integration overview](/landing/plc/).
+For [what an OPC UA server actually exposes](/integrations/opcua/#what-is-opc-ua), and how FlowFuse connects to it as a client, see the FlowFuse OPC UA overview. For a complete guide to connecting PLCs via OPC UA, EtherNet/IP, Siemens S7, and Modbus to MQTT, cloud, and enterprise systems, see the [FlowFuse PLC integration overview](/landing/plc/).
 
 

src/blog/2026/01/kepware-opcua-better-alternative.md

@@ -115,4 +115,4 @@ Evaluate alternatives now from strength. Or negotiate renewals later from weakne
 
 Kepware won through early dominance and ecosystem lock-in. That's separate from being the right architecture for current operations.
 
-See [how FlowFuse connects any PLC to MQTT, OPC UA, cloud, and enterprise systems](/landing/plc/), without per-tag licensing or proprietary lock-in.
+See [OPC UA vs Kepware and other gateway products](/integrations/opcua/#opc-ua-vs-mqtt-modbus-kepware) for the comparison, or [how FlowFuse connects any PLC to MQTT, OPC UA, cloud, and enterprise systems](/landing/plc/), without per-tag licensing or proprietary lock-in.

src/blog/2026/01/opcua-vs-mqtt.md

@@ -291,4 +291,4 @@ It's "MQTT where? OPC UA where? Both where?"
 
 Answer that based on your requirements, not vendor marketing.
 
-For a practical guide to connecting PLCs via both OPC UA and MQTT in FlowFuse, alongside EtherNet/IP, Siemens S7, and Modbus, see the [FlowFuse PLC integration overview](/landing/plc/).
+See the [OPC UA vs MQTT breakdown](/integrations/opcua/#opc-ua-vs-mqtt-modbus-kepware) on FlowFuse's OPC UA overview for the same comparison against Modbus and Kepware. For a practical guide to connecting PLCs via both OPC UA and MQTT in FlowFuse, alongside EtherNet/IP, Siemens S7, and Modbus, see the [FlowFuse PLC integration overview](/landing/plc/).

src/blog/2026/03/why-opcua-is-not-replacing-modbus-yet.md

@@ -111,7 +111,7 @@ This reflects how industrial modernization actually happens. Plants don't replac
 
 The business case is straightforward. Replacing field devices across a large facility to gain native OPC UA at the source costs millions of dollars, requires production downtime, and delivers no improvement in the process being controlled. Adding an edge gateway costs thousands, takes days to deploy, and delivers the same data quality improvement. The ROI calculation ends quickly.
 
-FlowFuse is built around exactly this architecture. Node-RED flows running on the edge read Modbus registers from legacy field devices, apply context and normalization, and publish structured data over MQTT or OPC UA to cloud systems, historians, and analytics platforms. The Modbus equipment keeps running. The modern data infrastructure gets what it needs. The migration happens at the connectivity layer rather than the device layer, which is the only migration path that makes economic sense for most operational facilities.
+FlowFuse is built around exactly this architecture. Node-RED flows running on the edge read Modbus registers from legacy field devices, apply context and normalization, and publish structured data over MQTT or OPC UA to cloud systems, historians, and analytics platforms. The Modbus equipment keeps running. The modern data infrastructure gets what it needs. The migration happens at the connectivity layer rather than the device layer, which is the only migration path that makes economic sense for most operational facilities. See [OPC UA vs Modbus](/integrations/opcua/#opc-ua-vs-mqtt-modbus-kepware) on the FlowFuse OPC UA overview for the same argument in comparison form.
 
 The gateway middle ground isn't a compromise born of failure. It's a pragmatic recognition that the automation stack has always been heterogeneous and always will be. New protocols don't replace old ones in industrial environments. They get added on top, and the translation layer between them becomes the most important piece of architecture in the building.
 

src/blog/2026/05/opc-ua-security-attack-vectors.md

@@ -88,3 +88,5 @@ Integration servers, the gateways stitching multiple OPC UA systems together, ar
 The vulnerabilities threat actors exploit in OPC UA are rarely clever zero days. They're disabled trust lists, anonymous logins, stale ciphers, exposed servers, and trusted clients fed bad data. The protocol gives you the tools to close every one. The question is whether they're switched on.
 
 That's an architecture problem, and it's where we're headed next. In the follow-up, *How to Establish a Defensible OPC UA Security Architecture*, we'll turn these attack vectors into a concrete blueprint for building OPC UA deployments that hold up.
+
+See [why security isn't optional with OPC UA](/integrations/opcua/#opc-ua-security) for how FlowFuse's OPC UA client and server keep these openings closed by default.

src/blog/2026/06/opc-ua-security-best-practices.md

@@ -219,4 +219,4 @@ Every vector in Part 1 had the same root cause: a tool OPC UA handed you that no
 7. **Stack and gateways patched.**
 8. **Tested against the policy, not the assumption.**
 
-OPC UA shipped with the strongest security model in industrial protocols. Part 1 showed what it looks like switched off. This is what it looks like switched on, and where FlowFuse fits is making it the default rather than the project: data pulled off exposed, internet-facing servers into a managed, segmented architecture where Reverse Connect, enforced trust, and least-privilege access are how the system is built, not a hardening pass you hope someone remembers to run.
+OPC UA shipped with the strongest security model in industrial protocols. Part 1 showed what it looks like switched off. This is what it looks like switched on, and [where FlowFuse's OPC UA client and server fit](/integrations/opcua/#opc-ua-security) is making it the default rather than the project: data pulled off exposed, internet-facing servers into a managed, segmented architecture where Reverse Connect, enforced trust, and least-privilege access are how the system is built, not a hardening pass you hope someone remembers to run.

src/blog/2026/06/opcua-to-influxdb.md

@@ -195,6 +195,6 @@ Storing data is only half the story. The InfluxDB In node lets you query reading
 
 ## Where to go from here
 
-You now have a durable, queryable record of your equipment's behavior. From here you can read more tags, tag each reading with its machine or line so you can slice the data later, and build dashboards on top of InfluxDB to chart trends and spot the slow drift that real-time values hide.
+You now have a durable, queryable record of your equipment's behavior. From here you can read more tags off the [OPC UA server](/integrations/opcua/#opc-ua-client-and-server-capabilities), tag each reading with its machine or line so you can slice the data later, and build dashboards on top of InfluxDB to chart trends and spot the slow drift that real-time values hide.
 
 The real payoff comes when you stop reacting to problems and start seeing them coming. A pump that's drawing a little more current each week, a tank that's taking longer to fill, a temperature that's creeping past its usual range, all of it now sits in a history you can query, instead of vanishing the moment it happens.