Conversation
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
@lbeau @MichaelBDavis can you have a look here? This PR sets us up in two ways:
You can review the changes directly here:
|
|
@Yndira-E adding you as a reviewer as well, see https://flowfuse.slack.com/archives/C09QS57R8AD/p1772192847293829?thread_ts=1772184741.264499&cid=C09QS57R8AD |
|
I would like to limit AI capabilities to our enterprise tier. I'm comfortable with lower tiers trying out the functionality for a period of time, but eventually these capabilities should be powerful enough to draw folks into the higher tiers on the basis of that feature alone. |
|
@Steve-Mcl what is our current exposure of insights mode and MCP server nodes VS FlowFuse tier (FlowFuse CLoud and Selfhosted)? Afaik it currently aligns with what has been defined as of now right? see https://deploy-preview-4607--flowforge-website.netlify.app/pricing/ |
This comment was marked as resolved.
This comment was marked as resolved.
@dimitrieh |
|
Thanks @Steve-Mcl that aligns with my assumptions |
|
@hardillb can you give this a final look in terms of code? |
Code review auditCode reviewNo issues found above the confidence threshold (80/100). Checked for bugs, CLAUDE.md compliance, git history context, previous PR comments, and code comment adherence. Notable observations below threshold (scored 75/100):
These did not meet the confidence threshold for flagging as issues because they may be intentional design decisions or are pre-existing patterns. 🤖 Generated with Claude Code If this code review was useful, please react with 👍. Otherwise, react with 👎. |
Replace pricingFeatures.yaml with a structured featureCatalog.yaml that uses named tier keys (starter/pro/enterprise) instead of position-dependent arrays, plain-text descriptions instead of inline HTML, and adds metadata fields (docsLink, changelog, solutions, showOnPricing, showOnFeaturesPage) to support feature data reuse across multiple pages. - Add src/_data/featureCatalog.yaml with all features migrated - Update features-table-base.njk to render from new data structure - Add handbook/engineering/product/features.njk as complete internal reference - Add solution-features.njk reusable component (not yet wired to pages) - Delete src/_data/pricingFeatures.yaml
…d Node-RED MCP Servers
…ve redundant note
- Add beta flag to Insights Mode feature, rendered as a badge next to the feature name in both pricing and handbook tables - Update Node-RED MCP Servers tagPrefix to "During Insights Mode" and note to "Available during beta of Insights Mode" - Fix handbook Beta badge padding with inline style
|
@dimitrieh With subitems, like in #4607 (comment), should the top level item be left aligned? |
@ZJvandeWeg looking into this. Side-question: Should we re-order our offerings with the most ideal one first, meaning enterprise? Anthropics does a similar thing with their newest model comparisons:
|
The distinction is intentional. The hero CTA was aimed at teams who want to technically evaluate the full Enterprise setup via a trial licence. Further down, after reviewing the feature details, “Request a quote” aligns more with organizations already considering procurement. Happy to align them if we decide consistency is preferable. |
|
@Yndira-E please take my comment with a grain of salt 🙃. Good to know there was thought behind it. Do think it makes things slightly confusing especially VS the Pro tier, though I can understand the want to direct towards a trial 🤔. My suggestion here would be to then create consistency and separate concerns. We can communicate a trial period is a possibility. Setting something up... |
Good question, I think this ties into how we want to position FlowFuse overall. Are we aiming to lead with Enterprise from a positioning perspective, or keep the tiered progression (Starter → Pro → Enterprise)? If we decide to lead with Enterprise, we should probably keep the order consistent across the whole page (hero cards and comparison table) to avoid cognitive switching while scanning. |
|
Edit: changes are moved to #4619 |
|
Please make sure the first cell is transparent instead of white. The top left one above "Empower". |
@Yndira-E White bg artifact is because of browser zoom. Is a non issue. Feel free to check the preview deployment |
|
This is ready to merge, but awaiting review by @lbeau as stated in https://flowfuse.slack.com/archives/C05GYH95NJZ/p1772455163819599?thread_ts=1772452761.313169&cid=C05GYH95NJZ |
e0d5c25 to
7c4dd23
Compare
…tally Move the fullscreen toggle button outside the overflow-x-auto wrapper into a new outer container. The button no longer scrolls away when the table is scrolled horizontally, while fullscreen mode continues to work with the sticky close button at the top.
|
Out of scope changes have been scoped out and moved to #4619 Merging |







Description
Adds FlowFuse Expert to the pricing page under a new Empower section, making it clearly visible to customers evaluating plans. FlowFuse Expert is available on all FlowFuse Cloud tiers and on request for Self-Hosted Enterprise customers.
This PR also refactors all pricing feature data to use
featureCatalog.yamlas a single source of truth, introduces a dedicated handbook page at/handbook/engineering/product/features/, and includes several visual refinements to the pricing page layout.Changes include:
featureCatalog.yamlis now the canonical source for all feature data across Cloud and Self-Hosted tierstag/tagPrefixfields in YAML render styled pill badges (e.g., "While in Beta") with proper spacing/handbook/engineering/product/features/covering all sections, tiers, and solutionssubfeature: trueflag renders child rows with└tree connector and visual indentationminmax(0, 1fr)to prevent wide tables from overflowing the page.ff-feature-tag-prefixCSS rule and oldpricingFeatures.yamlRelated Issue(s)
N/A
Checklist