Draft blog post on FlowFuse Certified Nodes#5152
Open
KristopherLeads wants to merge 8 commits into
Open
Conversation
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
ZJvandeWeg
requested changes
Jun 5, 2026
|
|
||
| **Security:** FlowFuse proactively resolves potential vulnerabilities and revokes certification from any node that falls short - and notifies affected customers when that happens, so you're never the last to find out. Your nodes are secure by default - removing an entire headache from your workflow. | ||
|
|
||
| **Support:** When a Certified Node gives you trouble, you get real troubleshooting help and a defined path to resolution, not an unanswered issue queue. FlowFuse node certification also means FlowFuse supported - so you get real, human support, not automatically generated documentation that may or may not map to solutions. |
Member
There was a problem hiding this comment.
I think the long term goal is to support each minor semver version for a decade. We cannot promise that today, but if you've built something now, it should continue to work and improve long term. (Performance etc)
Contributor
Author
There was a problem hiding this comment.
Is that something we want to call out here, or do we want to be somewhat general in our public stance to give us flexibility?
Co-authored-by: Zeger-Jan van de Weg <[email protected]>
Co-authored-by: Zeger-Jan van de Weg <[email protected]>
Adding liability comment based on #5152 (comment).
Updating per feedback #5152 (comment)
Updated text to emphasize the importance of security in handling sensitive data and the benefits of using Certified Nodes for compliance and risk management. #5152 (comment)
Added section about Certified Nodes and their benefits. #5152 (comment)
Contributor
Author
|
@ZJvandeWeg I added in a bunch of content to match these requests. Please take a look and let me know what you think. @PabloFilomeno83 let me know once you run your review. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
On request from ZJ: draft blog post for certified nodes.
Related Issue(s)
Checklist