Blog

FlowFuse is pleased to announce they are now offering Node-RED plus select third party nodes from the Bosch Rexroth ctrlX World marketplace.

FlowFuse is used by businesses and hobbyists alike. We aim to provide a platform that meets the needs of both, recognizing the importance of hobbyists in the Node-RED community and the long term success of FlowFuse as a company. We want to make it as easy as possible for people to get started on FlowFuse Cloud and help them understand the full value the platform offers. One of the barriers we've seen has been the current pricing structure of FlowFuse Cloud.

FlowFuse 1.11 introduces a new starter tier for FlowFuse Cloud that makes it easier to get started with FlowFuse and Node-RED.

More than once we’ve been in discussion with prospective customers on what tier is the right tier for their current Node-RED adoption. The question is likely to come up "Why wouldn't we just use the open source version of FlowFuse?". The implicit discussion created is one that is alike the question: “Why wouldn’t we go with your competition?”. For FlowFuse, and most other open-core companies like us, the open licensed and free to use core is tier, not competition.

FlowFuse 1.10 release includes improvements to device management and importing environment variable templates.

Using images in your Node-RED dashboards can significantly improve your users' experience. The most common method to add images to dashboards is to store them within the filesystem of an Node-RED instance but sometimes that's not an option. How can you easily use images when working in a containerized environment such as Docker, or Kubernetes? We will also explore latest feature from FlowFuse that makes this step super easy.

FlowFuse and the Device Agent both received updates yesterday that bring improvements to the Device Agent editor experience, making it more resilient to network issues.

FlowFuse 1.9 adds new features to make it easier to administer FlowFuse platform deployments, including new API documentation and the ability to create customized Node-RED palettes.

FlowFuse 1.8 introduces two key features that allow organizations to reliably deploy Node-RED applications into production. In 1.8, it is now possible to run Node-RED applications with high availability so the application is more scalable and more fault tolerant. FlowFuse 1.8 also introduces software deliver pipelines, so development teams can now set up dev/test/production environments for their Node-RED applications.

FlowFuse 1.7 adds new support for accessing the Node-RED Editor on Devices via FlowFuse.

FlowFuse's device agent allows you to manage and run your Node-RED instances on your own hardware such as a Raspberry Pi. This can be very useful where an application you've written needs to run flows with direct access to hardware sensors.

In this article I'm going to explain the steps to configure our device agent to run as a service in Raspbian OS, or any other OS that uses systemd.

"Do you use Node-RED?" This simple question became our favorite conversation opener as ZJ and I attended Hannover Messe, the world's leading industrial trade fair.

The new FlowFuse 1.6 adds new support for multi-instance Node-RED within a single application and support for logging from remote devices.

For FlowFuse 1.5 we have been busy making a lot of UX changes and upgrading our underlying architecture to enable future innovations on the FlowFuse platform.