From db34181fd3fc916001929c9e12264faf61321bb6 Mon Sep 17 00:00:00 2001 From: sumitshinde-84 Date: Wed, 11 Nov 2026 17:52:11 +0530 Subject: [PATCH 1/5] Describe FlowFuse as a deployment, not a service or self-serve hosting FAQ answers, schema and a few posts are what LLMs quote when asked what FlowFuse is and how it is bought. They still said per-instance pricing, "operational within days", hobby Node-RED, migration experts and "no consultants". - Team pages: pricing answers describe a scoped first application instead of per-instance plans. - Pricing FAQ: drop the self-serve annual billing question and the "tailored solution" and Node-RED-instance wording. - Homepage FAQ: the first application goes into production with FlowFuse engineers, instead of "operational within days". - Schema: sitewide Organization description and a SoftwareApplication node on the homepage, with no self-serve offer. - Professional Services and About descriptions follow the same model. - Posts: the 3.0 launch no longer offers a free trial; services and DIY lines (Migration Experts, tailored solutions, consultant savings, "in place of" an integrator) and hosted/hobby Node-RED framing are rewritten. --- nuxt/app.vue | 3 +++ .../blog/2022/12/what-flowforge-adds-to-node-red.md | 4 ++-- nuxt/content/blog/2023/01/flowforge-story.md | 4 ++-- nuxt/content/blog/2023/02/3-quick-node-red-tips-2.md | 2 +- .../blog/2023/04/securing-node-red-in-production.md | 10 +++++----- .../04/displaying-logged-in-users-on-dashboard.md | 4 ++-- .../07/smart-manufacturing-order-panel-flowfuse.md | 2 +- .../blog/2025/10/plc-to-mqtt-using-flowfuse.md | 8 ++++---- .../11/optimize-industrial-data-protocol-buffers.md | 2 +- .../blog/2025/11/ptc-kepware-thingworx-divestment.md | 2 +- .../blog/2025/12/getting-weather-data-in-node-red.md | 2 +- nuxt/content/blog/2025/12/node-red-timer.md | 2 +- .../blog/2026/01/what-is-system-integrator.md | 2 +- nuxt/content/blog/2026/08/flowfuse-release-3-0.md | 8 ++++---- nuxt/content/faq/pricing.yml | 6 ++---- nuxt/pages/about/index.vue | 3 +-- nuxt/pages/build-with-us/index.vue | 2 +- nuxt/pages/index.vue | 12 +++++++++++- nuxt/pages/professional-services/index.vue | 4 ++-- nuxt/pages/teams/automation-controls.vue | 2 +- nuxt/pages/teams/digital-transformation.vue | 2 +- nuxt/pages/teams/maintenance-reliability.vue | 2 +- 22 files changed, 49 insertions(+), 39 deletions(-) diff --git a/nuxt/app.vue b/nuxt/app.vue index 97c28574fa..6bc085c910 100644 --- a/nuxt/app.vue +++ b/nuxt/app.vue @@ -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 the edge-native platform for industrial applications. Manufacturers use it to build, deploy and govern production applications across their plants, and FlowFuse engineers build the first one with their team.', logo: 'https://flowfuse.com/handbook/images/logos/ff-logo--square--dark.png', sameAs: [ 'https://twitter.com/FlowFuseinc', diff --git a/nuxt/content/blog/2022/12/what-flowforge-adds-to-node-red.md b/nuxt/content/blog/2022/12/what-flowforge-adds-to-node-red.md index ec933101b4..0e2e592b97 100644 --- a/nuxt/content/blog/2022/12/what-flowforge-adds-to-node-red.md +++ b/nuxt/content/blog/2022/12/what-flowforge-adds-to-node-red.md @@ -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"] @@ -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. diff --git a/nuxt/content/blog/2023/01/flowforge-story.md b/nuxt/content/blog/2023/01/flowforge-story.md index 6713413557..d9dae44de8 100644 --- a/nuxt/content/blog/2023/01/flowforge-story.md +++ b/nuxt/content/blog/2023/01/flowforge-story.md @@ -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. \ No newline at end of file diff --git a/nuxt/content/blog/2023/02/3-quick-node-red-tips-2.md b/nuxt/content/blog/2023/02/3-quick-node-red-tips-2.md index c5e99f38a1..33ec6af95f 100644 --- a/nuxt/content/blog/2023/02/3-quick-node-red-tips-2.md +++ b/nuxt/content/blog/2023/02/3-quick-node-red-tips-2.md @@ -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: diff --git a/nuxt/content/blog/2023/04/securing-node-red-in-production.md b/nuxt/content/blog/2023/04/securing-node-red-in-production.md index 07de5239e4..3ad77244a5 100644 --- a/nuxt/content/blog/2023/04/securing-node-red-in-production.md +++ b/nuxt/content/blog/2023/04/securing-node-red-in-production.md @@ -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. @@ -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 diff --git a/nuxt/content/blog/2024/04/displaying-logged-in-users-on-dashboard.md b/nuxt/content/blog/2024/04/displaying-logged-in-users-on-dashboard.md index 6b6c9f9fee..61c7aafda4 100644 --- a/nuxt/content/blog/2024/04/displaying-logged-in-users-on-dashboard.md +++ b/nuxt/content/blog/2024/04/displaying-logged-in-users-on-dashboard.md @@ -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'?" @@ -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} diff --git a/nuxt/content/blog/2025/07/smart-manufacturing-order-panel-flowfuse.md b/nuxt/content/blog/2025/07/smart-manufacturing-order-panel-flowfuse.md index afa39d14f0..2f68d2326f 100644 --- a/nuxt/content/blog/2025/07/smart-manufacturing-order-panel-flowfuse.md +++ b/nuxt/content/blog/2025/07/smart-manufacturing-order-panel-flowfuse.md @@ -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/) diff --git a/nuxt/content/blog/2025/10/plc-to-mqtt-using-flowfuse.md b/nuxt/content/blog/2025/10/plc-to-mqtt-using-flowfuse.md index 6bdde7a348..c332e5e290 100644 --- a/nuxt/content/blog/2025/10/plc-to-mqtt-using-flowfuse.md +++ b/nuxt/content/blog/2025/10/plc-to-mqtt-using-flowfuse.md @@ -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" @@ -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. @@ -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. diff --git a/nuxt/content/blog/2025/11/optimize-industrial-data-protocol-buffers.md b/nuxt/content/blog/2025/11/optimize-industrial-data-protocol-buffers.md index f6cb03c311..9e9a776cae 100644 --- a/nuxt/content/blog/2025/11/optimize-industrial-data-protocol-buffers.md +++ b/nuxt/content/blog/2025/11/optimize-industrial-data-protocol-buffers.md @@ -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. diff --git a/nuxt/content/blog/2025/11/ptc-kepware-thingworx-divestment.md b/nuxt/content/blog/2025/11/ptc-kepware-thingworx-divestment.md index 59609fe2b2..808a89ab86 100644 --- a/nuxt/content/blog/2025/11/ptc-kepware-thingworx-divestment.md +++ b/nuxt/content/blog/2025/11/ptc-kepware-thingworx-divestment.md @@ -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. diff --git a/nuxt/content/blog/2025/12/getting-weather-data-in-node-red.md b/nuxt/content/blog/2025/12/getting-weather-data-in-node-red.md index c44706be62..8d464cef14 100644 --- a/nuxt/content/blog/2025/12/getting-weather-data-in-node-red.md +++ b/nuxt/content/blog/2025/12/getting-weather-data-in-node-red.md @@ -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. diff --git a/nuxt/content/blog/2025/12/node-red-timer.md b/nuxt/content/blog/2025/12/node-red-timer.md index deb3013c37..9db246bf5d 100644 --- a/nuxt/content/blog/2025/12/node-red-timer.md +++ b/nuxt/content/blog/2025/12/node-red-timer.md @@ -69,7 +69,7 @@ Before following this tutorial, you should have: - A running **Node-RED instance**. For professional development and production deployments, **[FlowFuse](/)** is the recommended platform. If you don’t have an account, [start your free trial](http://app.flowfuse.com) today. -> FlowFuse provides enterprise-grade Node-RED hosting with managed infrastructure, built-in [DevOps tools](/blog/2024/10/how-to-build-automate-devops-pipelines-node-red-deployments/), [MQTT broker](/blog/2025/10/plc-to-mqtt-using-flowfuse/#step-3%3A-set-up-mqtt-with-flowfuse), [database](/blog/2025/08/getting-started-with-flowfuse-tables/), [team collaboration](/blog/2024/12/flowfuse-team-collaboration/) with [granular access control](https://www.youtube.com/watch?v=mb1s1YQIpZY), and seamless scaling capabilities. Whether you need cloud-hosted instances managed by FlowFuse or remote instances running on your edge devices, the platform provides unified management for both. FlowFuse also includes AI-powered features that accelerate flow development and streamline automation projects. From prototyping to mission-critical production deployments, FlowFuse handles the infrastructure complexity so you can focus on building flows. +> FlowFuse is an industrial application platform with managed infrastructure, built-in [DevOps tools](/blog/2024/10/how-to-build-automate-devops-pipelines-node-red-deployments/), [MQTT broker](/blog/2025/10/plc-to-mqtt-using-flowfuse/#step-3%3A-set-up-mqtt-with-flowfuse), [database](/blog/2025/08/getting-started-with-flowfuse-tables/), [team collaboration](/blog/2024/12/flowfuse-team-collaboration/) with [granular access control](https://www.youtube.com/watch?v=mb1s1YQIpZY), and seamless scaling capabilities. Whether you need cloud-hosted instances managed by FlowFuse or remote instances running on your edge devices, the platform provides unified management for both. FlowFuse also includes AI-powered features that accelerate flow development and streamline automation projects. From prototyping to mission-critical production deployments, FlowFuse handles the infrastructure complexity so you can focus on building flows. That's all you need to get started. diff --git a/nuxt/content/blog/2026/01/what-is-system-integrator.md b/nuxt/content/blog/2026/01/what-is-system-integrator.md index 773df2ce05..da90f35282 100644 --- a/nuxt/content/blog/2026/01/what-is-system-integrator.md +++ b/nuxt/content/blog/2026/01/what-is-system-integrator.md @@ -120,7 +120,7 @@ The tools are also changing who can do integration work. Software developers and That's why choosing the right integrator still matters. -::cta-image{src="/blog/2026/01/images/integrator-cta-1.png" alt="Talk to our team about where FlowFuse fits alongside your system integrator, or in place of one" cta="demo"} +::cta-image{src="/blog/2026/01/images/integrator-cta-1.png" alt="Integrator, in-house, or both? Talk to our team about where FlowFuse fits in your setup" cta="demo"} :: ## How to Choose a System Integrator diff --git a/nuxt/content/blog/2026/08/flowfuse-release-3-0.md b/nuxt/content/blog/2026/08/flowfuse-release-3-0.md index 078031aa0e..0c192bd41f 100644 --- a/nuxt/content/blog/2026/08/flowfuse-release-3-0.md +++ b/nuxt/content/blog/2026/08/flowfuse-release-3-0.md @@ -49,7 +49,7 @@ Edge fits teams connecting PLCs, machines, and systems, and businesses standardi Fleet fits telemetry collection, distributed device deployments, and hardware and OEM partners shipping FlowFuse to their own customers. Where Edge gives you depth at each site, Fleet gives you reach across thousands of them. -It's the same strong platform underneath. The difference is which problem each one is tuned for — data center, manufacturing site, or a distributed fleet — so the path from "sign up" to "in production" is shorter for every team, making everything easier from POCs to prod and scaling. +It's the same strong platform underneath. The difference is which problem each one is tuned for — data center, manufacturing site, or a distributed fleet — so the path from first application to production is shorter for every team, making everything easier from POCs to prod and scaling. Every product is enabled by FlowFuse Expert, and every product connects the AI agent you already use. @@ -104,8 +104,8 @@ As soon as applications spread across sites and devices, the hard part shifts fr Explore the [product page](/product/) to decide if FlowFuse Edge, FlowFuse Hub, or FlowFuse Fleet is for you. FlowFuse 3.0 is live today on Cloud and Self-Hosted. -1. [Start a Free Trial of FlowFuse Edge](https://app.flowfuse.com/account/create): All OT teams can request a free 30-day trial immediately; if you're looking to try out FlowFuse Hub or FlowFuse Fleet, just [contact us](/contact-us/) and we'll make it happen. -2. See the full feature set and request [Pricing](/pricing/) -3. [Set up a demo](/book-demo/) to see all of these new features +1. [Build your first production application with us](/build-with-us/): FlowFuse engineers work alongside your team to get one application live on your own equipment and data. +2. See what each product includes on the [pricing page](/pricing/). +3. [Book a demo](/book-demo/) to see the new features. Note: FlowFuse Self-Hosted requires the 3.0 release installed for the new license types and features mentioned in this release. diff --git a/nuxt/content/faq/pricing.yml b/nuxt/content/faq/pricing.yml index 660b1c6ced..828bc012d7 100644 --- a/nuxt/content/faq/pricing.yml +++ b/nuxt/content/faq/pricing.yml @@ -2,16 +2,14 @@ page: pricing title: 'Frequently Asked Questions' items: - question: "What's the difference between Edge and Hub?" - answer: "Edge is a product designed specifically for OT teams and the unique challenges they manage. With Edge, you can connect PLCs, machines, and systems, applying a standardised methodology for deploying automation at scale. This tier comes with everything in the FlowFuse core platform, but also includes support for Device Fleet Updates and Device Group Management. Additionally, this tier includes the OT Certified Nodes collection and deployable OT Application Blueprints.\n\nHub is a product better suited for IT teams moving data between their systems and orchestrating multi-plant installations. For this reason, it includes everything in the FlowFuse core platform, as well as some particularly useful features for this use case. It includes Git Integration, High Availability, BAA for HIPAA, and Protected Instances. It also includes the IT Certified Nodes collection and deployable IT Application Blueprints.\n\nFor customers requiring something between these two featuresets, please [Contact Us](/contact-us/) so we can help build a tailored solution for your environment!" + answer: "Edge is a product designed specifically for OT teams and the unique challenges they manage. With Edge, you can connect PLCs, machines, and systems, applying a standardised methodology for deploying automation at scale. This tier comes with everything in the FlowFuse core platform, but also includes support for Device Fleet Updates and Device Group Management. Additionally, this tier includes the OT Certified Nodes collection and deployable OT Application Blueprints.\n\nHub is a product better suited for IT teams moving data between their systems and orchestrating multi-plant installations. For this reason, it includes everything in the FlowFuse core platform, as well as some particularly useful features for this use case. It includes Git Integration, High Availability, BAA for HIPAA, and Protected Instances. It also includes the IT Certified Nodes collection and deployable IT Application Blueprints.\n\nIf you need capabilities from both, [contact us](/contact-us/) and we'll scope the right combination for your environment." - question: "Can I self-host FlowFuse, or is it cloud only?" answer: "Both are available. Edge, Hub, and Fleet can run on FlowFuse Cloud, fully managed by us, or self-hosted on your own infrastructure - on-premise, in your private cloud, or in a fully air-gapped network. Self-hosted installs are supported on [Docker](/docs/install/docker/) and [Kubernetes](/docs/install/kubernetes/); see the [installation documentation](/docs/install/introduction/) to get started, or [Contact Us](/contact-us/) to discuss a self-hosted deployment for your environment." - question: "How does customer support work for FlowFuse?" answer: "FlowFuse provides active support for Certified Nodes and the FlowFuse platform per the [SLA](/handbook/sales/customer-success/#sla). Customers with these features can get support by [filing a ticket](/support/) or via help information in the [FlowFuse Support Portal](/support/). For general issues related to Node-RED or third party modules, raise issues in the [community forum](https://community.flowfuse.com/)." - question: "How does FlowFuse secure my data?" answer: "FlowFuse employs a layered approach to securing customer data. For a fuller understanding of the mechanisms behind this approach, please read our [security statement](/platform/security/) as well as our [architecture documentation](/docs/contribute/architecture/).\n\nFlowFuse secures user access through username/password, SAML-based SSO, or LDAP, with support for multi-factor authentication and automatic session expiry after 14 days. Access is governed by role-based controls within Teams - Owner, Member, Viewer, and Dashboard roles - while platform-wide admin access is tightly restricted (on FlowFuse Cloud, limited to vetted employees on a need-to-have basis). All administrative and team-level actions are captured in audit logs. On FlowFuse Cloud, data is encrypted at rest with AES-256 (PostgreSQL and AWS EFS), stored in the EU (Ireland), and protected in transit with TLS 1.2 or higher terminated at the edge for both HTTP and MQTT traffic.\n\nOrganizationally, FlowFuse holds SOC 2 Type 1 and Type 2 certifications (audited by Advantage Partners) and maintains formal information security, acceptable use, and data management policies alongside regular security awareness training. The platform is also built to be GxP validation-ready: features like role-based access control, audit logging, instance versioning and snapshots, infrastructure-as-code, and SSO/LDAP integration align with the traceability and change-control expectations of regulated environments such as FDA 21 CFR Part 11 and EU GMP Annex 11, enabling customers to perform their own validation and supplier qualification." - - question: "Does FlowFuse offer annual discounts for FlowFuse Cloud?" - answer: "Yes, Edge customers receive a free month when paying for a year of FlowFuse in advance. Simply choose yearly billing upon signup, or select it from the Billing area in the app." - question: "Are flat-fee or site-wide licenses available?" answer: "It is not possible at this time to purchase an unlimited-use license, but contact us to discuss pricing for your unique use case." - question: "Do you offer discounts for large-scale deployments?" - answer: "Yes, we provide customized volume discounts for use cases requiring hundreds or thousands of Node-RED instances. Please [Contact Us](/contact-us/) to discuss your specific requirements." + answer: "Yes. Rollouts across many lines and sites are priced to match their scale. [Contact us](/contact-us/) to discuss your plans." diff --git a/nuxt/pages/about/index.vue b/nuxt/pages/about/index.vue index ceb1dbe6b9..3ed4583c3e 100644 --- a/nuxt/pages/about/index.vue +++ b/nuxt/pages/about/index.vue @@ -49,7 +49,7 @@ const INVESTORS = [ const JOB_BOARD = 'https://boards.greenhouse.io/flowfuse' -const META_DESCRIPTION = 'FlowFuse provides a complete platform for building, scaling and securing your production Node-RED applications. Accelerate digitalization of your industrial processes with ease.' +const META_DESCRIPTION = 'FlowFuse is the edge-native platform for industrial applications. Manufacturers use it to build, deploy and govern production applications across their plants, and FlowFuse engineers build the first one with their team.' useSeoMeta({ title: 'About', @@ -67,7 +67,6 @@ useSeoMeta({ useSchemaOrg([ defineOrganization({ legalName: 'FlowFuse Inc', - description: META_DESCRIPTION, foundingDate: '2021', founder: [{ name: "Nick O'Leary" }], address: { diff --git a/nuxt/pages/build-with-us/index.vue b/nuxt/pages/build-with-us/index.vue index 796b9e4c6e..0811bc15db 100644 --- a/nuxt/pages/build-with-us/index.vue +++ b/nuxt/pages/build-with-us/index.vue @@ -48,7 +48,7 @@ const STEPS = [ const FAQ = [ { question: 'What happens on the first call?', - answer: 'We talk through the operational problem you want to solve, the equipment and systems involved, and who would be part of the project. If FlowFuse is a good fit, we agree the next step together, usually a session to scope the solution and its value.', + answer: 'We talk through the operational problem you want to solve, the equipment and systems involved, and who would be involved. If FlowFuse is a good fit, we agree the next step together, usually a session to scope the solution and its value.', }, { question: 'Can our team maintain it without you?', diff --git a/nuxt/pages/index.vue b/nuxt/pages/index.vue index 13a2ca1e42..e54be61ed7 100644 --- a/nuxt/pages/index.vue +++ b/nuxt/pages/index.vue @@ -94,7 +94,7 @@ const FAQ = [ { question: 'Do I need Node-RED experience to use FlowFuse?', answer: 'No. FlowFuse Expert, our AI-assisted development tool, lets your team describe what they need in plain language and generates the logic. Your team can build without a steep learning curve.' }, { question: 'Can FlowFuse work with our existing systems?', answer: 'Yes, FlowFuse is designed for brownfield environments. It connects to and extends your existing MES, ERP, SCADA, PLCs, and other systems without replacing them or requiring modifications to core platforms.' }, { question: 'How does FlowFuse handle security and compliance?', answer: 'FlowFuse is SOC 2 Type 1 and Type 2 certified. It supports RBAC, SSO, audit logs, and air-gapped self-hosted deployments for environments with strict network isolation requirements.' }, - { question: 'How long does a typical deployment take?', answer: 'Most teams are operational within days. FlowFuse is designed to start with a single use case and expand, not require a multi-month implementation before delivering value.' }, + { question: 'How long does a typical deployment take?', answer: 'You start with one application on one line, and it goes into production before anything is rolled out further. FlowFuse engineers build that first application with your team, so value comes from the first deployment rather than after a multi-month implementation.' }, ] // base.njk gave the homepage a title of "FlowFuse • " rather than the usual @@ -110,6 +110,16 @@ useSeoMeta({ useSchemaOrg([ defineWebPage({ '@type': 'FAQPage' }), + // States what the product is and how it is bought. No offers/price: FlowFuse is sold + // as a scoped deployment (/build-with-us/), not a self-serve plan. + defineSoftwareApp({ + name: 'FlowFuse', + applicationCategory: 'BusinessApplication', + applicationSubCategory: 'Industrial application platform', + operatingSystem: 'Cloud, Linux, Windows, macOS', + description: 'FlowFuse is the edge-native platform for industrial applications. Manufacturers use it to build, deploy and govern production applications across their plants, and FlowFuse engineers build the first one with their team.', + url: 'https://flowfuse.com/', + }), ...FAQ.map(item => defineQuestion({ question: item.question, answer: faqAnswerText(item.answer) })), ]) diff --git a/nuxt/pages/professional-services/index.vue b/nuxt/pages/professional-services/index.vue index e13f87136d..0832de4e1f 100644 --- a/nuxt/pages/professional-services/index.vue +++ b/nuxt/pages/professional-services/index.vue @@ -1,7 +1,7 @@ @@ -9,7 +9,7 @@ useSeoMeta({
diff --git a/nuxt/pages/teams/automation-controls.vue b/nuxt/pages/teams/automation-controls.vue index d78da62927..5fcdc137bd 100644 --- a/nuxt/pages/teams/automation-controls.vue +++ b/nuxt/pages/teams/automation-controls.vue @@ -148,7 +148,7 @@ const PAGE = { }, { question: 'How is FlowFuse priced?', - answer: 'Per instance. Each plan includes a set number of instances, and there are volume discounts for rollouts of hundreds or thousands. See [FlowFuse pricing](/pricing/), or tell us how many sites you expect and we\'ll model the cost with you, including what the next site adds.', + answer: 'It depends on the scope of your first application and how widely you plan to roll it out. We scope it with you, including what each additional site adds. Edge, Hub and Fleet are listed on [FlowFuse pricing](/pricing/).', }, ], }, diff --git a/nuxt/pages/teams/digital-transformation.vue b/nuxt/pages/teams/digital-transformation.vue index c4c6aacfc9..b5def45e0b 100644 --- a/nuxt/pages/teams/digital-transformation.vue +++ b/nuxt/pages/teams/digital-transformation.vue @@ -138,7 +138,7 @@ const PAGE = { }, { question: 'How is FlowFuse priced when budgets sit with the plants?', - answer: 'Per instance, meaning each running application or connected device. A first plant can start small, each plan includes a set number of instances, and volume discounts apply as the program reaches hundreds or thousands. See [FlowFuse pricing](/pricing/), or tell us how many plants you plan to reach and we\'ll model the cost with you.', + answer: 'It is scoped to your first application and the plants you plan to reach, so a first plant can start without a program-wide commitment. We model the cost with you as the rollout grows. Edge, Hub and Fleet are listed on [FlowFuse pricing](/pricing/).', }, ], }, diff --git a/nuxt/pages/teams/maintenance-reliability.vue b/nuxt/pages/teams/maintenance-reliability.vue index 2486dd335f..f9836cc16f 100644 --- a/nuxt/pages/teams/maintenance-reliability.vue +++ b/nuxt/pages/teams/maintenance-reliability.vue @@ -142,7 +142,7 @@ const PAGE = { }, { question: 'How is FlowFuse priced?', - answer: 'Per instance, meaning each running application or connected device. Each plan includes a set number of instances, and there are volume discounts for rollouts of hundreds or thousands. See [FlowFuse pricing](/pricing/), or tell us how many sites and assets you expect and we\'ll model the cost with you.', + answer: 'It depends on the scope of your first application and how widely you plan to roll it out. We scope it with you, based on the sites and assets you expect to cover. Edge, Hub and Fleet are listed on [FlowFuse pricing](/pricing/).', }, ], }, From 255ee239c4f881a44cffb3bf9ebaff006444e888 Mon Sep 17 00:00:00 2001 From: sumitshinde-84 Date: Wed, 11 Nov 2026 17:57:12 +0530 Subject: [PATCH 2/5] Use plain wording for the FlowFuse description in schema and About "Edge-native" is jargon an LLM repeats without explaining. Say what the platform does and where it runs instead. --- nuxt/app.vue | 2 +- nuxt/pages/about/index.vue | 2 +- nuxt/pages/index.vue | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/nuxt/app.vue b/nuxt/app.vue index 6bc085c910..77012eeb88 100644 --- a/nuxt/app.vue +++ b/nuxt/app.vue @@ -5,7 +5,7 @@ useSchemaOrg([ 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 the edge-native platform for industrial applications. Manufacturers use it to build, deploy and govern production applications across their plants, and FlowFuse engineers build the first one with their team.', + 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', diff --git a/nuxt/pages/about/index.vue b/nuxt/pages/about/index.vue index 3ed4583c3e..bcb2308a12 100644 --- a/nuxt/pages/about/index.vue +++ b/nuxt/pages/about/index.vue @@ -49,7 +49,7 @@ const INVESTORS = [ const JOB_BOARD = 'https://boards.greenhouse.io/flowfuse' -const META_DESCRIPTION = 'FlowFuse is the edge-native platform for industrial applications. Manufacturers use it to build, deploy and govern production applications across their plants, and FlowFuse engineers build the first one with their team.' +const META_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.' useSeoMeta({ title: 'About', diff --git a/nuxt/pages/index.vue b/nuxt/pages/index.vue index e54be61ed7..ce3263e649 100644 --- a/nuxt/pages/index.vue +++ b/nuxt/pages/index.vue @@ -117,7 +117,7 @@ useSchemaOrg([ applicationCategory: 'BusinessApplication', applicationSubCategory: 'Industrial application platform', operatingSystem: 'Cloud, Linux, Windows, macOS', - description: 'FlowFuse is the edge-native platform for industrial applications. Manufacturers use it to build, deploy and govern production applications across their plants, and FlowFuse engineers build the first one with their team.', + 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.', url: 'https://flowfuse.com/', }), ...FAQ.map(item => defineQuestion({ question: item.question, answer: faqAnswerText(item.answer) })), From f400d1a1ad520984761a83bf06260530f6f3fa7a Mon Sep 17 00:00:00 2001 From: sumitshinde-84 Date: Wed, 11 Nov 2026 18:19:01 +0530 Subject: [PATCH 3/5] Point the 3.0 post's last step at the ROI calculator instead of a demo --- nuxt/content/blog/2026/08/flowfuse-release-3-0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nuxt/content/blog/2026/08/flowfuse-release-3-0.md b/nuxt/content/blog/2026/08/flowfuse-release-3-0.md index 0c192bd41f..8e55e1c7de 100644 --- a/nuxt/content/blog/2026/08/flowfuse-release-3-0.md +++ b/nuxt/content/blog/2026/08/flowfuse-release-3-0.md @@ -106,6 +106,6 @@ Explore the [product page](/product/) to decide if FlowFuse Edge, FlowFuse Hub, 1. [Build your first production application with us](/build-with-us/): FlowFuse engineers work alongside your team to get one application live on your own equipment and data. 2. See what each product includes on the [pricing page](/pricing/). -3. [Book a demo](/book-demo/) to see the new features. +3. [Estimate what FlowFuse is worth on your lines](/resources/roi-calculator/) with the ROI calculator, using your own downtime and engineering numbers. Note: FlowFuse Self-Hosted requires the 3.0 release installed for the new license types and features mentioned in this release. From bab2a11c3a8ceaeb943dd1ce0afb214d905a5dbe Mon Sep 17 00:00:00 2001 From: sumitshinde-84 Date: Wed, 11 Nov 2026 18:20:28 +0530 Subject: [PATCH 4/5] Answer the deployment-time FAQ with scope, and fix a repeated word --- nuxt/pages/build-with-us/index.vue | 2 +- nuxt/pages/index.vue | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/nuxt/pages/build-with-us/index.vue b/nuxt/pages/build-with-us/index.vue index 0811bc15db..53e4006f3d 100644 --- a/nuxt/pages/build-with-us/index.vue +++ b/nuxt/pages/build-with-us/index.vue @@ -48,7 +48,7 @@ const STEPS = [ const FAQ = [ { question: 'What happens on the first call?', - answer: 'We talk through the operational problem you want to solve, the equipment and systems involved, and who would be involved. If FlowFuse is a good fit, we agree the next step together, usually a session to scope the solution and its value.', + answer: 'We talk through the operational problem you want to solve, the equipment and systems involved, and who on your team should take part. If FlowFuse is a good fit, we agree the next step together, usually a session to scope the solution and its value.', }, { question: 'Can our team maintain it without you?', diff --git a/nuxt/pages/index.vue b/nuxt/pages/index.vue index ce3263e649..6006f12345 100644 --- a/nuxt/pages/index.vue +++ b/nuxt/pages/index.vue @@ -94,7 +94,7 @@ const FAQ = [ { question: 'Do I need Node-RED experience to use FlowFuse?', answer: 'No. FlowFuse Expert, our AI-assisted development tool, lets your team describe what they need in plain language and generates the logic. Your team can build without a steep learning curve.' }, { question: 'Can FlowFuse work with our existing systems?', answer: 'Yes, FlowFuse is designed for brownfield environments. It connects to and extends your existing MES, ERP, SCADA, PLCs, and other systems without replacing them or requiring modifications to core platforms.' }, { question: 'How does FlowFuse handle security and compliance?', answer: 'FlowFuse is SOC 2 Type 1 and Type 2 certified. It supports RBAC, SSO, audit logs, and air-gapped self-hosted deployments for environments with strict network isolation requirements.' }, - { question: 'How long does a typical deployment take?', answer: 'You start with one application on one line, and it goes into production before anything is rolled out further. FlowFuse engineers build that first application with your team, so value comes from the first deployment rather than after a multi-month implementation.' }, + { question: 'How long does a typical deployment take?', answer: 'It depends on the application, and we agree the timeline when we scope it with you. You start with one application on one line, built with FlowFuse engineers alongside your team, and it goes into production before anything is rolled out further.' }, ] // base.njk gave the homepage a title of "FlowFuse • " rather than the usual From c598eb4b891613f71cd84f547ab63cfc90bc22cf Mon Sep 17 00:00:00 2001 From: sumitshinde-84 Date: Wed, 11 Nov 2026 18:22:53 +0530 Subject: [PATCH 5/5] Leave the Professional Services page to the retirement PR That PR deletes the page and redirects it to /build-with-us/, so editing its description here would only conflict. --- nuxt/pages/professional-services/index.vue | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nuxt/pages/professional-services/index.vue b/nuxt/pages/professional-services/index.vue index 0832de4e1f..e13f87136d 100644 --- a/nuxt/pages/professional-services/index.vue +++ b/nuxt/pages/professional-services/index.vue @@ -1,7 +1,7 @@ @@ -9,7 +9,7 @@ useSeoMeta({