From 854092025148c7bae995af85cf3768c96eb61913 Mon Sep 17 00:00:00 2001 From: Esmewieringa Date: Tue, 6 Oct 2026 17:58:09 +0200 Subject: [PATCH] Update introduction.md Updated the page - removing enterprise language and adjusted trial set up. --- docs/cloud/introduction.md | 37 ++++++++++++------------------------- 1 file changed, 12 insertions(+), 25 deletions(-) diff --git a/docs/cloud/introduction.md b/docs/cloud/introduction.md index 39aee0aa6d..1e5f2a309e 100644 --- a/docs/cloud/introduction.md +++ b/docs/cloud/introduction.md @@ -25,26 +25,23 @@ The [Concepts](/docs/user/concepts/) remain the same, but we run the platform fo When users sign-up to FlowFuse Cloud they get a 30-day free trial of the platform. This is a great way to start using FlowFuse and discover a lot of the value it provides. -Users can end their trial by heading to the Billing page of their team and -setting up their payment information. This includes the option to pick which -plan you want to upgrade the team to. +The trial ends automatically after 30 days. FlowFuse will reach out during the trial via email. +If the user wants to continue on our platform or want to learn more about FlowFuse, a meeting will be set up with sales. Otherwise, at the end of the 30-day trial period, any instances created in the team will be suspended. This means they will no longer be running and the -editor will not be accessible. Users will need to add their Billing details at which -point they will be able to restart their suspended Node-RED instances. +editor will not be accessible. We will email users about their trial when it is nearing the end to ensure they know what is happening. ## Billing -Customers are billed at the team level for each Node-RED instance they create. This is a recurring monthly charge. -See the [Billing](/docs/cloud/billing/) page for more detailed answers about billing. +Customers will only get billed for teams that aren't in a trial anymore and will need to sign an order form for an annual contract. This will be handled via sales or the CSM. ## Support -Premium customers can get support by [filing a ticket](/support). We offer +Customers can get support by [filing a ticket](/support). We offer support for the FlowFuse application and your account, any issues relating to Node-RED such as your flows or a 3rd party node should be raised in the [community forum](https://community.FlowFuse.com). @@ -57,18 +54,8 @@ and click the button to resend it. ## Team Types -FlowFuse Cloud offers a Trial and an Enterprise Team Type, aimed at different sorts of users +FlowFuse Cloud offers a Edge Trial, Edge, Hub and Fleet Team Type, aimed at different sorts of users. -### Enterprise - -Enterprise includes: - - - HA for Instances - - SSO - - Better Support SLA - - MQTT Broker - -Includes 10 instances and 20 MQTT Clients in the base price ### Changing Team Type @@ -109,7 +96,7 @@ table shows what is currently allocated by instance size. | Medium | 768MB | | Large | 3840MB | -Medium and Large instance types require the Enterprise tier. +Medium and Large instance types require Edge, Hub or Fleet. ## Use of the File System @@ -117,7 +104,7 @@ FlowFuse Cloud hosted instances have access to a persistent file-system that wil retain the files stored on it across restarts of the instance. 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. +Edge, Hub and Fleet teams have a file storage quota of 100GB per instance. 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). @@ -130,7 +117,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. -Enterprise teams have a context store quota of 1GB per instance. +Edge, Hub and Fleet teams have a context store quota of 1GB per instance. ## Network Connections @@ -154,16 +141,16 @@ Node-RED inside the FlowFuse Cloud platform. MQTT Connections to an external broker using the standard MQTT nodes will work fine as the connection is initiated by Node-RED. -FlowFuse provides an MQTT broker for Enterprise Node-RED instances. See the following section. +FlowFuse provides an MQTT broker for EDge, Hub and Fleet Node-RED instances. See the following section. Also the Project Nodes can be used to easily pass messages between Node-RED instances running in the platform. #### Enterprise Team Broker -Enterprise teams come with their own MQTT broker. You can provision clients from the broker tab in the left hand menu. +Edge and Fleet teams come with their own MQTT broker. You can provision clients from the broker tab in the left hand menu. -Enterprise level Teams can register up to 20 clients as part of their plan. The ability to purchase additional packs of clients will come in a near future release. +Teams can register up to 20 clients as part of their plan. The ability to purchase additional packs of clients will come in a near future release. The broker is available on `broker.flowfuse.cloud` and supports the following connection types: