diff --git a/nuxt/content/blog/2026/11/changes-to-starter-pro-team-plans.md b/nuxt/content/blog/2026/11/changes-to-starter-pro-team-plans.md new file mode 100644 index 0000000000..0274bd6a26 --- /dev/null +++ b/nuxt/content/blog/2026/11/changes-to-starter-pro-team-plans.md @@ -0,0 +1,108 @@ +--- +title: "Changes to Starter, Pro, and Team Plans: Your Questions Answered" +subtitle: "What happens on January 1, 2027, what you need to do, and what happens to your data" +description: "FlowFuse is retiring the Starter, Pro, and Team plans. Contact support@flowfuse.com before December 31, 2026 to move to Hub, Edge, or Fleet, or your account will be paused. Your data will not be lost." +date: 2026-11-16 +authors: ["kristopher-sandoval"] +image: /blog/2026/11/images/changes-to-starter-pro-team-plans.png +tags: + - posts + - flowfuse + - news +tldr: "FlowFuse is retiring the Starter, Pro, and Team plans. If you're on one of them, email support@flowfuse.com before December 31, 2026 so we can move you to Hub, Edge, or Fleet. We will not charge you or switch your plan automatically. If we don't hear from you, we'll pause your account on January 1, 2027. Pausing does not delete your data." +--- + +A few weeks ago we wrote to Starter customers about restructuring our product lineup. Since then, we've made one important change: we will no longer migrate anyone automatically. Instead, we want to talk to each of you directly, so you end up on the product that fits how you use FlowFuse. + +That raises fair questions, especially about your flows and your data. Here are the answers. + + + +## What's changing? + +We're replacing the Starter, Pro, and Team plans with three products, each built for a specific kind of work: + +- **FlowFuse Hub** connects your business systems. +- **FlowFuse Edge** connects your data sources and powers your dashboards. +- **FlowFuse Fleet** runs and manages IoT deployments across many devices. + +Our existing plans weren't built around what production environments need. These three products are. + +## Who does this affect? + +Every customer on a Starter, Pro, or Team plan, on both FlowFuse Cloud and FlowFuse Self-Hosted. + +If you're seeing a banner in FlowFuse that links to this post, this applies to you. + +## What do I need to do? + +Email [support@flowfuse.com](mailto:support@flowfuse.com) before December 31, 2026. Tell us a little about how you use FlowFuse, and we'll help you pick between Hub, Edge, and Fleet and walk you through next steps. + +That's it. One email keeps your account running. + +## Will I be charged automatically? + +No. We won't move you to a new product or charge you for one unless you reach out and agree to it. + +Our earlier email said Starter customers would move to Hub automatically on January 1, 2027. That no longer applies. + +## Does anything change before December 31? + +No. Your current plan keeps working as it does today through December 31, 2026. + +## What happens if I don't contact you by December 31? + +We'll pause your account on January 1, 2027. + +## What does "paused" mean? + +When we pause your account: + +- **Hosted instances** stop running and can't be restarted. Anything that depends on them, such as dashboards, HTTP endpoints, and integrations with other systems, stops too. +- **Remote instances** keep running on your devices, but you can't manage them from FlowFuse. +- **Exporting your data** requires contacting [support@flowfuse.com](mailto:support@flowfuse.com). +- **Billing stops.** We won't charge you while your account is paused. + +If your flows feed production systems or anything people rely on day to day, please don't wait until the last week of December to get in touch. + +## Will I lose my data? + +Not immediately - but paused accounts will be removed January 1st, 2028. Until then, pausing your account does not delete your data. Your flows, configuration, and account data stay intact. If you need a copy of your data while your account is paused, contact [support@flowfuse.com](mailto:support@flowfuse.com). + +## I'm on FlowFuse Self-Hosted. Does this apply to me? + +Yes. Self-Hosted customers on Enterprise or Team licenses need to contact [support@flowfuse.com](mailto:support@flowfuse.com) before December 31, 2026 as well. + +Your flows and data live on your own infrastructure, so they stay with you. + +## Can I export my flows before December 31? + +Yes. Your account works normally until December 31, so you can export your flows from the Node-RED editor at any time. You don't need to do this to keep your data, but some teams like having their own copy. After your account is paused, exports go through [support@flowfuse.com](mailto:support@flowfuse.com). + +## My account was paused. Can I still get help? + +Yes. Email [support@flowfuse.com](mailto:support@flowfuse.com) and we'll talk through next steps with you. + +## How do I know which product is right for me? + +You don't have to figure it out alone. Most self-serve accounts have never spoken to our team, so we don't always know how you use FlowFuse. A short conversation is usually enough to find the right fit. + +As a starting point: + +- **Hub** if FlowFuse mainly connects business systems such as ERP, MES, databases, and APIs. +- **Edge** if FlowFuse mainly collects data from machines and sensors and shows it on dashboards. +- **Fleet** if you run FlowFuse on many devices across sites. + +## How much will the new products cost? + +Pricing depends on the product and how you use it. Our team will go through it with you when you reach out. + +## Why are you doing this? + +Our existing plans didn't meet what production environments require. Rather than keep stretching general-purpose tiers, we built three products around the three ways customers use FlowFuse most: connecting business systems, connecting data sources and dashboards, and managing device fleets. + +## Who do I contact with questions? + +Email [support@flowfuse.com](mailto:support@flowfuse.com). We'd rather hear from you early, even if you're still deciding. + +Thank you for building with FlowFuse. We look forward to working with you on what comes next. diff --git a/nuxt/public/blog/2026/11/images/changes-to-starter-pro-team-plans.png b/nuxt/public/blog/2026/11/images/changes-to-starter-pro-team-plans.png new file mode 100644 index 0000000000..c79785319f Binary files /dev/null and b/nuxt/public/blog/2026/11/images/changes-to-starter-pro-team-plans.png differ