Remove deprecated Starter and Team tiers from docs#7930
Conversation
dimitrieh
left a comment
dimitrieh
left a comment
There was a problem hiding this comment.
Self-review annotating each change for the Starter/Team tier removal (Product Repackaging Phase 2). Draft, held until launch. Note: feature-availability gates that named the deprecated tier now name Enterprise (the kept tier), which narrows the stated availability in the interim; it will be reconciled with the new packaging at launch. No Trial/Open-Source quota figures were fabricated. Docs source lives in this repo (docs/), synced into the website at build time.
| ## Billing Cycle | ||
|
|
||
| Starter plan teams are billed monthly on the anniversary of the team creation. You will receive one bill for each team. | ||
| Teams are billed monthly on the anniversary of the team creation. You will receive one bill for each team. |
There was a problem hiding this comment.
Billing Cycle / Removing / Suspended sections: dropped the deprecated plan names ('Starter plan teams', 'For Team plan teams') across the four sentences here and below. Billing mechanics are unchanged.
There was a problem hiding this comment.
| Teams are billed monthly on the anniversary of the team creation. You will receive one bill for each team. | |
| If you've signed up to FlowFuse Cloud without a yearly contract agreed upon with our sales team, your FlowFuse teams are billed monthly on the anniversary of the team creation. You will receive one bill for each team. |
| | Large | 3840MB | | ||
|
|
||
| Medium and Large instance types require the Teams or Enterprise tier. | ||
| Medium and Large instance types require the Enterprise tier. |
There was a problem hiding this comment.
'Medium and Large instance types require the Teams or Enterprise tier' changed to 'require the Enterprise tier'.
There was a problem hiding this comment.
@knolleary Can we deprecated sizes too? And just remove this choice for users? It's a challenge to constantly have this discussion live or for self-service customers.
| ### Creating Additional Instances | ||
|
|
||
| For utilizing various other FlowFuse features (e.g., DevOps Pipelines), it's highly beneficial to create a second Node-RED instance. A second Node-RED instance is included in both our Starter Tier and the Trial Phase of FlowFuse Cloud. | ||
| For utilizing various other FlowFuse features (e.g., DevOps Pipelines), it's highly beneficial to create a second Node-RED instance. A second Node-RED instance is included in the Trial Phase of FlowFuse Cloud. |
There was a problem hiding this comment.
'included in both our Starter Tier and the Trial Phase' changed to 'included in the Trial Phase'.
| # FlowFuse Persistent Context | ||
|
|
||
| Some Node-RED flows require the ability to persist context values between restarts and FlowFuse stack updates. By default, context data in Node-RED is ephemeral, meaning it does not survive restarts or stack updates. With FlowFuse Starter, Team and Enterprise tiers, however, you can enable **persistent context storage**, ensuring that your context values persist across restarts, upgrades, and more. | ||
| Some Node-RED flows require the ability to persist context values between restarts and FlowFuse stack updates. By default, context data in Node-RED is ephemeral, meaning it does not survive restarts or stack updates. With FlowFuse's paid plans, however, you can enable **persistent context storage**, ensuring that your context values persist across restarts, upgrades, and more. |
There was a problem hiding this comment.
'With FlowFuse Starter, Team and Enterprise tiers' changed to 'With FlowFuse's paid plans'.
| Project Nodes allow you to easily call those flows and get the result back. | ||
|
|
||
| The project nodes are only available in the Team and Enterprise tiers of FlowFuse. | ||
| The project nodes are only available in the Enterprise tier of FlowFuse. |
There was a problem hiding this comment.
'only available in the Team and Enterprise tiers' changed to 'only available in the Enterprise tier'.
| avoid excessive data usage when a device is in the field or on a cellular connection. | ||
|
|
||
| NOTE: This feature is only available to Team and Enterprise tier teams | ||
| NOTE: This feature is only available to Enterprise tier teams |
There was a problem hiding this comment.
'only available to Team and Enterprise tier teams' changed to 'only available to Enterprise tier teams'.
|
|
||
| - A Instance Stack with a launcher version of 2.8.0 or greater. | ||
| - Pro or Enterprise Team Type. | ||
| - Enterprise Team Type. |
There was a problem hiding this comment.
'Pro or Enterprise Team Type' changed to 'Enterprise Team Type'.
| ## Billing Cycle | ||
|
|
||
| Starter plan teams are billed monthly on the anniversary of the team creation. You will receive one bill for each team. | ||
| Teams are billed monthly on the anniversary of the team creation. You will receive one bill for each team. |
There was a problem hiding this comment.
| Teams are billed monthly on the anniversary of the team creation. You will receive one bill for each team. | |
| If you've signed up to FlowFuse Cloud without a yearly contract agreed upon with our sales team, your FlowFuse teams are billed monthly on the anniversary of the team creation. You will receive one bill for each team. |
| Teams are billed monthly on the anniversary of the team creation. You will receive one bill for each team. | ||
|
|
||
| For Team plan teams, Node-RED Instances and Devices are added as pro-rated charges on the current billing cycle and invoiced | ||
| Node-RED Instances and Devices are added as pro-rated charges on the current billing cycle and invoiced |
There was a problem hiding this comment.
| Node-RED Instances and Devices are added as pro-rated charges on the current billing cycle and invoiced | |
| Hosted and Remote Instances which are added beyond the included amount are pro-rated charges on the current billing cycle and invoiced |
| ## Removing Instances | ||
|
|
||
| For Team plan teams, when a Node-RED instance is deleted your account will receive pro-rated credit for the time remaining in the billing cycle. | ||
| When a Node-RED instance is deleted your account will receive pro-rated credit for the time remaining in the billing cycle. |
There was a problem hiding this comment.
| When a Node-RED instance is deleted your account will receive pro-rated credit for the time remaining in the billing cycle. | |
| When an instance is deleted your account will receive pro-rated credit for the time remaining in the billing cycle. |
| | Large | 3840MB | | ||
|
|
||
| Medium and Large instance types require the Teams or Enterprise tier. | ||
| Medium and Large instance types require the Enterprise tier. |
There was a problem hiding this comment.
@knolleary Can we deprecated sizes too? And just remove this choice for users? It's a challenge to constantly have this discussion live or for self-service customers.
| |--------|--------| | ||
| | Starter | 10MB | | ||
| | Team | 100MB | | ||
| | Enterprise | 1GB | |
There was a problem hiding this comment.
This is fine for now, but now it's a table with 1 line. Seems odd?
|
Opted to merge now instead of blocking the merge on minor notes, @dimitrieh would you be so kind to make a follow up PR though? |
2 participants
Summary
Removes the deprecated Starter and Team tiers from the platform docs (the source of flowfuse.com/docs), as part of the Product Repackaging effort (Phase 2). Enterprise is kept. No new packaging (Edge/Hub/Fleet) is introduced here.
docs/cloud/introduction.md: removed the Starter and Team Team-Type blocks; reworded the Team Types lead-in to Trial and Enterprise; trimmed the File Storage and Context Store quota tables to the Enterprise row; neutralized the MQTT broker lines; removed an orphaned Team-tier client-count clause and the Enterprise "Team Level plus" reference.docs/cloud/billing.md: dropped the deprecated plan names from the billing-cycle, removal and suspension sections (billing mechanics unchanged).docs/user/introduction.md,docs/user/persistent-context.md,docs/user/expert/chat.md: neutralized tier name-drops.Please do not merge yet: this should land with the Product Repackaging launch.
docs/user/projectnodes.md,snapshots.md,devops-pipelines.md,custom-npm-packages.md,static-asset-service.md,contribute/feature-flags.md: feature-availability gates that named the deprecated tier ("Team and Enterprise", "Pro or Enterprise") now name Enterprise only, the tier that is kept. This narrows the stated availability in the interim; it will be reconciled with the new packaging at launch.Interim framing of what remains is Open Source, Trial, and Enterprise. A Trial Team Type description and Trial/Open-Source quota figures are pending the new packaging; Enterprise values are kept and nothing was fabricated.