Apply review follow-ups to Cloud billing and quota docs - #7946
Conversation
dimitrieh
left a comment
dimitrieh
left a comment
There was a problem hiding this comment.
Annotating each change against the review note it comes from, so the origin is traceable now that the source PR is closed. All four notes were left as review comments on #7930 and were never applied before that PR merged.
Still open and deliberately not touched here: the question of whether the Small/Medium/Large instance size choice should be deprecated for users entirely (#7930 (comment)). That has had no reply, so the gating sentence at docs/cloud/introduction.md line 112 is left as it is.
| ## Billing Cycle | ||
|
|
||
| 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. |
There was a problem hiding this comment.
Applies the suggestion at #7930 (comment) verbatim. Adds the carve-out for customers on a yearly contract agreed with sales, who are not billed monthly on the team anniversary.
| 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. | ||
|
|
||
| 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 |
There was a problem hiding this comment.
Applies the suggestion at #7930 (comment) verbatim. Moves to current product vocabulary (Hosted and Remote Instances rather than Node-RED Instances and Devices) and adds the qualifier that only instances beyond the included amount are pro-rated. The "at the end of the cycle." continuation on the next line is unchanged.
| ## Removing Instances | ||
|
|
||
| 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. |
There was a problem hiding this comment.
Applies the suggestion at #7930 (comment) verbatim. Terminology only, "a Node-RED instance" to "an instance".
| |--------|--------| | ||
| | Enterprise | 100GB | | ||
| A quota limit is applied to how much data can be stored, based on the Team type. | ||
| Enterprise teams have a file storage quota of 100GB per instance. |
There was a problem hiding this comment.
Addresses #7930 (comment) ("now it's a table with 1 line. Seems odd?"). That note was left on the Context Store table, but removing the deprecated tiers left this File Storage table in the same single-row shape, so both are converted to prose. The 100GB figure is unchanged.
| | Team Type | Context Store Quota (per instance) | | ||
| |--------|--------| | ||
| | Enterprise | 1GB | | ||
| Enterprise teams have a context store quota of 1GB per instance. |
There was a problem hiding this comment.
The table this replaces is the one the note at #7930 (comment) was left on. The 1GB figure is unchanged.
2 participants
Summary
Follow-up to #7930, which was merged without applying the review suggestions left on it.
docs/cloud/billing.md: applied the three review suggestions verbatim. The billing-cycle sentence now carves out teams on a yearly contract agreed with sales; the pro-rated charge sentence now names Hosted and Remote Instances and the included amount; the removal sentence now says "an instance" rather than "a Node-RED instance". Billing mechanics are unchanged.docs/cloud/introduction.md: the File Storage and Context Store quota tables were left with a single row each after the deprecated tiers were removed, which reads oddly. Both are now prose stating the Enterprise figure (100GB and 1GB per instance). No figures changed.Out of scope: the open question on whether the Small/Medium/Large instance size choice should be deprecated for users is unanswered, so
introduction.mdline 112 is left as is.