[{"data":1,"prerenderedAt":392},["ShallowReactive",2],{"blog-author-nick-oleary":3},[4,19,33,52,65,93,106,119,135,147,160,172,190,201,213,225,240,252,264,276,294,309,320,338,356],{"path":5,"title":6,"date":7,"authors":8,"description":6,"meta":10,"image":18},"\u002Fblog\u002F2026\u002F01\u002Fflowfuse-release-2-26","FlowFuse 2.26: Bringing access-controls to your MCP nodes","2026-01-15",[9],"nick-oleary",{"excerpt":11},{"type":12,"value":13},"minimark",[14],[15,16,17],"p",{},"With the holiday break sitting in the middle of this release cycle, it's a smaller release than usual this month. But that hasn't stopped us continuing to make the FlowFuse Expert even more useful.","\u002Fblog\u002F2026\u002F01\u002Fimages\u002Frelease-2-26.png",{"path":20,"title":21,"date":22,"authors":23,"description":24,"meta":25,"image":32},"\u002Fblog\u002F2025\u002F10\u002Fnode-red-revolution","The Node-RED Revolution: How Low-Code is Democratizing Industrial Automation","2025-10-09",[9],"Looking back on where Node-RED came from to understand the impact it has had on industry",{"keywords":26,"excerpt":27},null,{"type":12,"value":28},[29],[15,30,31],{},"To understand the impact Node-RED has had on industrial automation, it's useful to understand where it has come from and what has enabled its success.","\u002Fblog\u002F2025\u002F10\u002Fimages\u002Fnode-red-revolution.png",{"path":34,"title":35,"date":36,"authors":37,"description":38,"meta":39,"image":51},"\u002Fblog\u002F2025\u002F04\u002Fflowfuse-release-2-16","FlowFuse 2.16: Git Integration, improved log retention and more","2025-04-10",[9],"Start pushing your snapshots to git, get alerted when resources are running low and more logging from Node-RED",{"excerpt":40},{"type":12,"value":41},[42],[15,43,44,45,50],{},"Another release from the FlowFuse team to keep ",[46,47,49],"a",{"href":48},"\u002Fhandbook\u002Fcompany\u002Fstrategy\u002F","realising our mission"," to empower you to fuse the digital realm and physical reality.","\u002Fblog\u002F2025\u002F04\u002Fimages\u002Frelease-2-16.png",{"path":53,"title":54,"date":55,"authors":56,"description":57,"meta":58,"image":64},"\u002Fblog\u002F2024\u002F06\u002Fnode-red-4-on-flowfuse-cloud","Node-RED 4: Bringing better collaboration to FlowFuse Cloud","2024-06-20",[9],"Find out about the new Node-RED 4 release and what it brings to FlowFuse Cloud",{"excerpt":59},{"type":12,"value":60},[61],[15,62,63],{},"Node-RED 4.0 is the new major release of the project, which is at the heart of all we do at FlowFuse. It brings a range of new features that continue to make Node-RED the first choice for low-code development.","\u002Fblog\u002F2024\u002F06\u002Fimages\u002Fnode-red-4-on-flowfuse-cloud.png",{"path":66,"title":67,"date":68,"authors":69,"description":70,"meta":71,"image":92},"\u002Fblog\u002F2024\u002F04\u002Fnode-red-multiplayer","Node-RED Multiplayer mode","2024-04-10",[9],"An update on our work to bring concurrent editing to Node-RED",{"excerpt":72},{"type":12,"value":73},[74,89],[15,75,76,77,81,82,88],{},"Last month I ",[46,78,80],{"href":79},"\u002Fblog\u002F2024\u002F03\u002Flooking-towards-node-red-4\u002F","wrote"," about what users\ncan expect with Node-RED 4.0. One of the features I highlighted was improving the\nconcurrent editing experience. With the recent ",[46,83,87],{"href":84,"rel":85},"https:\u002F\u002Fdiscourse.nodered.org\u002Ft\u002Fnode-red-4-0-0-beta-2-released\u002F87026",[86],"nofollow","beta release"," of Node-RED, the first\nsteps on that journey are now available to try.",[15,90,91],{},"In this post, I'll cover what has been done so far and what we've got planned.","\u002Fblog\u002F2024\u002F04\u002Fimages\u002Fnode-red-multiplayer.png",{"path":94,"title":95,"date":96,"authors":97,"description":98,"meta":99,"image":105},"\u002Fblog\u002F2024\u002F03\u002Flooking-towards-node-red-4","Looking towards Node-RED 4.0 and beyond","2024-03-07",[9],"A look at what is coming in Node-RED 4.0",{"excerpt":100},{"type":12,"value":101},[102],[15,103,104],{},"With Node-RED 4.0 coming soon, I wanted to take a look at what users can expect to see with the new release,\nas well as some of the new features we're working on.","\u002Fblog\u002F2024\u002F03\u002Fimages\u002Flooking-towards-node-red-4.png",{"path":107,"title":108,"date":109,"authors":110,"description":111,"meta":112,"image":118},"\u002Fblog\u002F2024\u002F02\u002Fhistory-of-nodered","History of Node-RED","2024-02-28",[9],"Read about Node-RED's evolution from a proof-of-concept to a leading IoT platform in Nick O'Leary's firsthand account. An inspiring journey in open-source tech.",{"excerpt":113},{"type":12,"value":114},[115],[15,116,117],{},"In January 2013, I could have never foreseen that my fun little proof-of-concept project would become Node-RED, an open source low-code environment with millions of deployments in IoT and automation.","\u002Fblog\u002F2024\u002F02\u002Fimages\u002Fhistory-of-node-red.png",{"path":120,"title":121,"date":122,"authors":123,"description":124,"meta":125,"image":134},"\u002Fblog\u002F2024\u002F02\u002Fsoftware-development-in-node-red","Bringing Software Development practices to Node-RED","2024-02-06",[9],"Discover how software development practices enhance Node-RED workflows. Learn about linting, debugging, testing, and more.",{"excerpt":126},{"type":12,"value":127},[128,131],[15,129,130],{},"I'm always thinking about how we can continue to improve the Node-RED experience. One area I like to explore is to make sure we learn the right lessons from the Software Development world.",[15,132,133],{},"In this post, I'm going to look at some of the common practices in modern Software Development and show how they translate to the Node-RED world.","\u002Fblog\u002F2024\u002F02\u002Fimages\u002Fsoftware-development-practices-to-node-red.png",{"path":136,"title":137,"date":138,"authors":139,"description":140,"meta":141,"image":26},"\u002Fblog\u002F2023\u002F10\u002Fservice-disruption-report-2023-10-11","Service Disruption Report for October 11th, 2023","2023-10-18",[9],"____________",{"excerpt":142},{"type":12,"value":143},[144],[15,145,146],{},"On October 11th, 2023, we had an issue where users were not able to access the\nNode-RED editor, recieving a 'Access Denied' error message.\nThis post examines the issue that was hit, the timeline of events and\nwhat we've done to resolve it.",{"path":148,"title":149,"date":150,"authors":151,"description":152,"meta":153,"image":159},"\u002Fblog\u002F2023\u002F09\u002Frebranding-our-components","Updating our branding across GitHub, npm and Dockerhub","2023-09-27",[9],"Renaming our packages and containers and what it means for our users",{"excerpt":154},{"type":12,"value":155},[156],[15,157,158],{},"Following our rename to FlowFuse last month, we are about to take the next\nset of steps to complete the rebrand. This time, focussed on the technical\nassets we produce.","\u002Fblog\u002F2023\u002F09\u002Fimages\u002Ftile-rebranding.png",{"path":161,"title":162,"date":163,"authors":164,"description":165,"meta":166,"image":26},"\u002Fblog\u002F2023\u002F07\u002Fflowforge-1-9-3-release","FlowFuse 1.9.3 and Device Agent 1.9.5 released","2023-07-21",[9],"A maintenance release to improve the Device Agent editor experience",{"excerpt":167},{"type":12,"value":168},[169],[15,170,171],{},"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.",{"path":173,"title":174,"date":175,"authors":176,"description":177,"meta":178,"image":189},"\u002Fblog\u002F2023\u002F05\u002Fbringing-high-availability-to-node-red","Bringing High Availability to Node-RED","2023-06-02",[9],"Explore how FlowFuse tackles HA challenges, statefulness, and work routing, revolutionizing Node-RED's reliability.",{"excerpt":179},{"type":12,"value":180},[181],[15,182,183,184,188],{},"Many companies look to deploy Node-RED into use cases that require the application\nto have a high degree of availability, reliability, and scalability. Following up\nour ",[46,185,187],{"href":186},"\u002Fblog\u002F2023\u002F02\u002Fhighly-available-node-red\u002F","previous post on the subject",", in this\npost I’m going to look at some of the technical details of achieving HA, the\napproaches available and what that means for the work we’re doing at FlowFuse\nand upstream in Node-RED.","\u002Fimages\u002Fblog\u002Ftile-ha-nr.jpg",{"path":191,"title":192,"date":193,"authors":194,"description":195,"meta":196,"image":26},"\u002Fblog\u002F2023\u002F02\u002Fservice-disruption-report-2023-01-27","Service Disruption Report for January 27th, 2023","2023-02-10",[9],"On January 27th, 2023, we were alerted to an issue on FlowFuse Cloud where a user\nwas not able to access a newly created Node-RED Project, receiving a 404 error\ninstead. This post examines the issue that was hit, the timeline of events and\nwhat we've done to resolve it.",{"excerpt":197},{"type":12,"value":198},[199],[15,200,195],{},{"path":202,"title":203,"date":204,"authors":205,"description":206,"meta":207,"image":26},"\u002Fblog\u002F2022\u002F12\u002Fflowforge-joins-openjs-foundation","FlowFuse Inc. becomes a member of the OpenJS Foundation","2022-12-13",[9],"Supporting the foundation that has given Node-RED a great home",{"excerpt":208},{"type":12,"value":209},[210],[15,211,212],{},"We're pleased to share the news we've joined the OpenJS Foundation to bolster our\nsupport for the Node-RED community.",{"path":214,"title":215,"date":216,"authors":217,"description":218,"meta":219,"image":26},"\u002Fblog\u002F2022\u002F12\u002Fflowforge-1-1-2-released","FlowFuse 1.1.2 released","2022-12-09",[9],"Release includes a fix for installing additional nodes into Node-RED.",{"excerpt":220},{"type":12,"value":221},[222],[15,223,224],{},"We've published a maintenance fix with an important fix for the Palette Manager in Node-RED.",{"path":226,"title":227,"date":228,"authors":229,"description":230,"meta":231,"image":26},"\u002Fblog\u002F2022\u002F06\u002Fflowforge-06-released","FlowFuse 0.6 released","2022-06-19",[9],"Adding Devices to the platform",{"excerpt":232},{"type":12,"value":233},[234,237],[15,235,236],{},"Node-RED is well known for its role in IoT solutions - which often means running\nflows on devices.",[15,238,239],{},"This was something we always wanted to support in FlowFuse and with this release\nwe're taking the next steps in that direction.",{"path":241,"title":242,"date":243,"authors":244,"description":245,"meta":246,"image":26},"\u002Fblog\u002F2022\u002F05\u002Fflowforge-05-released","FlowFuse 0.5 released","2022-05-12",[9],"Bringing a new look to the platform",{"excerpt":247},{"type":12,"value":248},[249],[15,250,251],{},"The cycle continues with our next regularly scheduled release, bringing a fresh\nnew look to the platform.",{"path":253,"title":254,"date":255,"authors":256,"description":257,"meta":258,"image":26},"\u002Fblog\u002F2022\u002F03\u002Fflowforge-03-released","FlowFuse 0.3 released","2022-03-17",[9],"Moving towards the launch of FlowFuse Cloud",{"excerpt":259},{"type":12,"value":260},[261],[15,262,263],{},"The FlowFuse 0.3 release brings us closer to the launch of FlowFuse Cloud.\nFind out more about what's in this new release.",{"path":265,"title":266,"date":267,"authors":268,"description":269,"meta":270,"image":26},"\u002Fblog\u002F2022\u002F02\u002Fflowforge-02-released","FlowFuse 0.2 released","2022-02-17",[9],"Keeping the releases flowing of our open platform for Node-RED",{"excerpt":271},{"type":12,"value":272},[273],[15,274,275],{},"Four weeks have passed since our initial release of FlowFuse, and we're happy\nto release v0.2 today as we continue moving forward and evolve the platform.",{"path":277,"title":278,"date":279,"authors":280,"description":281,"meta":282,"image":26},"\u002Fblog\u002F2022\u002F02\u002Fwelcome-joe","Welcome Joe","2022-02-08",[9],"Welcoming Joe Pavitt to FlowFuse Inc.",{"excerpt":283},{"type":12,"value":284},[285],[15,286,287,288,293],{},"Today we welcome Joe Pavitt (",[46,289,292],{"href":290,"rel":291},"https:\u002F\u002Ftwitter.com\u002Fjoepavitt3d",[86],"@joepavitt3d",") as\nour new Head of UX & Design. This is a key role that will help deliver the awesome\nuser experience of the FlowFuse platform.",{"path":295,"title":296,"date":297,"authors":298,"description":299,"meta":300,"image":26},"\u002Fblog\u002F2022\u002F01\u002Fflowforge-01-released","FlowFuse 0.1 released","2022-01-20",[9],"Making the first release of the platform and transitioning to open development",{"excerpt":301},{"type":12,"value":302},[303,306],[15,304,305],{},"For an open core company, we haven't been very open with what we're doing. That all\nchanges today with the release of FlowFuse 0.1 and making all of our repositories\npublic.",[15,307,308],{},"This is a significant step for the company as we look to build a platform around Node-RED.",{"path":310,"title":311,"date":297,"authors":312,"description":313,"meta":314,"image":26},"\u002Fblog\u002F2022\u002F01\u002Fwelcome-steve","Welcome Steve",[9],"Welcoming Steve McLaughlin to FlowFuse Inc.",{"excerpt":315},{"type":12,"value":316},[317],[15,318,319],{},"We're continuing to grow the FlowFuse team with our latest hire; Steve McLaughlin\nwho is joining our development team.",{"path":321,"title":322,"date":323,"authors":324,"description":325,"meta":326,"image":26},"\u002Fblog\u002F2022\u002F01\u002Fwelcome-zj","Welcome ZJ","2022-01-03",[9],"Welcoming Zeger-Jan van de Weg to FlowFuse Inc.",{"excerpt":327},{"type":12,"value":328},[329],[15,330,331,332,337],{},"This year the FlowFuse team will grow further, and I'm excited to announce our\nnewest addition to the team; Zeger-Jan van de Weg (",[46,333,336],{"href":334,"rel":335},"https:\u002F\u002Ftwitter.com\u002FZJvandeWeg",[86],"@ZJvandeWeg",").\nZeger-Jan, also known as ZJ, is joining FlowFuse as CEO.",{"path":339,"title":340,"date":341,"authors":342,"description":343,"meta":344,"image":26},"\u002Fblog\u002F2021\u002F05\u002Fwelcome-ben","Welcome Ben","2021-05-10",[9],"Welcoming Ben Hardill to FlowFuse Inc.",{"excerpt":345},{"type":12,"value":346},[347],[15,348,349,350,355],{},"I'm excited to share the news that Ben Hardill (",[46,351,354],{"href":352,"rel":353},"https:\u002F\u002Ftwitter.com\u002Fhardillb",[86],"@hardillb",") is joining FlowFuse as a Senior Engineer.",{"path":357,"title":358,"date":359,"authors":360,"description":361,"meta":362,"image":26},"\u002Fblog\u002F2021\u002F04\u002Ffirst-deploy","Introducing FlowFuse Inc.","2021-04-06",[9],"Building a new low-code development platform around the Node-RED project",{"excerpt":363},{"type":12,"value":364},[365,374,377,380,389],[15,366,367,368,373],{},"When Dave and I first created ",[46,369,372],{"href":370,"rel":371},"https:\u002F\u002Fnodered.org",[86],"Node-RED",", it was a tool to solve a\nproblem - allowing us to do our day job more effectively when building IoT solutions\nfor clients. That gave us the means and purpose to create a truly useful platform.",[15,375,376],{},"When it became an open source project, it quickly found an enthusiastic audience that\nhas seen the community grow beyond our imagination. From both individual users, to a wide\nrange of companies integrating it into their own products.",[15,378,379],{},"But with that growth, the question in my mind has always been how to take it further\nand secure its long term future.",[15,381,382,383,388],{},"I wrote on the ",[46,384,387],{"href":385,"rel":386},"https:\u002F\u002Fnodered.org\u002Fblog\u002F2020\u002F10\u002F13\u002Ffuture-plans",[86],"project blog","\nlast year about the future plans of the project. A key piece of that is its sustainability -\nhow we can increase the commercial adoption of Node-RED and how we can get more people\ncontributing back.",[15,390,391],{},"An opportunity presented itself earlier this year that I believe will bring a\nstep-change to what the Node-RED project is able to achieve.",1786117170023]