📅 Node-RED Con 2025 - Call For Papers now open!

We're excited to announce that Node-RED Con 2025 will be held online on Tuesday, 4 November 2025.

This year, the conference is dedicated to showcasing the power of Node-RED applications in industry. It's a community-centric event for developers, engineers, and enthusiasts to share practical knowledge and explore real-world solutions.

The conference programme is built entirely from community submissions, and the Call for Papers is now open! We are looking for:

  • Full Talks & Demos on industrial use cases, IoT architectures, and edge computing.
  • Inspiring Lightning Talks showcasing fun and creative projects.
  • Expert Panelists for discussions on the future of industrial automation.

If you have a story to tell, this is your platform to share your expertise and innovations.

Find full details and submit your proposal at the conference page: https://nrcon.nodered.org/

2 Likes

The theme is Node-RED applications in Industry, but will there be content of interest to non-Industrial use cases as well?

I'm thinking about applying:

2 Likes

There's a category for Lightning Talks for any kind of "fun, cool, or inspiring projects" built with Node-RED. You can see more details here.

1 Like

It's been a couple weeks since we announced the CFP for Node-RED Con and we've already had some great talks come in. But there's always room for more!

If you've got a story to tell, please do consider submitting a talk!

(And also, a big Thank You to @Yndira-E who is handling so much of the organising behind the scenes!)

1 Like

Hi knolleary, it's has been a long walk from node-red v1 till today.

I can not provide full uses of how we use node-red in production for French Central Banks but I can tell it did help greatly many useless meeting, documentation, workflow and basically remove a lot of business analyst/workflow/process/technical analysis by simply displaying a BOARD of flow.

Usefull we allow a business analyst to display a targetted process by empty boxes + unit tests
Then dev completes boxes until unit-test is validated
Then a isolated flow is created as a module

We still miss production grade system ( JIRA ) , Replay a day and a Multi Flow external monitors for orchestration ( so we developped it ourself )

To avoid messy display, it would be usefull to have multiple layers

  1. Layer for valid flow
  2. Non displayed unit test Layers for validation linked to JIRA or ticketting
  3. Non displayed layer for monitoring messages
  4. Non displayed admin layer for halting/replaying/resume

But overall Node-Red has always been easy way to bypass ETL

Hi all,

Only 15 days left to submit your talk proposals for the Node-RED Con 2025– the CFP closes on 25 July. :alarm_clock:

Don't miss the chance to share your work: https://nrcon.nodered.org/

Registrations will open soon, you can sign up for email updates through FlowFuse, or keep an eye on this thread, or our socials for the announcement!

1 Like