Skip to content

Apply review follow-ups to Cloud billing and quota docs #7946

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dimitrieh wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Apply review follow-ups to Cloud billing and quota docs #7946

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c2e1ffb
Apply review follow-ups to Cloud billing and quota docs
dimitrieh Jul 27, 2026
d41fbcd
Merge branch 'main' into repackaging/docs-billing-and-quota-followup
hardillb Jul 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/cloud/billing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,14 +30,14 @@ instances and Devices owned by the team.

## 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.

@dimitrieh dimitrieh Jul 27, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.


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

@dimitrieh dimitrieh Jul 27, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

at the end of the cycle.

## 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.

@dimitrieh dimitrieh Jul 27, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Applies the suggestion at #7930 (comment) verbatim. Terminology only, "a Node-RED instance" to "an instance".


## Suspended Instances

Expand Down
13 changes: 3 additions & 10 deletions docs/cloud/introduction.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,12 +116,8 @@ Medium and Large instance types require the Enterprise tier.
FlowFuse Cloud hosted instances have access to a persistent file-system that will
retain the files stored on it across restarts of the instance.

A quota limit is applied to how much data can be stored, which varies based on
the Team type.

| Team Type | File Storage Quota (per 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.

@dimitrieh dimitrieh Jul 27, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.


Files can be manually uploaded to an instance using the [Static Asset Service](https://flowfuse.com/blog/2024/08/flowfuse-2-8-release/#static-assets-service).

Expand All @@ -134,10 +130,7 @@ FlowFuse Cloud provides an optional context store that can be used to persist
the data.

The amount of data that can be stored in context is determined by the Team type.

| Team Type | Context Store Quota (per instance) |
|--------|--------|
| Enterprise | 1GB |
Enterprise teams have a context store quota of 1GB per instance.

@dimitrieh dimitrieh Jul 27, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The table this replaces is the one the note at #7930 (comment) was left on. The 1GB figure is unchanged.



## Network Connections
Expand Down
Loading