Skip to content

Include remote instances in hub feature table #5587

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

Closed
knolleary wants to merge 1 commit into from
+2 −2
Closed

Include remote instances in hub feature table #5587

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions nuxt/content/feature-catalog.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ sections:
- id: edge-development
title: Edge Development
description: "Develop and test Node-RED flows directly on edge devices with a remote editor proxy."
tiers: { edge: true, hub: false, fleet: true }
tiers: { edge: true, hub: true, fleet: true }

@ZJvandeWeg ZJvandeWeg Aug 13, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@knolleary How many? I would limit this.

@knolleary knolleary Aug 13, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

What had been agreed was the license includes a set number of runtimes - that could be either hosted or remote - rather than individual limits.

@ZJvandeWeg ZJvandeWeg Aug 14, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@knolleary So what's the difference between Hub and Edge?

- id: private-npm-registry
title: Custom Node-RED Nodes
description: "Create and manage your own private npm registry for Node-RED nodes, so you can share custom nodes across your team and devices without publishing them publicly."
Expand Down Expand Up @@ -54,7 +54,7 @@ sections:
- id: edge-devices
title: Edge Instances
description: "Deploy and mange your Node-RED instances on edge PLCs and gateways, with full visibility and control from the cloud."
tiers: { edge: true, hub: false, fleet: true }
tiers: { edge: true, hub: true, fleet: true }

@ZJvandeWeg ZJvandeWeg Aug 13, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@knolleary How many? I would limit this.

- id: custom-hostnames
title: Custom Hostnames
tiers: { edge: false, hub: true, fleet: false }
Expand Down