FlowFuse · ZJvandeWeg · Aug 28, 2026 · Aug 28, 2026
diff --git a/nuxt/content/faq/pricing.yml b/nuxt/content/faq/pricing.yml
@@ -4,7 +4,7 @@ items:
   - question: "What's the difference between Edge and Hub?"
     answer: "Edge is a product designed specifically for OT teams and the unique challenges they manage. With Edge, you can connect PLCs, machines, and systems, applying a standardised methodology for deploying automation at scale. This tier comes with everything in the FlowFuse core platform, but also includes support for Device Fleet Updates and Device Group Management. Additionally, this tier includes the OT Certified Nodes collection and deployable OT Application Blueprints.<br><br>Hub is a product better suited for IT teams moving data between their systems and orchestrating multi-plant installations. For this reason, it includes everything in the FlowFuse core platform, as well as some particularly useful features for this use case. It includes Git Integration, High Availability, BAA for HIPAA, and Protected Instances. It also includes the IT Certified Nodes collection and deployable IT Application Blueprints.<br><br>For customers requiring something between these two featuresets, please <a href='/contact-us'>Contact Us</a> so we can help build a tailored solution for your environment!"
   - question: "How does customer support work for FlowFuse?"
-    answer: "FlowFuse provides active support for Certified Nodes and the FlowFuse platform per the <a href='/handbook/sales/subscription-agreement-1.5'>SLA</a>. Customers with these features can get support by <a href='/support'>filing a ticket</a> or via help information in the <a href='/support'>FlowFuse Support Portal</a>. For general issues related to Node-RED or third party modules, raise issues in the <a href='https://community.flowfuse.com/'>community forum</a>."
+    answer: "FlowFuse provides active support for Certified Nodes and the FlowFuse platform per the <a href='/handbook/sales/customer-success/#sla'>SLA</a>. Customers with these features can get support by <a href='/support'>filing a ticket</a> or via help information in the <a href='/support'>FlowFuse Support Portal</a>. For general issues related to Node-RED or third party modules, raise issues in the <a href='https://community.flowfuse.com/'>community forum</a>."
   - question: "How does FlowFuse secure my data?"
     answer: "FlowFuse employs a layered approach to securing customer data. For a fuller understanding of the mechanisms behind this approach, please read our <a href='/platform/security/'>security statement</a> as well as our <a href='/docs/contribute/architecture/'>architecture documentation</a>.<br><br>FlowFuse secures user access through username/password, SAML-based SSO, or LDAP, with support for multi-factor authentication and automatic session expiry after 14 days. Access is governed by role-based controls within Teams - Owner, Member, Viewer, and Dashboard roles - while platform-wide admin access is tightly restricted (on FlowFuse Cloud, limited to vetted employees on a need-to-have basis). All administrative and team-level actions are captured in audit logs. On FlowFuse Cloud, data is encrypted at rest with AES-256 (PostgreSQL and AWS EFS), stored in the EU (Ireland), and protected in transit with TLS 1.2 or higher terminated at the edge for both HTTP and MQTT traffic.<br><br>Organizationally, FlowFuse holds SOC 2 Type 1 and Type 2 certifications (audited by Advantage Partners) and maintains formal information security, acceptable use, and data management policies alongside regular security awareness training. The platform is also built to be GxP validation-ready: features like role-based access control, audit logging, instance versioning and snapshots, infrastructure-as-code, and SSO/LDAP integration align with the traceability and change-control expectations of regulated environments such as FDA 21 CFR Part 11 and EU GMP Annex 11, enabling customers to perform their own validation and supplier qualification."
   - question: "Does FlowFuse offer annual discounts for FlowFuse Cloud?"

diff --git a/nuxt/content/feature-catalog.yml b/nuxt/content/feature-catalog.yml
@@ -375,7 +375,7 @@ sections:
       - id: baa-for-hipaa
         title: BAA for HIPAA
         description: "FlowFuse can sign a Business Associate Agreement to ensure proper safeguarding of protected health information handled on your behalf."
-        docsLink: /handbook/sales/subscription-agreement-1.5/
+        docsLink: /handbook/sales/subscription-agreement-1.6/
         tiers: { edge: false, hub: true, fleet: false }
       - id: sbom
         title: Software Bill of Materials

diff --git a/nuxt/content/handbook/engineering/support/index.md b/nuxt/content/handbook/engineering/support/index.md
@@ -10,7 +10,7 @@ Support tickets can be opened via the [FlowFuse Support Portal](/support). FlowF
 
 ## SLAs
 
-For all FlowFuse customers, we have an [SLA](/handbook/sales/subscription-agreement-1.5) defined as part of the Subscription Agreement. Initial responses to support tickets must be sent within the SLA time frame defined in the Subscription Agreement.
+All paying FlowFuse customers get a Standard Support SLA by default; a faster Enterprise-level SLA can be purchased and negotiated as an upgrade. See the [SLA definitions](/handbook/sales/customer-success/#sla) for the current response-time commitments. Initial responses to support tickets must be sent within the applicable SLA time frame.
 
 ## Triage Duty
 

diff --git a/nuxt/content/handbook/engineering/support/triage.md b/nuxt/content/handbook/engineering/support/triage.md
@@ -89,7 +89,7 @@ Some customers have response-time SLAs based on their subscription.
 
 Triage leads are not responsible for enforcing SLAs directly, but are responsible for ensuring tickets are routed and acknowledged in a way that supports them.
 
-Current SLA definitions and response expectations are documented in the [Subscription Agreement](/handbook/sales/subscription-agreement-1.5/).
+Current SLA definitions and response expectations are documented in [Customer Success](/handbook/sales/customer-success/#sla).
 
 When triaging:
 

diff --git a/nuxt/content/handbook/sales/customer-success.md b/nuxt/content/handbook/sales/customer-success.md
@@ -234,16 +234,16 @@ customer direct to a repo for a 3rd party node question.
 
 #### SLA
 
-Support availability and response times are defined by the customer’s subscription level:
+All paying customers get a Standard Support SLA by default. A faster, Enterprise-level SLA can be purchased and negotiated as an upgrade.
 
-- Standard Support
+- Standard Support (default for all paying customers)
   - Support available 24 × 5 (Monday to Friday, UTC-2 timezone)
-  - First Response SLA: Next business day (within 24 hours)  
+  - First Response SLA: Next business day (within 24 hours)
   - Support tickets can be submitted at [our Support Form](/support/)
 
-- Enterprise (Enterprise Support)
+- Enterprise Support (purchasable/negotiable upgrade)
   - Support available 24 × 5 (Monday to Friday, UTC-2 timezone)
-  - First Response SLA: 4 hours  
+  - First Response SLA: 4 hours
   - Support tickets can be submitted at [https://flowfuse.com/support/](/support/)
 
 #### Escalation

diff --git a/nuxt/content/handbook/sales/legal.md b/nuxt/content/handbook/sales/legal.md
@@ -13,7 +13,7 @@ See the [Signatures](/handbook/operations/signatures/) page in Operations for pr
 ## Subscription agreement
 
 For self-managed licenses FlowFuse has a standard
-[subscription agreement template](/handbook/sales/subscription-agreement-1.5/).
+[subscription agreement template](/handbook/sales/subscription-agreement-1.6/).
 When a customer sends over their Standard terms before signing the subscription
 agreement, we have a
 [standard response overview](https://docs.google.com/document/d/1US_eixmRtzzFHybl3l9woP0isrwvK2_t7nPXoKYiuq4/edit?tab=t.0#heading=h.w8522tz1d0cr).

diff --git a/nuxt/content/handbook/sales/subscription-agreement-1.5.md b/nuxt/content/handbook/sales/subscription-agreement-1.5.md
@@ -5,6 +5,8 @@ navigation:
   order: 23
 ---
 
+**Superseded.** This version has been replaced by the [Subscription Agreement 1.6](/handbook/sales/subscription-agreement-1.6/) and is kept here only because it's still referenced by existing contracts and quotes. Do not link new customers to this page.
+
 Below is the FlowFuse subscription agreement that applies to few Edge, Hub, and Fleet tier customers buying annual subscriptions, and most customers on the legacy Enterprise Platform. If you'd like to make alterations for your organization, please download the .docx file in the following form and initiate the legal part of the negotiation through your account executive.
 
 Note alterations to the following agreement are only accepted on the Enterprise tier.
-Original file line number
+Diff line change
@@ Expand Up @@
     ## SLAs
-    For all FlowFuse customers, we have an [SLA](/handbook/sales/subscription-agreement-1.5) defined as part of the Subscription Agreement. Initial responses to support tickets must be sent within the SLA time frame defined in the Subscription Agreement.
+    All paying FlowFuse customers get a Standard Support SLA by default; a faster Enterprise-level SLA can be purchased and negotiated as an upgrade. See the [SLA definitions](/handbook/sales/customer-success/#sla) for the current response-time commitments. Initial responses to support tickets must be sent within the applicable SLA time frame.
     ## Triage Duty
@@ Expand Down @@