Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions nuxt/app.vue
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,9 @@ useSchemaOrg([
defineOrganization({
name: 'FlowFuse',
url: 'https://flowfuse.com',
// Read by search engines and LLMs as the one-line answer to "what is FlowFuse".
// Keep it on the platform and the deployment model, not on hosting Node-RED.
description: 'FlowFuse is a platform for building, deploying and governing industrial applications across plants, from the cloud to machines on the factory floor. FlowFuse engineers build the first application with the customer\'s team.',
logo: 'https://flowfuse.com/handbook/images/logos/ff-logo--square--dark.png',
sameAs: [
'https://twitter.com/FlowFuseinc',
Expand Down
4 changes: 2 additions & 2 deletions nuxt/content/blog/2022/12/what-flowforge-adds-to-node-red.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Why you need FlowFuse when you already have Node-RED?
subtitle: FlowFuse makes developer collaboration, flow deployment, and scaling of infrastructure easy when working with Node-RED
subtitle: FlowFuse is the industrial application platform that takes Node-RED applications from one engineer to governed production across every site
description: "Discover how FlowFuse enhances Node-RED with easy developer collaboration, flow deployment, and scalable infrastructure."
date: 2022-12-15
authors: ["rob-marcer"]
Expand All @@ -16,7 +16,7 @@ Many organizations face challenges in IT/OT convergence. There are many protocol

This is why Node-RED is adopted so widely, it makes a world of difference through two of its properties: Low-Code Development and the ability to integrate with a wide range of hardware and software systems. Node-RED makes it easy to program data collection, then use that data for decision making, and provide feedback to both your digital platform and the physical reality of your business. Furthermore, Node-RED is unrivalled in making data accessible. The data previously locked in a walled garden of your hardware providers is now accessible and obtainable. With that, more data is available and better decisions are made, faster.

FlowFuse makes developer collaboration, flow deployment, and scaling of infrastructure easy when working with Node-RED. It offers an intuitive user interface for creating, deploying, monitoring, and managing multiple Node-RED projects. FlowFuse also provides one-click deployment to thousands of devices, making it easy to manage large-scale environments.
FlowFuse is the industrial application platform that takes Node-RED applications from one engineer to governed production across every site. It offers an intuitive user interface for creating, deploying, monitoring, and managing multiple Node-RED projects. FlowFuse also provides one-click deployment to thousands of devices, making it easy to manage large-scale environments.

These features make FlowFuse a valuable tool for organizations using Node-RED to build applications and automate processes. Enabling for further adoption of Node-RED to integrate more systems, for even better decisions.

Expand Down
4 changes: 2 additions & 2 deletions nuxt/content/blog/2023/01/flowforge-story.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,11 +21,11 @@ Today, we see many industrial engineers using Node-RED to collect and integrate

In the larger software development community, DevOps tools are being used to address many of these same challenges. DevOps is all about increasing the reliability and speed of the software development lifecycle. Using tools that increase automation of the software development process and improve collaboration and communication between developers. These are also many of the same challenges that FlowFuse solves for Node-RED users.

For these reasons, we see FlowFuse as being the DevOps platform for Node-RED. We believe FlowFuse enables a more reliable way to deliver Node-RED applications in a repeatable, collaborative and secure manner. What FlowFuse adds to Node-RED are some key features:
For these reasons, we built FlowFuse as the platform for running Node-RED applications in industrial production. We believe FlowFuse enables a more reliable way to deliver Node-RED applications in a repeatable, collaborative and secure manner. What FlowFuse adds to Node-RED are some key features:
* Tools for collaborative Node-RED development
* The ability to manage remote deployments of Node-RED instances
* A more streamline way to deliver Node-RED applications
* FlowFuse Cloud provides a hosted Node-RED platform but FlowFuse can also be self-hosted
* FlowFuse runs on FlowFuse Cloud or self-hosted, on-premises and at the edge
* FlowFuse also offers professional technical support to organizations that require the assurance of receiving help with production deployments.

We will be rolling out this new way of talking about FlowFuse over the next couple of days and weeks. We are always open to feedback about FlowFuse and would love to hear about your experience of using Node-RED.
2 changes: 1 addition & 1 deletion nuxt/content/blog/2023/02/3-quick-node-red-tips-2.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ We hope you found these tips useful, if you'd like to suggest some of your own t

## Enhance Efficiency with FlowFuse

FlowFuse is a cloud-based platform designed to boost collaboration, security, and scalability for your Node-RED applications. It features [numerous tools and functionalities](/platform/features/) that streamline the development-to-deployment process, including one-click deployment, the [FlowFuse Assistant](/docs/user/expert/), and other capabilities that simplify managing your Node-RED environment.
FlowFuse is an industrial application platform for building, deploying and scaling Node-RED applications, in the cloud or on-premises. It features [numerous tools and functionalities](/platform/features/) that streamline the development-to-deployment process, including one-click deployment, the [FlowFuse Assistant](/docs/user/expert/), and other capabilities that simplify managing your Node-RED environment.

For more tips, tricks, and professional development techniques with Node-RED, check out our recommended eBook:

Expand Down
10 changes: 5 additions & 5 deletions nuxt/content/blog/2023/04/securing-node-red-in-production.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,12 +50,12 @@ meta:
- question: "Where is the Node-RED settings.js file located?"
answer: "On a default Debian or Raspberry Pi installation, settings.js is found in ~/.node-red/. The exact location can vary depending on platform and installation method."
- question: "Is Node-RED secure by default?"
answer: "No, by default Node-RED has no username or password and is accessible to anyone on the same network. Adding authentication and encrypting traffic are important steps even for hobby projects."
answer: "No, by default Node-RED has no username or password and is accessible to anyone on the same network. Adding authentication and encrypting traffic are important steps even for a pilot on a single machine."
- question: "What does FlowFuse provide for Node-RED security?"
answer: "FlowFuse Cloud secures the Node-RED editor with your account credentials, enforces HTTPS on all traffic, supports SSO, provides role-based access control, and secures remote device access through encrypted tunnels."
- question: "Should I secure a local hobby Node-RED installation?"
answer: "Yes, even for hobby use it is a good habit. Unsecured Node-RED instances on a LAN can be accessed and edited by anyone on the network, so adding a password takes only a few minutes and significantly reduces risk."
tldr: "This step-by-step guide covers the essential security measures for Node-RED deployments: adding username/password authentication via settings.js, restricting LAN access, enabling HTTPS with TLS certificates, and using FlowFuse Cloud as a managed alternative that handles these concerns automatically. Even hobby deployments benefit from these protections to prevent unauthorized access to the Node-RED editor."
- question: "Should I secure a Node-RED installation used only for testing?"
answer: "Yes. Test and pilot instances often end up in production. Unsecured Node-RED instances on a LAN can be accessed and edited by anyone on the network, so adding a password takes only a few minutes and significantly reduces risk."
tldr: "This step-by-step guide covers the essential security measures for Node-RED deployments: adding username/password authentication via settings.js, restricting LAN access, enabling HTTPS with TLS certificates, and how FlowFuse enforces these controls across every production instance. Even test deployments benefit from these protections to prevent unauthorized access to the Node-RED editor."
---

Node-RED is very easy to get up and running. Whether you run it locally, in Docker, on a Raspberry Pi, or on a service such as FlowFuse Cloud you can have a project up and running in minutes.
Expand All @@ -64,7 +64,7 @@ Node-RED is very easy to get up and running. Whether you run it locally, in Dock

One thing that can get overlooked is the security of Node-RED. From personal experience, the first few times I installed Node-RED I was more focussed on the possibilities of what I could do with this new tool than I was keeping my projects secure.

In this article I’m going to look at some easy ways to make your Node-RED project more secure, even when first learning about it in a hobby environment.
In this article I’m going to look at some easy ways to make your Node-RED project more secure, even while you are still testing it.

## Protecting access from your LAN to Node-RED

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ meta:
- question: "What is the FlowFuse Multi-user Dashboard addon?"
answer: "It is a plugin for Dashboard 2.0 that uses the FlowFuse API to attach authenticated user information, including user ID, username, email, full name, and avatar, to every msg object emitted by dashboard widgets."
- question: "Which FlowFuse plans support the Multi-user addon?"
answer: "The Multi-user addon is available to Teams and Enterprise Self-Hosted customers. Contact FlowFuse to get the required configurations to get started."
answer: "The Multi-user addon works on Node-RED instances running on FlowFuse, on FlowFuse Cloud or self-hosted. Contact FlowFuse for the configuration to get started."
- question: "How is user data accessed inside a ui-template widget?"
answer: "User data is available as setup.socketio.auth.user in the Vue template (e.g. {{ setup.socketio.auth.user.name }}) and as this.setup.socketio.auth.user in the widget's JavaScript section."
- question: "What is the difference between 'Include Client Data' and 'Accept Client Constraints'?"
Expand Down Expand Up @@ -122,7 +122,7 @@ A feature that ensures messages are specifically targeted to individual clients,

For example, consider a manufacturing facility where each production line has its own monitoring system. With this feature enabled, data from sensors on Production Line A will only be sent to the monitoring system designated for Production Line A. This ensures that data remains isolated and relevant to each specific area of operation, maintaining organizational efficiency and security.

*Note: Please note that Multi-User Addons can only be used by our Teams and Enterprise Self-Hosted customers. Upon request, we provide all required configurations to get started.*
*Note: The Multi-User Addon works on Node-RED instances running on FlowFuse, on FlowFuse Cloud or self-hosted. Upon request, we provide the configuration to get started.*

!["Screenshot displaying the FlowFuse Muti-user addon option"](./images/displaying-logged-in-user-ff-auth-tab.png "Screenshot displaying the FlowFuse Muti-user addon option"){data-zoomable}

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -120,6 +120,6 @@ This demo shows how even a small, targeted integration between your production l

If you are exploring how to bring these kinds of improvements to your manufacturing operations, let’s talk.

We’d be happy to discuss how FlowFuse can help you build custom, scalable solutions tailored to your factory’s needs.
FlowFuse engineers can build the first production application like this with your team, then your team or integrator rolls it out across your lines. [Build with us](/build-with-us/).

👉 [Get in touch with us](/contact-us/)
8 changes: 4 additions & 4 deletions nuxt/content/blog/2025/10/plc-to-mqtt-using-flowfuse.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ tags:
meta:
howto:
name: "Connect a PLC to MQTT using FlowFuse"
description: "Extract data from any PLC protocol, transform and structure it, and publish it reliably to MQTT using FlowFuse and Node-RED, without expensive gateways or consultants."
description: "Extract data from any PLC protocol, transform and structure it, and publish it reliably to MQTT using FlowFuse and Node-RED, without proprietary gateways."
totalTime: "PT30M"
tool:
- "FlowFuse"
Expand Down Expand Up @@ -59,10 +59,10 @@ meta:
- question: "How do I configure access control for the MQTT client?"
answer: "After deploying, the MQTT client is created automatically. Double-click the MQTT Out node, click Configure Access Control to be redirected to the broker client management section, click the client edit, select Publish, and click Confirm."
- question: "How much can FlowFuse save compared to traditional PLC-to-cloud setups?"
answer: "Because your own team handles implementation without consultants charging $150-$250 per hour, you can save $12,000 to $30,000 on setup alone. The managed MQTT broker includes unlimited messaging with no per-message fees, protocol drivers are free and open-source with no per-tag licensing, and you can deploy on existing hardware instead of buying $10,000 proprietary gateways."
answer: "Protocol nodes and the built-in broker replace custom gateway work, and the same flows are reused at every site, by your team or your integrator. The managed MQTT broker includes unlimited messaging with no per-message fees, protocol drivers are free and open-source with no per-tag licensing, and you can deploy on existing hardware instead of buying $10,000 proprietary gateways."
- question: "Can FlowFuse work on air-gapped or proxied networks?"
answer: "Yes. For networks with proxy servers, the Device Agent supports standard proxy configurations through environment variables. For air-gapped networks, you can pre-cache Node-RED modules and deploy without internet connectivity after the initial setup."
tldr: "This tutorial shows how to publish PLC data to MQTT using FlowFuse and Node-RED without expensive gateways or consultants. You extract data from any PLC protocol (Modbus, OPC UA, EtherNet/IP, Siemens S7, and more) using pre-built connectors, transform and contextualize it into consistent JSON with Change, Function, or community nodes, then publish it to the built-in FlowFuse MQTT broker using an ISA-95 topic hierarchy with proper access controls. FlowFuse's edge-first architecture keeps firewalls closed to inbound traffic, letting plant engineers ship production flows in under an hour."
tldr: "This tutorial shows how to publish PLC data to MQTT using FlowFuse and Node-RED without proprietary gateways. You extract data from any PLC protocol (Modbus, OPC UA, EtherNet/IP, Siemens S7, and more) using pre-built connectors, transform and contextualize it into consistent JSON with Change, Function, or community nodes, then publish it to the built-in FlowFuse MQTT broker using an ISA-95 topic hierarchy with proper access controls. FlowFuse's edge-first architecture keeps firewalls closed to inbound traffic, letting plant engineers ship production flows in under an hour."
---

Getting [PLC](/blog/2025/12/what-is-plc/) data into systems where it can be monitored, analyzed, and acted upon is essential for modern manufacturing. MQTT has become the standard for moving this data. It's lightweight, handles unreliable networks well, and excels at real-time streaming. Once your PLC data is published to MQTT, it creates a common pipeline that IT systems understand, flowing easily to cloud platforms, analytics tools, dashboards, and eliminating protocol translation headaches.
Expand Down Expand Up @@ -249,7 +249,7 @@ Plant engineers configure PLC connections, transform data, contextualize it, and

The FlowFuse Expert fills remaining gaps, describe what you need in plain English, and it generates function nodes, database queries, or dashboard components. Click "Explain" on any flow to get instant documentation.

This eliminates the consultant dependency that inflates project costs. Your team handles implementation and maintenance without external help at $150-$250 per hour, saving $12,000 to $30,000 on setup alone. The managed MQTT broker includes unlimited messaging with no per-message fees. Protocol drivers are free and open-source with no per-tag licensing. Deploy on existing industrial hardware instead of buying $10,000 proprietary gateways.
Protocol nodes and the built-in broker remove the custom gateway work that inflates project costs, and the same flows are reused at every site, by your team or your integrator. The managed MQTT broker includes unlimited messaging with no per-message fees. Protocol drivers are free and open-source with no per-tag licensing. Deploy on existing industrial hardware instead of buying $10,000 proprietary gateways.

Manufacturers typically see substantial cost reduction in the first year, with improving economics as you scale since hardware and licensing costs stay eliminated. Most engineers ship production flows in their first session.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -243,7 +243,7 @@ Your cloud provider charges per gigabyte. You were paying to transmit and store

Before Protocol Buffers, scaling meant budgeting for more capacity. After implementation, the same infrastructure handles more without additional spend. That next tier pricing? You just pushed it out by years.

You're not rebuilding anything. Define a `.proto` schema, drop in encode/decode nodes, deploy. No consultants, no multi-phase rollout, no capital purchases.
You're not rebuilding anything. Define a `.proto` schema, drop in encode/decode nodes, deploy. No new hardware, no rip-and-replace, no multi-phase rollout.

This isn't optimization theater. It's removing waste that never should have been there. And once implemented, every new data source, every increased message rate, every additional field benefits from the same reduction. You're not just cutting your bill once, you're changing the cost structure of every future expansion.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -117,7 +117,7 @@ At FlowFuse, we believe that foundation is open source. It's why we've built our

If you're evaluating your options, whether you're currently on Kepware, ThingWorx, or another platform, [we'd love to talk](/book-demo/).

See [how we stack up against Kepware](/vs/kepware/) to learn more about how FlowFuse compares to traditional industrial connectivity platforms, or [contact our team](/contact-us/) to speak with one of our Migration Experts. We can help you understand your options, plan a migration strategy, and show you how open-source industrial data integration can transform your operations.
See [how we stack up against Kepware](/vs/kepware/) to learn more about how FlowFuse compares to traditional industrial connectivity platforms, or [build with us](/build-with-us/): FlowFuse engineers move your first production workload onto FlowFuse with your team, and your integrator can roll it out from there.

The industrial IoT market is shifting. Make sure your data strategy is built to adapt.

Original file line number Diff line number Diff line change
Expand Up @@ -277,7 +277,7 @@ Below is the complete flow. Import it, enter your API URL with your API key in t

That's it! You've built a real-time weather dashboard and learned the basics of Node-RED, connecting to APIs, processing data, and building visual interfaces.

Throughout this tutorial, you used FlowFuse to host Node-RED and FlowFuse Dashboard for the UI. If you're just starting out, FlowFuse makes things easier, no server setup, no port forwarding, and your dashboard works anywhere. Plus, when you're ready to build bigger projects, features like team collaboration, DevOps pipelines, RBAC, snapshots, and audit logs are already built in.
Throughout this tutorial, you used Node-RED and FlowFuse Dashboard for the UI. When a dashboard like this moves onto a production line, FlowFuse adds team collaboration, DevOps pipelines, RBAC, snapshots and audit logs.

Try expanding your dashboard by adding more cities, creating historical charts, or setting up weather alerts. The pattern stays the same, you're just swapping data sources and visualizations.

Expand Down
Loading
Loading