Skip to content

Replace old tier names with Edge, Hub and Fleet - #6011

Merged
JoycePlaysFootball merged 10 commits into
mainfrom
old-tiering-cleanup
Nov 11, 2026
Merged

JoycePlaysFootball merged 10 commits into
mainfrom
old-tiering-cleanup

Conversation

@sumitshinde-84

@sumitshinde-84 sumitshinde-84 commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

Description

Several pages still referred to the Starter, Pro, Team, Enterprise and free tiers, which no longer exist. This brings the site in line with Edge, Hub and Fleet.

  • Tutorials and guides: availability notes now name the current products, based on feature-catalog.yml.
  • Release posts and changelog entries: left as published, with the existing product update note added on top.
  • Retired 8 posts that were only about old tiers or prices. Each redirects to /pricing/.
    • /blog/2025/08/annual_billing/
    • /blog/2026/03/enterprise-packaging-updates/
    • /changelog/2025/07/team-to-pro-plan-rename/
    • /changelog/2025/03/free-tier/
    • /changelog/2025/01/free-tier-onboarding/
    • /changelog/2024/02/device-pricing-change/
    • /changelog/2024/04/pricing-change/
    • /changelog/2023/09/introduction-enterprise-tier/
  • Handbook: the changelog writing guide now asks for Edge, Hub and Fleet in availability notes.

Product docs are updated in FlowFuse/flowfuse#9125.

Related Issue(s)

None

Checklist

  • I have read the contribution guidelines
  • I have considered the performance impact of these changes
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
  • For blog PRs, an Art Request has been created

Availability notes still pointed readers at the Starter, Pro, Team and
Enterprise tiers, which no longer exist on FlowFuse Cloud. Each note now
names the current products that include the feature, taken from
nuxt/content/feature-catalog.yml: FlowFuse Tables, MCP nodes, Project
Nodes, auto snapshots, the private node registry and FlowFuse Expert are
in every product, and the MQTT broker is in Edge and Fleet. Edge, Hub and
Fleet are called products, as the pricing page does.

Release posts and changelog entries are left as they were published.
Self-hosted "Enterprise license" wording is unchanged.
The post told readers to upgrade to the Premium or Enterprise tier, which
no longer exist. The listing is still live, so the post stays and now
names the current commercial products. Its feature list is refreshed from
nuxt/content/feature-catalog.yml, noting the product for features that
aren't in all three.
32013af set it to 2025-02-06 on 2026-02-06, eight months before the
post was published, so the page never showed it as updated. The content
change it records is from 2026-02-06.
Eight blog and changelog posts described the Starter, Pro and Team tiers,
the free tier, the old Enterprise package or their prices. Edge, Hub and
Fleet replaced all of them, so each post now 301s to /pricing/ instead of
showing visitors offers they can't buy.

The two links to the Enterprise tier announcement are removed, and the
images only these posts used are deleted. annual-billing.png stays, since
the 2.21 release post uses it too.
The guide's catalog section already asked for availability notes naming
the current products, but its post template and review checklist still
asked writers for the old tier and licence type, and a worked example
quoted an Enterprise tier note. The template and checklist now match the
catalog section, and the example keeps only the part it illustrates.
The tier rewording dropped it from the self-hosted half of these notes,
which then implied any self-hosted install gets FlowFuse Tables and
FlowFuse Expert. The product docs still require an Enterprise license.
The Arduino tutorial still offered the withdrawn free tier, and the
deployment guide tied remote terminal access to the Team and Enterprise
tiers. The feature catalog does not list remote terminal access, so the
tier note is removed rather than replaced.
Release posts and changelog entries keep their original availability
text as a record of what shipped. The existing ::product-update-note
component, already on 24 of them, now tops the 23 that named Starter,
Pro, Team or Enterprise without it, pointing readers to Edge, Hub and
Fleet.

improved-diagnostics.md uses CRLF line endings, which stop the
component from rendering, so its note lines use LF.
@netlify

netlify Bot commented Nov 6, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for flowfuse-website ready!

Name Link
🔨 Latest commit d2496c0
🔍 Latest deploy log https://app.netlify.com/projects/flowfuse-website/deploys/6af45e05d9c6f6a7b08a036c
😎 Deploy Preview https://deploy-preview-6011--flowfuse-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 42 (🟢 up 13 from production)
Accessibility: 95 (no change from production)
Best Practices: 92 (no change from production)
SEO: 92 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

Since 3.0, self-hosted licenses are issued per product (Hub, Edge,
Fleet), and every one of them, like an older Enterprise license, turns
on FlowFuse Tables and FlowFuse Expert. Naming only the Enterprise
license told new license holders they did not qualify.
@sumitshinde-84
sumitshinde-84 requested review from a team and JoycePlaysFootball and removed request for a team and JoycePlaysFootball November 6, 2026 11:16
@allthedoll

Copy link
Copy Markdown
Contributor

@sumitshinde-84 this PR did delete some historic blogs/changelogs that I don't think we want to touch.

@hardillb

Copy link
Copy Markdown
Contributor

I've just done a quick search for "Enterprise" across the website repo and there are a few blogs that still mention needing Enterprise level teams for certain features. (e.g. nuxt/content/blog/2024/building-uns-with-flowfuse.md has “Note: Enterprise-level teams can register up to 20 clients”).

I'm tempted to say these are generally fine and can probably be left, but rather than remove pages that talk about old tiers maybe just add a header that points to the current offerings and has a comment that the old ones are discontinued, this feels like it will be better SEO than just a straight redirect (might be wrong, I try to avoid the whole SEO world)

@sumitshinde-84

sumitshinde-84 commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor Author

Thanks both. Joyce and I discussed this last week.

The 8 posts deleted here are exclusively about old tiers and pricing: the free tier, the Team-to-Pro rename, device and instance pricing, annual billing, and the old Enterprise package. None of them contains any meaningful product or technical content beyond that.

An outdated page about pricing doesn't help anyone reading it today. These pages also receive almost no traffic (15 organic search clicks across all 8 in the last three months), so very few people would even see a note saying the plans have been discontinued. Keeping them live would mainly preserve outdated information.

We decided to retire them so AI tools and search engines consistently describe FlowFuse's current offering and don't confuse people about what we sell. Each page redirects to /pricing/.

@hardillb agreed that posts which only mention an old tier in passing, such as the UNS post, are fine to keep. That's what we've done here as well: we've updated a few, added notes where needed, and kept the posts. To update remaining mentions, I am working on new PR

@allthedoll, if there's any of these 8 posts you'd prefer to keep, let me know which ones and I'll restore them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants