diff --git a/nuxt/components/TeamPage.vue b/nuxt/components/TeamPage.vue
index 07c7eb3137..7f5b7058d7 100644
--- a/nuxt/components/TeamPage.vue
+++ b/nuxt/components/TeamPage.vue
@@ -11,7 +11,7 @@ const props = defineProps<{
hero: { eyebrow: string, title: Heading, subtext: string, imagePlaceholder: string, image?: { src: string, alt: string } }
outcomes: { heading: Heading, intro: string, items: Array<{ label: string, title: string, detail: string, icon: string }> }
solutions: { heading: Heading, intro: string, cards: Array<{ eyebrow: string, title: string, description: string, points: string[], image: { src: string, alt: string, fit: 'cover' | 'contain', video?: string, youtube?: string }, link: { to: string, label: string } }> }
- support: { heading: Heading, intro: string, items: Array<{ title: string, description: string, icon: string }> }
+ support: { heading: Heading, intro: string, items: Array<{ title: string, description?: string, descriptionLinks?: Array<{ text: string, href?: string, destination?: 'signUp' }>, icon: string }> }
proof: { heading: Heading, intro: string, items: Array<{ number: string, text: string }> }
faq: { heading: Heading, items: Array<{ question: string, answer: string }> }
cta: { heading: string, body: string, buttons: Array<'bookDemo' | 'signUp'> }
@@ -206,7 +206,7 @@ useSchemaOrg([
- {{ part.text }}{{ part.text }}
+ {{ part.text }}{{ part.text }}{{ part.text }}
{{ item.description }}
diff --git a/nuxt/content/blog/2022/02/announcing-flowforge-cloud.md b/nuxt/content/blog/2022/02/announcing-flowforge-cloud.md
deleted file mode 100644
index 0588b4af9f..0000000000
--- a/nuxt/content/blog/2022/02/announcing-flowforge-cloud.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: Announcing FlowFuse Cloud
-subtitle: Hosting your Node-RED, so you don't have to.
-description: "FlowFuse Cloud is officially announced. Join the waitlist for early access to FlowFuse's new hosted Node-RED cloud offering."
-date: 2022-02-23 19:44:00.0
-authors: ["zeger-jan-van-de-weg"]
-tags:
- - posts
- - flowfuse
- - news
- - releases
----
-
-As an open core company, anyone is free to [download and install][install-docs]
-our platform. In many cases this is a great solution, it
-allows for custom setups in your own environment. We know this isn't for everyone
-though, some people just want to start building with [Node-RED](/node-red/) without having to manage their servers.
-
-We are excited to announce FlowFuse Cloud, a hosted
-Node-RED as a service offering and today we are opening the waitlist.
-
-[install-docs]: https://github.com/FlowFuse/flowfuse/tree/9219e81399eaf52fb0ee5573707a52f5520fbfdd/docs/install
-
-
-
-Our waitlist captures your email, and we'll reach out to you on that address once your account is created.
-
-### Starting operations
-
-After having released v0.2 recently, we're now working on v0.3 that will include
-a user flow for [billing](https://github.com/FlowFuse/flowfuse/issues/224).
-When that work has been done and deployed people on the waitlist will slowly be invited to the platform.
-Currently that's scheduled for April 1st, no joke, although it could happen either sooner
-or later.
-More details on the exact pricing will be availble nearer the time.
-
-Once you are invited you will be able to;
-- Create multiple Node-RED projects hosted on flowforge.cloud,
-- Invite team members to collaborate on those projects,
-- And many more features will automatically become availble with each new release.
diff --git a/nuxt/content/blog/2022/03/community-news-02.md b/nuxt/content/blog/2022/03/community-news-02.md
index 16e008b2e9..98f361ca2e 100644
--- a/nuxt/content/blog/2022/03/community-news-02.md
+++ b/nuxt/content/blog/2022/03/community-news-02.md
@@ -15,9 +15,6 @@ Welcome to the FlowFuse newsletter, a regular roundup of what\`s happening with
If you've got something that you'd like us to share please email [contact@flowfuse.com](mailto:contact@flowfuse.com).
-[Announcing FlowFuse Cloud](/blog/2022/02/announcing-flowforge-cloud/)
-We are excited to announce FlowFuse Cloud, a hosted Node-RED as a service offering and today we are opening the waitlist.
-
[FlowFuse 0.2](/blog/2022/02/flowforge-02-released/)
We continue to iterate with our 4 weekly releases of the FlowFuse platform.
diff --git a/nuxt/content/blog/2022/03/flowforge-03-released.md b/nuxt/content/blog/2022/03/flowforge-03-released.md
index 77e0d0dce1..2e7e90227a 100644
--- a/nuxt/content/blog/2022/03/flowforge-03-released.md
+++ b/nuxt/content/blog/2022/03/flowforge-03-released.md
@@ -104,6 +104,5 @@ Our regular release cycle puts the next release on Thursday 14th April.
We're still in planning stage for the release, but we'll also be beginning to invite
people from the waiting list to sign-up to FlowFuse Cloud.
-For more information, check out the [annoucement blog post](/blog/2022/02/announcing-flowforge-cloud/).
You can also sign up to our general mailing list below if you want to hear more
about the work we're doing.
diff --git a/nuxt/content/blog/2022/04/flowforge-04-released.md b/nuxt/content/blog/2022/04/flowforge-04-released.md
index ed377ba32d..3b83141138 100644
--- a/nuxt/content/blog/2022/04/flowforge-04-released.md
+++ b/nuxt/content/blog/2022/04/flowforge-04-released.md
@@ -75,7 +75,5 @@ We also have a `#flowfuse` channel on the [Node-RED Slack workspace](https://nod
Our regular release cycle puts the next release on Thursday 12th May.
We will be building on features in the last few releases around managing your projects and using templates, we're also setting the foundations of our work to [manage Node-RED on your own devices running at the Edge](https://github.com/FlowFuse/flowfuse/issues/446).
-For more information, check out the [announcement blog post](/blog/2022/02/announcing-flowforge-cloud/).
-
You can also sign up to our general mailing list below if you want to hear more
about the work we're doing.
diff --git a/nuxt/content/blog/2022/04/flowforge-accepting-customers.md b/nuxt/content/blog/2022/04/flowforge-accepting-customers.md
deleted file mode 100644
index 65cec0c4fb..0000000000
--- a/nuxt/content/blog/2022/04/flowforge-accepting-customers.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: FlowFuse is accepting customers now
-subtitle: We're starting to onboard users from the waitlist
-description: "FlowFuse is now officially accepting customers, starting to onboard users from the waitlist for its new Node-RED cloud platform."
-date: 2022-04-04
-authors: ["zeger-jan-van-de-weg"]
-tags:
- - posts
- - flowfuse
- - news
----
-
-A year ago our CTO, Nick O'Leary, [introduced FlowFuse](/blog/2021/04/first-deploy/).
-Since then major milestones have been achieved. As we grow as a company, important
-steps are taken. Today we make another very important step; we're accepting our
-first customers.
-
-
-
-A few weeks ago our product was nearly in a state where it could support customers,
-when that was the case, we [opened up our waitlist](/blog/2022/02/announcing-flowforge-cloud/).
-The waitlist has been growing daily and now we're ready to start inviting those
-users onto the platform. The first
-lucky few users are being added today, and each working day for the foreseeable
-future we'll continue onboarding users. New users will receive an email from our
-team with their login details and can start creating new workflows with Node-RED
-minutes after.
-
-While the source code of FlowFuse is [available](https://github.com/FlowFuse/flowfuse),
-there's a chance you're unfamiliar with what has been built around Node-RED.
-With FlowFuse, our intent is to build a platform to aid with colaboration of
-flows in Node-RED. The first steps to our vision include a managed Node-RED
-instance to connect virtually any online service. Multiple users will have
-access to the same flows and can collaborate. Further, once Node-RED 3.0 has
-been released, the platform will provide a pain-free way to upgrade and keep
-your projects up to date. There's many more exciting features right around the
-corner on our [roadmap](/changelog/)
diff --git a/nuxt/content/blog/2022/05/sign-up-for-flowforge-cloud.md b/nuxt/content/blog/2022/05/sign-up-for-flowforge-cloud.md
deleted file mode 100644
index 1aec8a0c7b..0000000000
--- a/nuxt/content/blog/2022/05/sign-up-for-flowforge-cloud.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: FlowFuse open for everybody
-subtitle: Sign up and start a new Node-RED project within a minute!
-description: With the waitlist now phased out users can sign up and start using FlowFuse right away and start developing on new projects.
-date: 2022-05-25 09:00:00.0
-authors: ["zeger-jan-van-de-weg"]
-tags:
- - posts
- - flowfuse
- - news
----
-
-FlowFuse wants to enable everyone to build workflows in [Node-RED](/node-red/). Since announcing
-[FlowFuse Cloud](https://flowforge.com/blog/2022/02/announcing-flowforge-cloud/)
-two months ago we've had a waiting list for users to sign up to. That allowed us
-to control the pace we were bringing new users onto the platform, learning what
-is needed to scale up our platform and continue to improve our first user experience.
-
-Today we have removed the waiting list. Anyone can sign up to FlowFuse and start a
-new Node-RED project in under a minute!
-
-
-
-
-
-## What we offer
-
-Besides the sub minute time to start a new Node-RED project, there's many more
-features our offering includes. Two we'd like to highlight.
-
-To start our blog highlight reel: Collaboration. FlowFuse allows you to work
-with a team on your flows. There's the ability to create multiple users, each
-with their own credentials that can alter the flows on Node-RED, and it's
-execution environment like for example the [environments variables](https://flowforge.com/docs/user/envvar/).
-
-Furthermore, [stacks](https://flowforge.com/docs/user/changestack). These allow
-a user to select the execution environment for their Node-RED project. For example; the
-Node-RED version being used. Combined with the ability for one to copy a project
-to a new stack, this allows FlowFuse users to copy their project to the Node-RED
-3.0-beta stack to validate their solutions will continue to work on the new release
-without disrupting their main project.
-
-## Our roadmap
-
-Currently we're working towards our 0.6 release. The main feature of this release
-will be support for Devices. This will allow you to send a snapshot of a project
-to a Node-RED instance running outside of the FlowFuse platform and update the flows
-remotely. Remote devices will run our [agent](https://github.com/FlowFuse/device-agent)
-to communicate with the FlowFuse Cloud project.
-
-While the first iteration will be considered an Alpha release, by shipping early and often, it lets us get
-welcome feedback from our users and the wider community - helping to shape the future direction.
-It also allows users to start validating the feature for their own proof of concept projects.
-
-Over the next few months we're continuing to drive development of the platform
-across a number of areas - including further improvements to the Device feature.
-But also looking at new Enterprise-ready features, such as Single-Sign On integration
-and more tools to make collaboration even easy.
-
-We intend to grow our offering so that FlowFuse remains the best way to run
-Node-RED.
-
-Stay informed by registering for our newsletter!
diff --git a/nuxt/content/blog/2022/07/new-projecttype.md b/nuxt/content/blog/2022/07/new-projecttype.md
deleted file mode 100644
index 605872ccde..0000000000
--- a/nuxt/content/blog/2022/07/new-projecttype.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Introducing Medium Projects on FlowFuse Cloud
-subtitle: A bigger project with more resources
-description: "Introducing Medium Projects on FlowFuse Cloud, a bigger project tier offering more resources for growing engineering teams."
-date: 2022-07-22 12:00:00.0
-authors: ["sam-machin"]
-tags:
- - posts
- - flowfuse
- - news
----
-We've added a second size of project to FlowFuse Cloud. A bigger project type with more resources available to it.
-
-
-Our [0.7 release](https://flowforge.com/blog/2022/07/flowforge-07-released/) introduced the concept of Project Types. This allows platforms to provide different sizes of projects, varying the memory/cpu or features available within a given type.
-
-Today we've put this feature to work on FlowFuse Cloud by introducing the new **Medium Project** type.
-
-
-Medium projects have 3 times the resources of the existing Small type, allowing for more complex flows and larger message objects. This will be useful to business users looking to process complex sets of data.
-
-Our Medium project is priced at $50 a month and we'll be adding new features to this project type in the coming months to further enhance the value of this new tier.
-
-We don't currently support directly upgrading a project between types, but that is in the [plan for the future](https://github.com/FlowFuse/flowfuse/issues/595). In the meantime, you can use the 'Export Project' feature on a project's settings tab to copy it over into a new Medium type project.
-
-
-
-
diff --git a/nuxt/content/blog/2022/08/community-news-06.md b/nuxt/content/blog/2022/08/community-news-06.md
index fbc488738f..2eff47b91a 100644
--- a/nuxt/content/blog/2022/08/community-news-06.md
+++ b/nuxt/content/blog/2022/08/community-news-06.md
@@ -23,9 +23,6 @@ We've updated the format of our release posts as well to detail all the user fac
[Raspberry Pi Pico with Node-RED](https://www.tomshardware.com/how-to/raspberry-pi-pico-w-node-red)
[Les Pounder](https://twitter.com/biglesp) Has published a great tutorial on communicating with the new [Raspberry Pi Pico W](https://www.raspberrypi.com/products/raspberry-pi-pico/) and Node-RED. He shows you how to capture data from an environmental sensor then display this on a dashboard.
-[Medium Projects](/blog/2022/07/new-projecttype/)
-We've added a second size of project to FlowFuse Cloud. A bigger project type with more resources available to it.
-
[Using Node-RED to control IoT Devices on Golioth](https://blog.golioth.io/how-to-use-node-red-to-control-iot-devices-on-golioth/)
Our friends at [Golioth](https://golioth.io/) have published an article on how to use Node-RED to control and process data from IoT Devices connected to their platform.
diff --git a/nuxt/content/blog/2023/03/ibmcloud-starter-removed.md b/nuxt/content/blog/2023/03/ibmcloud-starter-removed.md
deleted file mode 100644
index 2780bfeaf3..0000000000
--- a/nuxt/content/blog/2023/03/ibmcloud-starter-removed.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-title: IBM Cloud removes Node-RED starter application
-subtitle: Get up and running with a Starter Application for Node-RED with FlowFuse or migrate your existing flows from IBM Cloud
-description: "IBM Cloud is removing its Node-RED starter application from its Cloud App Service Starter Kits. FlowFuse has you covered."
-date: 2023-03-29 12:00:00
-authors: ["joe-pavitt"]
-image: /images/blog/tile-ibm-cloud-starter-removed--text.png
-tags:
- - posts
- - node-red
- - news
----
-
-IBM Cloud has [recently announced](https://www.ibm.com/cloud/blog/announcements/deprecation-of-ibm-cloud-starter-kits) that they will no longer be providing their Cloud App Service Starter Kits, including the [Node-RED Starter Application](https://developer.ibm.com/tutorials/how-to-create-a-node-red-starter-application/).
-
-
-
-## Node-RED Starter Application
-
-If you're looking for an alternative place to get started with Node-RED then FlowFuse, founded by Node-RED co-creator Nick O'Leary, are here to help you with Cloud-hosted Node-RED as well as infrastructure and tooling to scale your Node-RED instances in production.
-
-As an ex-IBM Employee myself, over the years, I've been very dependant upon the Node-RED Starter Application in IBM Cloud. I'd used it dozens of times with clients to showcase the value of Node-RED and how easy it is to spin up integrations between hardware devices, APIs and online services.
-
-If you're now looking for somewhere to rely on in order to easily spin up new instance of Node-RED, then FlowFuse is the obvious answer. If you're completely new for Node-RED too, we can also help you there with our [Getting Started](/blog/2023/01/getting-started-with-node-red/) guide.
-
-You can sign up for a [free FlowFuse Cloud Account](https://app.flowfuse.com/account/create) where you'll be given one small Node-RED instance for free, for your first month.
-
-## Integrations
-
-If you've seen the excellent ["Create a Node-RED starter application"](https://developer.ibm.com/tutorials/how-to-create-a-node-red-starter-application/) article on IBM Developer, you'll probably be looking to connect up to a Cloudant Instance, or other IBM Cloud Services. Don't worry. All of that is still available through Node-RED on FlowFuse.
-
-You can install the relevant nodes in one of two places:
-
-1. **Node-RED Palette Manager:** Click "Menu > Manage Palette > Install". The menu is available via the icon in the top-right of your running Node-RED Instance)
-
-
-
-
-2. **FlowFuse Instance Settings:** For a given Instance in FlowFuse, click "Settings > Palette". You can then define the npm module name and versions explicitely in the "Installed Modules" section
-
-
-
-It's also easy to setup [Environment Variables](/blog/2023/01/environment-variables-in-node-red/) for Node-RED in FlowFuse for when you integrate with external services like APIs too.
-
-## Security
-
-As with IBM Cloud, FlowFuse makes it very easy to secure your Node-RED Applications. [FlowFuse offers three tiers of security](/docs/user/instance-settings/#security) options on your Node-RED Instances to secure any exposed HTTP routes on your Node-RED instance, e.g. REST API endpoints or Node-RED Dashboard.
-
-- **None**: Anyone will be able to access the exposed routes.
-- **Basic Auth**: Setup a single, dedicated username and password combination that is required in order to access the routes.
-- **FlowFuse Credentials**: Visitors can use their FlowFuse username/password in order to access the endpoints. This also includes SSO if you have that configured for your FlowFoerge Team.
-
-## Migrating Existing Instances
-
-If you're looking to move your Node-RED applications from IBM Cloud, then you can do so through one of two options:
-
-### Node-RED Tools Plugin
-
-You can use our Node-RED Tools plugin to migrate your flows and credentials over to FlowFuse. You can read the details in our [Migration Guide](/docs/migration/introduction/), which also includes instructions on how to export your environment variables too.
-
-
-### Manual Import
-
-This will only enable you to import your Flows, not the associated credentials.
-
-1. Export your existing `flows.json` from your IBM Cloud-hosted Node-RED instance by choosing "Export > All Flows > Download" within Node-RED
-2. Create a new Application on FlowFuse
-3. Once created, click the Node-RED instance that has been generated within your Application
-4. Click "Settings"
-5. Scroll down and select the "Import Instance" option
-6. Choose your `flows.json` file that you downloaded earlier.
-
-_If you have any questions about the above, or more generally about Node-RED or FlowFuse, then please do reach out and [get in touch](/contact-us)._
\ No newline at end of file
diff --git a/nuxt/content/blog/2023/04/community-news-04.md b/nuxt/content/blog/2023/04/community-news-04.md
index 58174082e7..0da9e672ab 100644
--- a/nuxt/content/blog/2023/04/community-news-04.md
+++ b/nuxt/content/blog/2023/04/community-news-04.md
@@ -27,8 +27,6 @@ Join Steve McLaughlin from FlowFuse as he showcases how easy it is to use Node-R
## From our Blog
[Comparing Node-RED Dashboards Solutions](/blog/2023/03/comparing-node-red-dashboards/) - A popular article comparing Node-RED Dashboard, uibuilder and FlexDash.
-[IBM Cloud removes Node-RED starter application](/blog/2023/03/ibmcloud-starter-removed/) - IBM has discontinued their Node-RED Starter Application, discover how to migrate to FlowFuse.
-
[The benefits and drawbacks of using Node-RED function nodes](/blog/2023/03/why-should-you-use-node-red-function-nodes/) - Node-RED function nodes provide a great deal of flexibility in Node-RED. Discover the benefits and drawbacks of using them.
[FlowFuse 15. Now Available](/blog/2023/03/flowforge-1-5-0-released/) - FlowFuse 1.5 included updates to the UI and architecture to allow for future features.
diff --git a/nuxt/content/blog/2023/08/flowfuse-1-11-release.md b/nuxt/content/blog/2023/08/flowfuse-1-11-release.md
deleted file mode 100644
index 26b6c4d21a..0000000000
--- a/nuxt/content/blog/2023/08/flowfuse-1-11-release.md
+++ /dev/null
@@ -1,83 +0,0 @@
----
-metaTitle: "FlowFuse 1.11: Easier Node-RED Setup"
-title: FlowFuse 1.11 makes it easier to get started with FlowFuse and Node-RED
-subtitle: Our latest release includes a new starter tier for FlowFuse Cloud, Personal Access Tokens for API access and improvements to device management.
-description: The new FlowFuse 1.11 release includes a new starter tier for FlowFuse Cloud, Personal Access Tokens for API access and improvements to device management.
-date: 2023-08-31
-lastUpdated: 2026-08-13
-authors: ["ian-skerrett"]
-image: /blog/2023/08/images/release-1-11-graphic.png
-tags:
- - posts
- - flowfuse
- - releases
----
-
-FlowFuse 1.11 introduces a new starter tier for FlowFuse Cloud that makes it easier to get started with FlowFuse and Node-RED.
-
-
-
-::product-update-note
-::
-
-## New FlowFuse Cloud Starter Tier [#2328](https://github.com/FlowFuse/flowfuse/issues/2328)
-
-It is now easier for Node-RED developers to get started with FlowFuse and Node-RED. The new starter tier allows developers to use two Node-RED instances and two remote device deployments. Ideal for creating proof of concepts or running a home automation system with Node-RED.
-
-FlowFuse provides a cloud hosted version of Node-RED so developers don't need to worry about Node-RED installation or operation. This makes it a lot easier to get started with Node-RED and easier to maintain a running instance.
-
-
-## FlowFuse API access now possible via personal access tokens [#14](https://github.com/FlowFuse/flowfuse/issues/14)
-FlowFuse APIs are now accessible via personal access tokens (PAT). This makes it possible to create automation scripts that interact with the FlowFuse platform using the API and authenticate the scripts with the PAT.
-
-## Usability Improvements to Device Management [#2294](https://github.com/FlowFuse/flowfuse/issues/2334)
-
-A number of usability improvements have been added to the FlowFuse device management solution to make it more flexible and intuitive to use. These improvements include being able to associate devices at the application level allowing for easier editing of Node-RED instances on edge devices.
-
-## FlowFuse Rebranding [#119](https://github.com/orgs/FlowFuse/projects/1?pane=issue&itemId=34719640)
-
-Earlier in August, [FlowForge announced](/blog/2023/08/flowforge-is-now-flowfuse/) a change to our company and product name to FlowFuse. Work has begun to change the product branding to FlowFuse. The UI has been rebranded and the remaining points will be changed in the next release.
-
-## Other New Features
-
-- Add ability to add a description to an application and display it in the portal [#2279](https://github.com/FlowFuse/flowfuse/issues/2279)
-- UI Improvements to device management [#2427](https://github.com/FlowFuse/flowfuse/issues/2427)
-- Improve landing page for documentation [#842](https://github.com/FlowFuse/website/issues/842)
-- Restructure of user interface navigation [#2474](https://github.com/FlowFuse/flowfuse/issues/2474)
-
-
-## Bug Fixes
-
-- Device running old snapshot [#132](https://github.com/FlowFuse/device-agent/issues/132)
-
-
-
-
-## What's next?
-
-We're always working to enhance your experience with FlowFuse. Here's how you can stay informed and contribute:
-
-- **Roadmap Overview**: Check out our [Product Roadmap Page](/changelog/) to see what we're planning for future updates.
-- **Entire Roadmap**: Visit our [Roadmap on GitHub](https://github.com/orgs/FlowFuse/projects/5) to follow our progress and contribute your ideas.
-- **Feedback**: We're interested in your thoughts about FlowFuse. Your feedback is crucial to us, and we'd love to hear about your experiences with the new features and improvements. Please share your thoughts, suggestions, or report any [issues on GitHub](https://github.com/FlowFuse/flowfuse/issues/new/choose).
-
-Together, we can make FlowFuse better with each release!
-
-## Try it out
-
-We're confident you can have self managed FlowFuse running locally in under 30 minutes.
-You can install FlowFuse yourself via a variety of install options. You can find out more details [here](/docs/install/introduction/).
-
-If you'd rather use our hosted offering: [Get started for free](https://app.flowfuse.com/account/create) on FlowFuse Cloud.
-
-## Upgrading FlowFuse
-
-[FlowFuse Cloud](site:appURL) is already running 1.11.
-
-If you installed a previous version of FlowFuse and want to upgrade, our documentation provides a
-guide for [upgrading your FlowFuse instance](/docs/upgrade/).
-
-## Getting help
-
-Please check FlowFuse's [documentation](/docs/) as the answers to many questions are covered there. Additionally you can go to the [community forum](https://discourse.nodered.org/c/vendors/flowfuse/24) if you have
-any feedback or feature requests.
diff --git a/nuxt/content/blog/2023/08/open-source-is-a-tier-not-competition.md b/nuxt/content/blog/2023/08/open-source-is-a-tier-not-competition.md
deleted file mode 100644
index b16208a24e..0000000000
--- a/nuxt/content/blog/2023/08/open-source-is-a-tier-not-competition.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: "Our Open Source offering is a tier, not our competition"
-subtitle: Discover the perspective on open source as a valuable tier, not competition.
-description: "Gain insight into FlowFuse's approach to its open-source tier versus paid offerings, and why it's a tier, not competition."
-date: 2023-08-18
-authors: ["zeger-jan-van-de-weg"]
-image: "/blog/2023/08/images/matt-hardy-waves.jpg"
-tags:
- - posts
- - flowfuse
----
-
-More than once we’ve been in discussion with prospective customers on what tier
-is the right tier for their current Node-RED adoption. The question is likely to
-come up "Why wouldn't we just use the open source version of FlowFuse?". The
-implicit discussion created is one that is alike the question:
-“Why wouldn’t we go with your competition?”. For FlowFuse, and most other open-core
-companies like us, the open licensed and free to use core is tier, not competition.
-
-
-
-In the traditional sense, the prospective customer is right. By the definition,
-a customer **buys** goods or services by exchanging it for **money**. For
-FlowFuse’s open-source edition, which is free as in beer and free as in speech,
-no money changes hands. It can be installed and run by anyone. Once the software
-is being installed and used, we consider we've gained a new customer.
-There’s an agreement in place, the Apache 2.0 license, and value is obtained by
-the customer. The only missing component compared to an ‘ordinary’ sale is the lack
-of money from the customer to FlowFuse. The fact that no monetary value is exchanged,
-like the situation where a customer picks the competitor, doesn’t make the open
-source tier competition. It is just a free tier.
-
-Another reason it's really a tier is that the core of the product is the same. In
-many open-core products, the path to upgrade from the open source license product to
-the paid tier is much alike customers are used to on SaaS models. In the reals of
-self-managed software that's mostly uploading a license and at times a few configuration
-steps.
-
-Furthermore, the open tier is a tier as the customer choses to not adopt all
-capabilities. They're leaving value on the table. Either this is because it's not
-quite clear what the value is or if the higher tiers provides
-enough business value to warrant the expense. Or the adoption journey for the
-customer doesn't yet require the full featured tiers.
-
-What’s unique about open source software, is that customers can exchange value
-towards the company and community building the software in other forms: by
-opening issues, updating documentation, advocating for the OSS variant, among
-other ways. While this is not **money**, it is significant for a young company
-like FlowFuse.
-
-## Challenges with a open core free tier
-
-That's not to say that an open source tier is a silver bullet for a company. For
-one, it's hard to track how many users a software package has, and who these users
-are. For example; FlowFuse has [Telemetry](/docs/admin/telemetry/#usage-telemetry),
-though it can be turned off. Nor do we know who hosts this software.
-
-Another challenge is around product and feature packaging. At FlowFuse and other open core companies it's
-uncommon to move features from the open tier to paid tier only. If this choice has
-been made it's a done deal, even when the product team got it wrong. Usually the
-initial thoughts are therefor to move all features into the paid tiers. However,
-this hampers long term growth as adoption of paid features are adopted later or
-not at all. We follow the
-[Open-Core buyer based model](https://opencoreventures.com/blog/2023-01-open-core-standard-pricing-model)
-to segregate the value, about which I'll write a post next time.
-
-Photo by Matt Hardy.
diff --git a/nuxt/content/blog/2023/09/community-news-09.md b/nuxt/content/blog/2023/09/community-news-09.md
index 5a46127607..063a7f353d 100644
--- a/nuxt/content/blog/2023/09/community-news-09.md
+++ b/nuxt/content/blog/2023/09/community-news-09.md
@@ -47,7 +47,6 @@ Hard to believe that Node-RED was launched 10 years ago. We want to celebrate th
- [FlowFuse is now available on the AWS Marketplace](/blog/2023/08/aws-marketplace-announce/) - making it easier to run FlowFuse on the AWS cloud.
-- [Our Open Source offering is a tier, not our competition](/blog/2023/08/open-source-is-a-tier-not-competition/) - some insight from our CEO into our open source strategy.
- [Why the Automation Pyramid blocks digital transformation - The Role of Unified Namespace](/blog/2023/08/isa-95-automation-pyramid-to-unified-namespace/) - some insight from the FlowFuse product manager into the role of a Unified Namespace.
diff --git a/nuxt/content/blog/2024/02/professional-services-for-node-red.md b/nuxt/content/blog/2024/02/professional-services-for-node-red.md
deleted file mode 100644
index 2a61fdb6f8..0000000000
--- a/nuxt/content/blog/2024/02/professional-services-for-node-red.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-metaTitle: "Invest in Node-RED Professional Services?"
-title: Should You Invest in Professional Services for Your Node-RED Development?
-subtitle: Professional Services for Node-RED, When and Why?
-description: "Discover the benefits of investing in professional services for your Node-RED development, from initial setup to full scaling."
-date: 2024-02-05
-authors: ["grey-dziuba"]
-image: /blog/2024/01/images/professional-services-for-your-node-red.png
-tags:
- - posts
- - flowfuse
----
-
-Professional services come in many different forms. Anything from setup and configuration, flow development, to node development. In this article, we will cover a few examples of how you can leverage professional services for your Node-RED applications.
-
-
-
-## Should You Invest in Professional Services for Your Node-RED Development?
-
-Node-RED is multifaceted, and Professional Services (PS) can apply to many use cases. We will break it down into three categories that will help identify whether PS (Professional Services) is right for you. Those categories will be setup, flow development, and node development. Each takes a different skill set and has different levels of complexity.
-
-Before we jump into things, we need to understand the value proposition of Node-RED. Why Node-RED? Node-RED is a tool that makes [Citizen Development](/blog/2023/10/citizen-development/) a reality. It should be treated that way throughout the development journey regardless of Professional Services or not. Following standard procedures that minimize complexity, for example: reducing the use of function nodes when other nodes would be more ideal. Don’t overcomplicate things that don’t need to be or better said by this quote.
-
-> Easy things should be easy, and hard things should be possible.
--Larry Wall
-
-### Setup
-
-It is often recommended to use PS for the setup and installation of products,
-and Node-RED and FlowFuse aren't different. This becomes especially true if you
-desire to professionalize your Node-RED instance. The reason for this is that PS
-teams focus on minimizing the risk of application failure, security compromise,
-and data/ip loss. This is an area of PS that can easily be overlooked, mainly
-there aren't any negative consequences in the short term. The work these teams focus on prevents catastrophic issues in the future. With Node-RED and FlowFuse, these teams will focus on installing FlowFuse based on system requirements and prerequisites, migrating existing Node-RED instances, securing your environment, and integrating with your existing ecosystem of applications.
-
-### Flow development
-
-Oftentimes, many think of Flow development when they think of PS for Node-RED. There will be a process flow that needs to be accomplished, but it is leveraging standard nodes built within the Node-RED platform. Occasionally, there will be a need to install a custom node from the pallet manager, but the complexities in the development are adhering to a process and or visualization. There may be complex data translation, but for the most part, access to the command line of the Node-RED instance is unnecessary. Professional services may be used in situations like this where knowledge of specific systems that Node-RED is integrating into is complex. For example, a complex backend database for specific industry-wide used applications.
-
-### Node Development
-
-At the core of some integration projects lies a critical requirement: the need for specific integrations that align precisely with your application's demands. This is where Node-RED's open-source nature becomes its most significant asset. Node-RED allows for the development of custom nodes, catering to specialized protocols unique to your organization or to serve niche applications. Such node development isn't just another feature; it represents the foundational element of Node-RED, embodying the platform's core value proposition.
-
-Whether addressing the need for custom integration with internal systems or expanding functionality to include less common applications, node development stands as the pivotal mechanism for enabling these capabilities. This critical development can be undertaken in-house, leveraging your team's expertise, or through PS specialized in node development.
-
-#### Conflating Flow and Node Development
-
-It is important when scoping out a project to identify all of the potential nodes needed and identify any potential missing ones. The skills for developing Nodes and Flow development, while similar, are often different skill sets. Having these identified will help prevent scope creep and setting expectations on timelines.
-
-## Conclusion
-
-As we've explored throughout this article, Professional Services for Node-RED can significantly enhance the efficiency, security, and scalability of your automation and integration projects. From the initial setup and configuration to the intricacies of flow and node development, the expertise PS teams offer can be invaluable. The decision to engage with Professional Services should be informed by your project's specific needs, internal capabilities, and strategic priorities. Whether it's leveraging PS for the foundational setup of your Node-RED instance, outsourcing flow development to expedite project timelines, or seeking expert assistance for node development, the goal is the same: create a coding environment that is conducive to citizen development.
-
-If you are interested in professional services or consultation, [please reach out](/professional-services/).
diff --git a/nuxt/content/blog/2024/03/flowfuse-self-hosted-open-source-resource-limits.md b/nuxt/content/blog/2024/03/flowfuse-self-hosted-open-source-resource-limits.md
deleted file mode 100644
index be48c66685..0000000000
--- a/nuxt/content/blog/2024/03/flowfuse-self-hosted-open-source-resource-limits.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: FlowFuse Open Source Tier Resource Limits
-subtitle: The first 5 Node-RED runtimes are part of the open-source tier going forward
-description: "FlowFuse's Open Source tier resource limits: the first 5 Node-RED runtimes are now part of the open-source tier going forward."
-date: 2024-03-14
-authors: ["zeger-jan-van-de-weg"]
-image: /blog/2024/03/images/open-source-tier-resource-limits.png
-tags:
- - posts
- - flowfuse
----
-
-Today, with the latest FlowFuse release, an important change was made that
-updates the resource limits for our open-source, self-managed FlowFuse server
-tier. This change does not affect FlowFuse Cloud users in any way.
-
-
-
-::product-update-note
-::
-
-## New Open Source Tier Resource Limits
-
-The new limit for the number of Node-RED runtimes on the Open Source tier is 5.
-These 5 instances can be distributed across a maximum of 5 teams. This revised
-structure allows for the development of your initial FlowFuse and Node-RED
-solutions, providing a clear understanding of how FlowFuse can enhance your
-organization's workflows. Upgrading to a Team or Enterprise tier license unlocks
-the full potential of FlowFuse and grants access to our dedicated support team.
-
-## Why the Change?
-
-Here at FlowFuse, we're committed to providing a great experience for all our
-users, including those utilizing our free, open-source tier. We
-initially designed this tier to offer a platform for small organizations and
-larger teams to explore FlowFuse's capabilities without needing our direct
-involvement. However, we've observed instances where the Open Source tier's free
-limits were being used to run very large deployments and even entire sites.
-
-While support is a key benefit we offer to paying customers, we believe everyone
-deserves a positive FlowFuse experience. As such, we're adjusting the resource
-limits to better align with the Open Source tier's intended purpose and allow the
-company to continue to invest in the Open Source tier.
-
-## Transitioning Users
-
-If you're currently impacted by these resource limit changes, we want to ensure
-a smooth transition. We're offering a complimentary 1-year Enterprise license to
-affected users. To claim your license, simply email support@flowfuse.com with
-the IP address your server has used to send telemetry data (if available) and a
-screenshot of your admin panel so we can match the currently usage with the new
-license.
-
-We appreciate your understanding and continued support. If you have any
-questions regarding this update, please don't hesitate to reach out to our team
-at support@flowfuse.com.
diff --git a/nuxt/content/blog/2024/05/product-strategy-updates.md b/nuxt/content/blog/2024/05/product-strategy-updates.md
deleted file mode 100644
index f4fc59ca78..0000000000
--- a/nuxt/content/blog/2024/05/product-strategy-updates.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: Product Mission Statement and Strategy Updates
-subtitle: We've recently refined our product strategy to better align with our mission and vision. Here's a summary of the changes.
-description: We've recently refined our product strategy to better align with our mission and vision. Here's a summary of the changes.
-date: 2024-05-14
-authors: ["joe-pavitt"]
-image: /blog/2024/05/images/product-strategy-updates.png
-tags:
- - posts
- - flowfuse
----
-
-It's now been two years since our first ever `0.1.0` release of FlowFuse. In that time, we've been working hard to build out a platform to help users elevate their Node-RED experience. In that time we've delivered some incredibly valuable features to FlowFuse users such as centralized instance management, remote deployments and version control. We've also learned a lot about our users, their needs, and how we can best serve them, and in a recent reflection on our product strategy decided to refine our product mission statement.
-
-
-
-## Product Mission Statement
-
-FlowFuse is used across a range of industries and use-cases, and in the hundreds of conversations we've had with customers, we've found that in every scenario there is a common pattern. So, to reflect ths, we've created a new Product Mission Statement, to make it clear to existing and prospective users of FlowFuse what it is that we're striving for.
-
-Our new mission statement is as follows:
-
-> **Provide the best way to build, manage and deploy Node-RED applications at scale, in reliable and secure production environments.**
-
-We believe that by focusing on this mission, we can better serve our users and provide them with the tools they need to succeed. This mission statement will act as the north star for our product prioritization moving forward, and be our compass to ensure we're staying on track in delivering value to our users.
-
-### Build
-
-FlowFuse strives to be the best place to build Node-RED applications by providing tools to help users build applications with more confidence.
-
-- **Simplified Hosting:** Whether you want cloud-hosted instances, or to run Node-RED on edge devices, FlowFuse provides the smoothest experience to setup new Node-RED instances.
-- **Trust**: [Certified Nodes](/blog/2023/10/certified-nodes/) ensure Node-RED developers can trust the reliability, quality and security of third-party nodes they're using in their applications.
-- **Version Control**: [Snapshots](/docs/user/snapshots/) capture point-in-time views of Node-RED flows, environment variables and other configuration settings. We even capture automatic snapshots of your flows every time you deploy, so you can always be confident you have a backup.
-- **Collaborative Development**: We are building FlowFuse to be a platform that enables teams to work seamlessly together on Node-RED applications. From the [Team Library](/docs/user/shared-library/), through to [Node-RED Multiplayer](/blog/2024/04/node-red-multiplayer/), we want to make sure that FlowFuse is the best platform for collaborative development in Node-RED.
-- **Remote Access:** FlowFuse provides a secure way to access your Node-RED instances and devices from anywhere in the world, so you can build and debug your applications with ease.
-
-### Manage
-
-With FlowFuse, it's possible to manage thousands of Node-RED instances, all in one place. We make sure you have a clear picture of what's happening across all of your instances, and provide tools to help you manage them effectively.
-
-- **Centralized Management**: FlowFuse provides a single entry point to manage all of your Node-RED instances, no matter where they are hosted.
-- **Security**: FlowFuse provides a range of security features to help you keep your Node-RED instances secure. From [Two-Factor Authentication](/docs/user/user-settings/#two-factor-authentication) to [Role-Based Access Control](/blog/2024/04/role-based-access-control-rbac-for-node-red-with-flowfuse/), we're building FlowFuse to be the most secure way to manage your Node-RED instances.
-- **Frictionless Maintenance:** Whether you're updating your Node-RED version, or one of the many third-party dependencies that your applications depend upon, FlowFuse provides tools to make it easy to keep your instances up-to-date and running smoothly.
-- **Observability:** FlowFuse provides tools to help you keep an eye on your Node-RED instances and make sure they're running smoothly. Get alerts when something goes wrong, and use the [Audit Logs](/docs/user/logs/#audit-log) to help you debug issues when they arise.
-
-### Deploy
-
-With FlowFuse, we aim to provide the best way to deploy Node-RED applications to production environments, whether that be to hundreds of remote devices, or via staging environments to ensure you can deploy with confidence.
-
-- **DevOps:** Test your applications in development and staging environments, ensuring you can deploy them with confidence to production.
-- **Remote Deployments:** Deploy your applications to hundreds of remote devices with a single-click, ensuring you can get your applications running in production quickly and easily.
-- **Reliability:** FlowFuse users can have trust that their applications will run without issues with features like [High Availability](/blog/2023/06/flowforge-1-8-released/). FlowFuse makes sure users have the tools to monitor and manage the reliability of their applications, including being alerted when things go wrong, and making the recovery as easy as possible.
-
-### What's Next?
-
-Our development team are busy working on a range of new features to help us deliver on our mission. If you're interested to see what highlight features we're working on for the next release (v2.5) in four weeks time, you can checkout our [Development Board](https://github.com/orgs/FlowFuse/projects/1/views/39) on GitHub.
-
-For longer term planning, we have our [Product Planning Board](https://github.com/orgs/FlowFuse/projects/3/views/9), which outlines the features we're working on for the next 12 months. It's subject to change, as we're always [iterating](/handbook/company/values/#iterative-improvement), but it gives a good idea of where our focus will likely be in the coming months.
-
-In the mean time, please do reach out if there are any features you'd like to see in FlowFuse, or if you have any feedback on our product strategy. We're always keen to hear from our users and learn how we can better serve you.
-
-### Read More
-
-If you're interested in learning more about our company and product strategies, you can read more detail in our Handbook:
-
-- [Company Strategy](/handbook/company/strategy)
-- [Product Mission Statement](/handbook/engineering/product/)
\ No newline at end of file
diff --git a/nuxt/content/blog/2024/06/node-red-4-on-flowfuse-cloud.md b/nuxt/content/blog/2024/06/node-red-4-on-flowfuse-cloud.md
index d1ad81b63b..6bf553d202 100644
--- a/nuxt/content/blog/2024/06/node-red-4-on-flowfuse-cloud.md
+++ b/nuxt/content/blog/2024/06/node-red-4-on-flowfuse-cloud.md
@@ -21,7 +21,7 @@ Node-RED 4.0 is the new major release of the project, which is at the heart of a
-As [we wrote recently](/blog/2024/05/product-strategy-updates/), our product mission statement is to provide the best way to build, manage and deploy Node-RED applications at scale, in reliable and secure production environments. This drives the work we do both within the FlowFuse platform and our contributions back into the Node-RED project.
+Our goal is to make FlowFuse the platform industrial teams use to build, deploy and govern Node-RED applications in reliable, secure production environments. That drives the work we do both within the FlowFuse platform and our contributions back into the Node-RED project.
The [Node-RED 4.0 release](https://nodered.org/blog/2024/06/20/version-4-0-released) includes some of our recent contributions to improve the Build part of that mission - more specifically around the Collaborative Development part.
diff --git a/nuxt/content/blog/2024/12/flowfuse-release-2-12.md b/nuxt/content/blog/2024/12/flowfuse-release-2-12.md
deleted file mode 100644
index bba9ca7796..0000000000
--- a/nuxt/content/blog/2024/12/flowfuse-release-2-12.md
+++ /dev/null
@@ -1,159 +0,0 @@
----
-title: FlowFuse Cloud now available for free!
-subtitle: With our new FlowFuse release, comes a new team tier, available on FlowFuse Cloud, to provide you an easy way to manage your many Node-RED instances.
-description: With our new FlowFuse release, comes a new team tier, available on FlowFuse Cloud, to provide you an easy way to manage your many Node-RED instances.
-lastUpdated: 2026-06-03
-date: 2024-12-19
-authors: ["greg-stoutenburg"]
-image: /blog/2024/12/images/tile-release-2-12.png
-tags:
- - flowfuse
- - news
- - releases
-keywords: flowfuse release, flowfuse free plan, node-red cloud, device agent, remote node-red, flowfuse 2.12, free tier, node-red management
-cta:
- type: sign-up
- title: "Get Started with FlowFuse for Free"
- description: "Manage your Node-RED instances in the cloud with FlowFuse. Start with a free trial and experience centralised control, snapshots, and remote access for your edge devices."
-meta:
- faq:
- - question: "What is included in the FlowFuse free plan?"
- answer: "The free plan included 2 remote Node-RED instances managed through the FlowFuse Device Agent, version control via Snapshots, and remote access using Developer Mode."
- - question: "What is the FlowFuse Device Agent?"
- answer: "The FlowFuse Device Agent is a package you install on any hardware (Raspberry Pi, laptop, industrial gateway) where you want Node-RED to run. It connects that device to FlowFuse Cloud for remote management."
- - question: "How do I install the FlowFuse Device Agent on Linux or macOS?"
- answer: "Run `sudo npm install -g @flowfuse/device-agent` in your terminal. On Windows, run `npm install -g @flowfuse/device-agent` in an elevated command prompt."
- - question: "What are FlowFuse Snapshots?"
- answer: "Snapshots are automatic backups of your Node-RED flows. Device Auto Snapshots means any changes to flows running on remote devices are saved automatically, giving you a version history you can restore from."
- - question: "What is a Remote Instance in FlowFuse?"
- answer: "A Remote Instance is a Node-RED instance that is managed by FlowFuse but runs on external hardware, such as an edge device in a factory or a home server, connected via the Device Agent."
- - question: "Is the FlowFuse free plan still available?"
- answer: "The free plan has been withdrawn. You can sign up for a 2-week free trial to experience all FlowFuse features, or start with the Starter plan at $20/month."
- - question: "Can I use FlowFuse for home automation?"
- answer: "Yes. FlowFuse is well suited for home automation scenarios where you want to manage multiple Node-RED instances from a single interface, with version control and remote access."
- - question: "What is Developer Mode in the FlowFuse Device Agent?"
- answer: "Developer Mode allows you to access your remote Node-RED editor directly through FlowFuse Cloud, so you can edit flows on edge devices without needing direct network access to the hardware."
-tldr: "FlowFuse 2.12 introduced a free team tier on FlowFuse Cloud, allowing users to manage two remote Node-RED instances via the Device Agent at no cost. The release also included Device Auto Snapshots for automatic flow backups. Note: the free plan has since been withdrawn, but a 2-week trial and a Starter plan are available."
----
-
-The new Free plan on FlowFuse Cloud will allow you to manage two remote instances using FlowFuse Device Agent, completely free of charge, forever! The new plan also provides Device Auto Snapshots, so any changes to your Node-RED flows running on your devices are backed up automatically.
-
-
-
-::product-update-note
-::
-
-FlowFuse is an industrial data platform that enables engineers to build, manage, scale, and secure their Node-RED solutions for digitalizing processes and operations. More fundamentally though, it's a great platform to manage multiple instances of Node-RED.
-
-
-
After careful consideration, we've decided to withdraw the free plan. You can still sign up for a 30-day trial to experience all that FlowFuse has to offer.
-
-
-## What's Included?
-
-Whether you're running multiple Node-RED instances at home for Home Automation, or running thousands of Node-RED instances in your factory, FlowFuse provides an easy-to-use, centralised view of your Node-RED instances, making it easy to manage and monitor them in one place.
-
-In our new free tier on FlowFuse Cloud you get:
-
-- 2 x Remote Node-RED Instances, managed through the FlowFuse [Device Agent](/docs/device-agent/quickstart)
-- Version control for your Node-RED flows with FlowFuse's [Snapshots](/docs/user/snapshots/#introduction)
-- Remote access to your Node-RED instances through FlowFuse Cloud, utilizing the Device Agent's [Developer Mode](/docs/device-agent/quickstart/#developer-mode)
-
-## Getting Started
-
-::cta-image{src="/images/cta/book-a-demo.png" alt="Walk through your FlowFuse setup with our team - book a demo" cta="demo"}
-::
-
-### Create Your Free Team
-
-To create a free team, simply [sign up to FlowFuse Cloud](https://app.flowfuse.com/create).
-
-Once you've filled in your details, you'll be presented with the option to choose your team type. Select the "Free" option, and you're good to go.
-
-{data-zoomable}
-_Screenshot showing the UI for selecting your Team's type, when onboarding through on FlowFuse Cloud._
-
-
-
-### Remote Instances
-
-When you create a Free team, an Application is created for you automatically. Applications in FlowFuse help you organise and group your resources, from Instances to DevOps Pipelines and Snapshots for Version Control. Within your new application, you can "register" your first Remote Instance.
-
-A "Remote Instance" in FlowFuse is a just a term for an instance Node-RED, managed by FlowFuse, but running somewhere different from FlowFuse, e.g. on Edge hardware in a factory or your home. FlowFuse connects to these Remote Instances using the FlowFuse Device Agent, which is easy to setup and get running.
-
-To get started with your Remote Instance, you need to complete two steps:
-
-1. **Install Device Agent**: The FlowFuse Device Agent is installed onto the hardware where you want your Node-RED Instance to run.
-2. **Add Your Remote Instance**: In the FlowFuse UI, add a new "Remote Instance", and connect to your hardware.
-
-### Install Device Agent
-
-Firstly, wherever you want your Node-RED to run, e.g. on a Raspberry Pi or your own Laptop, install the `flowfuse-device-agent` package:
-
-#### Linux/MacOS
-
-```bash
-sudo npm install -g @flowfuse/device-agent
-```
-
-#### Windows
-
-Issue the below command in an elevated command prompt:
-
-```bash
-npm install -g @flowfuse/device-agent
-```
-
-For alternative installation options and more details, please refer to our [documentation](/docs/device-agent/).
-
-### Connect Your Hardware to FlowFuse
-
-To connect your Device Agent, in the FlowFuse Platform, click on the "Remote Instances" option in the left-hand menu, and then click the "Add Remote Instance" button.
-
-Fill out the name, device type and select the application you've just created, and you'll be presented with the following:
-
-{data-zoomable}
-_Screenshot showing the dialog with the one-time-code to connect your remote Node_RED instance to FlowFuse_
-
-The command presented is used to connect your device to FlowFuse. Run this where you just installed the `@flowfuse/device-agent` package. This will connect your remote Node-RED instance to the FlowFuse platform.
-
-The final step to take is to then start running the device agent, which you can do by simply calling:
-
-```bash
-flowfuse-device-agent
-```
-
-### Developing on your Remote Instance
-
-FlowFuse offers remote development capabilities, allowing you to edit your Node-RED flows directly, and securely, from the FlowFuse Cloud platform. This is done through "Developer Mode".
-
-To get started with developing flows with your Remote Instance, simply select your newly created Instance in the FlowFuse UI, toggle on 'Developer Mode", and click "Open Editor"!
-
-### Version Control with Snapshots
-
-FlowFuse makes version control easy with [Snapshots](/docs/user/snapshots/#introduction). The new Free plan includes Device Auto Snapshots, which will automatically create a snapshot any time a flow is deployed to your device.
-
-## What Else is New?
-
-In addition to the Free plan, we've also added two new views to the FlowFuse platform:
-
-- **Pipelines**: This view provides a way to manage all of your DevOps Pipelines, making it even easier to manage your development, testing, staging and production environments.
-- **Bill of Materials**: This view provides a way to manage all of your Node-RED dependencies, making it easy to see what versions of nodes are being used across all of your Node-RED instances.
-
-For a full list of everything that went into our 2.12 release, you can check out the [release notes](https://github.com/FlowFuse/flowfuse/releases/tag/v2.12.0).
-
-We're always working to enhance your experience with FlowFuse. We're always interested in your thoughts about FlowFuse too. Your feedback is crucial to us, and we'd love to hear about your experiences with the new features and improvements. Please share your thoughts, suggestions, or report any [issues on GitHub](https://github.com/FlowFuse/flowfuse/issues/new/choose).
-
-Together, we can make FlowFuse better with each release!
-
-## Try FlowFuse
-
-### Self-Hosted
-
-We're confident you can have self managed FlowFuse running locally in under 30 minutes. You can install FlowFuse using [Docker](/docs/install/docker/) or [Kubernetes](/docs/install/kubernetes/).
-
-### FlowFuse Cloud
-
-The quickest and easiest way to get started with FlowFuse is on our own hosted instance, FlowFuse Cloud.
-
-[Get started for free](https://app.flowfuse.com/account/create) now, and you'll have your own Node-RED instances running in the Cloud within minutes.
diff --git a/nuxt/content/blog/2025/08/flowfuse-why-pricing-matters.md b/nuxt/content/blog/2025/08/flowfuse-why-pricing-matters.md
deleted file mode 100644
index a9b4d83596..0000000000
--- a/nuxt/content/blog/2025/08/flowfuse-why-pricing-matters.md
+++ /dev/null
@@ -1,94 +0,0 @@
----
-metaTitle: "Why Pricing Models Matter in Automation"
-title: "The Evolution of Business Automation: Why Pricing Models Matter"
-subtitle: The importance of a predictable pricing model in workflow automation
-description: "The importance of a predictable pricing model in workflow automation, and how it shapes how teams choose their automation tools."
-date: 2025-08-08
-authors: ["pablo-filomeno"]
-keywords: node-red, n8n, pricing, business automation
-image: /blog/2025/08/images/the-evolution-of-business-automation-why-pricing-models-matter.png
-tags:
- - flowfuse
----
-The automation landscape is evolving rapidly, and recent industry developments have sparked important conversations about how businesses should evaluate their automation platforms. N8N’s recent shift from workflow-based to execution-based pricing, positioned as removing limits, has received mixed reactions from the community, with many growing businesses finding the reality more complex. As pricing models change across the industry, now is the perfect time to reflect on what truly matters when choosing the right automation solution for your needs.
-
-
-
-
-## The Current State of Automation Pricing
-
-Many automation platforms are rethinking their pricing structures, moving from workflow-based models to execution-based billing. While this approach aims to provide more flexibility, it can create new challenges for businesses trying to predict costs and plan their automation strategies.
-
-Execution-based pricing means each step or run of your workflow consumes credits or counts toward your usage limits. What initially appears straightforward can become complex when scaling automation across teams and departments.
-
-## What Business Users Really Need
-
-Based on conversations we're seeing in automation communities, business users are looking for:
-
-- **Cost predictability**: The ability to forecast automation expenses as operations grow
-- **Scalability confidence**: Knowing their platform can handle increased complexity without surprises
-- **Team collaboration**: Tools that support multiple users working together effectively
-- **Enterprise readiness**: Solutions built to handle business-critical operations from the start
-
-## FlowFuse: Built for Business Automation
-
-FlowFuse takes a different approach to business automation, focusing on what enterprises actually need rather than trying to retrofit consumer tools for business use.
-
-### Industrial-Grade Foundation
-
-FlowFuse is designed as an Industrial Application Platform that empowers teams to build, deploy and manage applications that optimize industrial operations. This isn't an add-on feature, it's fundamental to how we approach automation.
-
-### The Power of Node-RED
-
-At the heart of FlowFuse is Node-RED, the free and truly Open Source low-code programming tool of choice for industrial applications. With over 5,000 community-contributed nodes, Node-RED enables engineers to collect, transform, and integrate data through visualized dashboards. It's been proven in everything from home automation to massive industrial deployments.
-
-### Transparent Business Model
-
-Rather than complex execution counting, FlowFuse focuses on delivering reliable automation that scales with your business needs. Our approach eliminates the guesswork and lets you focus on building solutions rather than calculating usage; costs scale with how many Node-RED runtimes you need to manage.
-
-## Key Advantages of the FlowFuse Approach
-
-1. **Enterprise-First Design:**
-FlowFuse is built specifically for mission-critical business applications where reliability isn't optional.
-
-2. **True Team Collaboration:**
-FlowFuse enables organizations to reliably deliver Node-RED applications in a continuous, collaborative and secure manner, supporting team-based development from the ground up.
-
-3. **Flexible Deployment Options:**
-Whether you need cloud, on-premises, or hybrid deployment, FlowFuse adapts to your infrastructure requirements without artificial constraints.
-
-4. **Mature, Battle-Tested Ecosystem:**
-Built on Node-RED's proven foundation, FlowFuse leverages years of community development and real-world industrial deployment experience.
-
-## Evaluating Your Automation Strategy
-
-As the automation landscape evolves, consider these key factors when choosing or re-evaluating your platform:
-
-**Cost Transparency**: Can you clearly understand and predict your automation costs as you scale?
-
-**Business Focus**: Is your platform designed for enterprise requirements, or adapted from simpler use cases?
-
-**Team Support**: Does your solution enable effective collaboration across your organization?
-
-**Long-term Stability**: Is your chosen platform built to handle the complexity and scale of business operations?
-
-## The FlowFuse Advantage
-
-FlowFuse stands out because we've built our platform specifically for business automation challenges:
-
-- **Predictable, business-friendly pricing** that grows with your needs
-- **Industrial-grade reliability** for mission-critical applications
-- **Enterprise security and compliance** built in from day one
-- **Professional support** that understands business requirements
-
-## Ready to Experience the Difference?
-
-While other platforms adapt consumer tools for business use, FlowFuse was designed from the ground up for enterprise automation needs.
-
-A free trial is available for FlowFuse Cloud, and you can also run FlowFuse locally, docker-based, or in Kubernetes.
-
-Experience automation without the complexity of execution counting or artificial limitations. Discover how FlowFuse can support your business's growth with transparent, scalable solutions.
-
----
-
-*Ready to get started? [Explore FlowFuse today](/) and see why businesses choose purpose-built automation platforms.*
diff --git a/nuxt/content/changelog/2023/09/snapshots-devices.md b/nuxt/content/changelog/2023/09/snapshots-devices.md
index 138084f749..a6aa824708 100644
--- a/nuxt/content/changelog/2023/09/snapshots-devices.md
+++ b/nuxt/content/changelog/2023/09/snapshots-devices.md
@@ -7,7 +7,7 @@ authors: ["marian-demme"]
tags:
- changelog
---
-Four weeks ago, we began working on several [usability improvements to our Device Management](/blog/2023/08/flowfuse-1-11-release/#usability-improvements-to-device-management-%232294). This included the ability to associate devices at the application level, allowing for easier editing of Node-RED instances on edge devices.
+Four weeks ago, we began working on several usability improvements to our Device Management. This included the ability to associate devices at the application level, allowing for easier editing of Node-RED instances on edge devices.
Starting today, it will also be possible to create and manage snapshots for those standalone devices.
diff --git a/nuxt/content/changelog/2023/11/devices-in-pipelines.md b/nuxt/content/changelog/2023/11/devices-in-pipelines.md
index aaf3358e8c..9378922a34 100644
--- a/nuxt/content/changelog/2023/11/devices-in-pipelines.md
+++ b/nuxt/content/changelog/2023/11/devices-in-pipelines.md
@@ -12,7 +12,7 @@ tags:
::product-update-note
::
-Building on our [previous release](/blog/2023/08/flowfuse-1-11-release/#usability-improvements-to-device-management-%232294) that enabled the management of devices independently of instances. Now, the integration of individual devices into DevOps Pipelines is possible. This update marks a significant step towards more flexible and efficient device management within FlowFuse. In our ongoing efforts, we are also developing features to group devices, aiming to streamline and improve the overall device management experience.
+Building on our previous release that enabled the management of devices independently of instances. Now, the integration of individual devices into DevOps Pipelines is possible. This update marks a significant step towards more flexible and efficient device management within FlowFuse. In our ongoing efforts, we are also developing features to group devices, aiming to streamline and improve the overall device management experience.

diff --git a/nuxt/data/chrome.json b/nuxt/data/chrome.json
index 899c7b9bef..a5b8b70a5e 100644
--- a/nuxt/data/chrome.json
+++ b/nuxt/data/chrome.json
@@ -344,11 +344,6 @@
"label": "Partnerships",
"href": "/partners/",
"icon": "user-group"
- },
- {
- "label": "Professional Services",
- "href": "/professional-services/",
- "icon": "wrench-screwdriver"
}
]
},
@@ -670,10 +665,6 @@
},
{
"links": [
- {
- "label": "Professional Services",
- "href": "/professional-services/"
- },
{
"label": "Service Status",
"href": "https://status.flowfuse.com/"
diff --git a/nuxt/nuxt.config.ts b/nuxt/nuxt.config.ts
index 47cdc12ce4..a1c3a425b0 100644
--- a/nuxt/nuxt.config.ts
+++ b/nuxt/nuxt.config.ts
@@ -577,7 +577,6 @@ export default defineNuxtConfig({
'/contact-us',
'/book-demo',
'/support',
- '/professional-services',
'/dashboard/tags-and-canvas-feedback',
'/trial-feedback',
'/ebooks/beginner-guide-to-a-professional-nodered/',
diff --git a/nuxt/pages/professional-services/index.vue b/nuxt/pages/professional-services/index.vue
deleted file mode 100644
index e13f87136d..0000000000
--- a/nuxt/pages/professional-services/index.vue
+++ /dev/null
@@ -1,61 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-

-
-
-
-
- Engineering and Architecture Services
-
-
-
- FlowFuse employees are experts in Node-RED development. We can help your team create Node-RED flows that meet your requirements or conduct an architecture review of existing flows to align with Node-RED best practices.
-
-
-
-
-
-

-
-
-
-
- Education and Training
-
-
-
- FlowFuse offers Node-RED and FlowFuse in-person and online courses for engineers, architects, and managers. Our structured approach to training can be customized to fit your unique requirements.
-
-
-
-
-
-
-
-
-
-
diff --git a/nuxt/pages/teams/manufacturing-operations.vue b/nuxt/pages/teams/manufacturing-operations.vue
index 0c9e42eb14..0388cb9c36 100644
--- a/nuxt/pages/teams/manufacturing-operations.vue
+++ b/nuxt/pages/teams/manufacturing-operations.vue
@@ -80,8 +80,8 @@ const PAGE = {
intro: 'We become part of your team from the first conversation, and stay that way long after go-live.',
items: [
{ title: 'Built together, around your goals', descriptionLinks: [
- { text: 'Our team works alongside yours to build solutions around what you\'re accountable for, and stays close whenever a plant needs help. Learn about ' },
- { text: 'working with FlowFuse engineers', href: '/professional-services/' },
+ { text: 'Our team works alongside yours to build solutions around what you\'re accountable for, and stays close whenever a plant needs help. See ' },
+ { text: 'how we build with your team', destination: 'signUp' as const },
{ text: '.' },
], icon: 'i-lucide-handshake' },
{ title: 'No lock-in, ever', descriptionLinks: [
diff --git a/nuxt/pages/use-cases/uns.vue b/nuxt/pages/use-cases/uns.vue
index 7486144acd..66f90445ab 100644
--- a/nuxt/pages/use-cases/uns.vue
+++ b/nuxt/pages/use-cases/uns.vue
@@ -149,11 +149,13 @@ onMounted(startQuoteTimer)
onUnmounted(() => clearInterval(quoteTimer))
// "You're never alone" from /teams/manufacturing-operations/, with the copy pointed at a UNS.
-// Each description is split into parts so a part with an href renders as a link.
-const SUPPORT = [
+// Each description is split into parts so a part with an href renders as a link, and a
+// part with a destination renders as a tracked CtaLink to that CTA destination.
+type SupportPart = { text: string, href?: string, destination?: 'signUp' }
+const SUPPORT: Array<{ icon: string, title: string, parts: SupportPart[] }> = [
{ icon: 'i-lucide-handshake', title: 'Built with your team', parts: [
{ text: 'Our engineers work alongside yours to design the namespace and deliver the first plant, then stay close whenever a site needs help. See ' },
- { text: 'how we work with your team', href: '/professional-services/' },
+ { text: 'how we build with your team', destination: 'signUp' as const },
{ text: '.' },
] },
{ icon: 'i-lucide-lock-open', title: 'No lock-in, ever', parts: [
@@ -420,7 +422,7 @@ useSchemaOrg([
{{ item.title }}
- {{ part.text }}{{ part.text }}
+ {{ part.text }}{{ part.text }}{{ part.text }}
diff --git a/nuxt/public/blog/2022/07/images/project-type.png b/nuxt/public/blog/2022/07/images/project-type.png
deleted file mode 100644
index b4f491f3b9..0000000000
Binary files a/nuxt/public/blog/2022/07/images/project-type.png and /dev/null differ
diff --git a/nuxt/public/blog/2023/03/images/ff-installed-modules.png b/nuxt/public/blog/2023/03/images/ff-installed-modules.png
deleted file mode 100644
index 9170bad52e..0000000000
Binary files a/nuxt/public/blog/2023/03/images/ff-installed-modules.png and /dev/null differ
diff --git a/nuxt/public/blog/2023/03/images/nr-manage-palette-cloudant.png b/nuxt/public/blog/2023/03/images/nr-manage-palette-cloudant.png
deleted file mode 100644
index 3d50351500..0000000000
Binary files a/nuxt/public/blog/2023/03/images/nr-manage-palette-cloudant.png and /dev/null differ
diff --git a/nuxt/public/blog/2023/08/images/matt-hardy-waves.jpg b/nuxt/public/blog/2023/08/images/matt-hardy-waves.jpg
deleted file mode 100644
index 0fb7ce584c..0000000000
Binary files a/nuxt/public/blog/2023/08/images/matt-hardy-waves.jpg and /dev/null differ
diff --git a/nuxt/public/blog/2023/08/images/release-1-11-graphic.png b/nuxt/public/blog/2023/08/images/release-1-11-graphic.png
deleted file mode 100644
index e1abc593eb..0000000000
Binary files a/nuxt/public/blog/2023/08/images/release-1-11-graphic.png and /dev/null differ
diff --git a/nuxt/public/blog/2024/01/images/professional-services-for-your-node-red.png b/nuxt/public/blog/2024/01/images/professional-services-for-your-node-red.png
deleted file mode 100644
index 958f451515..0000000000
Binary files a/nuxt/public/blog/2024/01/images/professional-services-for-your-node-red.png and /dev/null differ
diff --git a/nuxt/public/blog/2024/03/images/open-source-tier-resource-limits.png b/nuxt/public/blog/2024/03/images/open-source-tier-resource-limits.png
deleted file mode 100644
index 2520f31078..0000000000
Binary files a/nuxt/public/blog/2024/03/images/open-source-tier-resource-limits.png and /dev/null differ
diff --git a/nuxt/public/blog/2024/05/images/product-strategy-updates.png b/nuxt/public/blog/2024/05/images/product-strategy-updates.png
deleted file mode 100644
index 5d6fccc99e..0000000000
Binary files a/nuxt/public/blog/2024/05/images/product-strategy-updates.png and /dev/null differ
diff --git a/nuxt/public/blog/2024/12/images/onboarding-device-registration.png b/nuxt/public/blog/2024/12/images/onboarding-device-registration.png
deleted file mode 100644
index 810ed70545..0000000000
Binary files a/nuxt/public/blog/2024/12/images/onboarding-device-registration.png and /dev/null differ
diff --git a/nuxt/public/blog/2024/12/images/onboarding-team-type.png b/nuxt/public/blog/2024/12/images/onboarding-team-type.png
deleted file mode 100644
index c1635f563e..0000000000
Binary files a/nuxt/public/blog/2024/12/images/onboarding-team-type.png and /dev/null differ
diff --git a/nuxt/public/blog/2024/12/images/tile-release-2-12.png b/nuxt/public/blog/2024/12/images/tile-release-2-12.png
deleted file mode 100644
index c7ff79f9c9..0000000000
Binary files a/nuxt/public/blog/2024/12/images/tile-release-2-12.png and /dev/null differ
diff --git a/nuxt/public/blog/2025/08/images/the-evolution-of-business-automation-why-pricing-models-matter.png b/nuxt/public/blog/2025/08/images/the-evolution-of-business-automation-why-pricing-models-matter.png
deleted file mode 100644
index e21ed88b93..0000000000
Binary files a/nuxt/public/blog/2025/08/images/the-evolution-of-business-automation-why-pricing-models-matter.png and /dev/null differ
diff --git a/nuxt/public/images/blog/tile-ibm-cloud-starter-removed--text.png b/nuxt/public/images/blog/tile-ibm-cloud-starter-removed--text.png
deleted file mode 100644
index 1d5ffb5b4e..0000000000
Binary files a/nuxt/public/images/blog/tile-ibm-cloud-starter-removed--text.png and /dev/null differ
diff --git a/nuxt/public/images/services/engineering-and-architecture-services.png b/nuxt/public/images/services/engineering-and-architecture-services.png
deleted file mode 100644
index 01b24e8c6f..0000000000
Binary files a/nuxt/public/images/services/engineering-and-architecture-services.png and /dev/null differ
diff --git a/nuxt/public/images/services/training.png b/nuxt/public/images/services/training.png
deleted file mode 100644
index 8c8506ea9d..0000000000
Binary files a/nuxt/public/images/services/training.png and /dev/null differ
diff --git a/nuxt/redirects.ts b/nuxt/redirects.ts
index 6ec0b17d59..dafa13c42f 100644
--- a/nuxt/redirects.ts
+++ b/nuxt/redirects.ts
@@ -44,7 +44,7 @@ export const redirects: Record = {
'/platform/features/': { redirect: { to: '/product/', statusCode: 301 } },
'/product/why-flowfuse/': { redirect: { to: '/product/', statusCode: 301 } },
'/features/': { redirect: { to: '/product/', statusCode: 301 } },
- '/blog/2024/03/flowfuse-self-hosted-starter-resource-limits/': { redirect: { to: '/blog/2024/03/flowfuse-self-hosted-open-source-resource-limits/', statusCode: 301 } },
+ '/blog/2024/03/flowfuse-self-hosted-starter-resource-limits/': { redirect: { to: '/pricing/', statusCode: 301 } },
'/unified-namespace/': { redirect: { to: '/use-cases/uns/', statusCode: 301 } },
'/solutions/manufacturing/': { redirect: { to: '/use-cases/it-ot-middleware/', statusCode: 301 } },
'/solutions/device-management/': { redirect: { to: '/use-cases/remote-device-management/', statusCode: 301 } },
@@ -129,7 +129,25 @@ export const redirects: Record = {
'/ingest': { redirect: { to: '/', statusCode: 301 } },
'/handbook/marketing/customer-stories': { redirect: { to: '/handbook/marketing/content-strategy/customer-stories/', statusCode: 301 } },
'/handbook/marketing/customer-stories/': { redirect: { to: '/handbook/marketing/content-strategy/customer-stories/', statusCode: 301 } },
- '/blog/2023/08/new-starter-tier/': { redirect: { to: '/blog/2023/08/flowfuse-1-11-release/', statusCode: 301 } },
+ '/blog/2023/08/new-starter-tier/': { redirect: { to: '/pricing/', statusCode: 301 } },
+
+ // Posts that taught FlowFuse as self-serve hosted Node-RED, the old free and paid
+ // tiers, or professional services. Retired with the move to selling deployments
+ // (Foundation Partnership). 302 as agreed with marketing.
+ '/blog/2022/02/announcing-flowforge-cloud/': { redirect: { to: '/build-with-us/', statusCode: 302 } },
+ '/blog/2022/04/flowforge-accepting-customers/': { redirect: { to: '/build-with-us/', statusCode: 302 } },
+ '/blog/2022/05/sign-up-for-flowforge-cloud/': { redirect: { to: '/build-with-us/', statusCode: 302 } },
+ '/blog/2022/07/new-projecttype/': { redirect: { to: '/pricing/', statusCode: 302 } },
+ '/blog/2023/03/ibmcloud-starter-removed/': { redirect: { to: '/build-with-us/', statusCode: 302 } },
+ '/blog/2023/08/flowfuse-1-11-release/': { redirect: { to: '/pricing/', statusCode: 302 } },
+ '/blog/2023/08/open-source-is-a-tier-not-competition/': { redirect: { to: '/pricing/', statusCode: 302 } },
+ '/blog/2024/02/professional-services-for-node-red/': { redirect: { to: '/build-with-us/', statusCode: 302 } },
+ '/professional-services/': { redirect: { to: '/build-with-us/', statusCode: 302 } },
+ '/blog/2024/03/flowfuse-self-hosted-open-source-resource-limits/': { redirect: { to: '/pricing/', statusCode: 302 } },
+ '/blog/2024/05/product-strategy-updates/': { redirect: { to: '/platform/why-flowfuse/', statusCode: 302 } },
+ '/blog/2024/12/flowfuse-release-2-12/': { redirect: { to: '/pricing/', statusCode: 302 } },
+ '/blog/2025/08/flowfuse-why-pricing-matters/': { redirect: { to: '/build-with-us/', statusCode: 302 } },
+
'/handbook/peopleops/job-descriptions/technical-product-manager': { redirect: { to: '/handbook/peopleops/job-descriptions/product-manager/', statusCode: 301 } },
'/handbook/peopleops/job-descriptions/technical-product-manager/': { redirect: { to: '/handbook/peopleops/job-descriptions/product-manager/', statusCode: 301 } },
'/node-red/fundamentals/': { redirect: { to: '/blog/2023/01/getting-started-with-node-red/', statusCode: 301 } },