# Project Nodes vs. MQTT
**URL:** https://discourse.nodered.org/t/project-nodes-vs-mqtt/101698
**Category:** FlowFuse
**Created:** [28 August 2026 17:00 UTC](https://discourse.nodered.org/t/project-nodes-vs-mqtt/101698 "2026-08-28T17:00:42Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@kenm](https://discourse.nodered.org/u/kenm)
#### Post date: [28 August 2026 17:00 UTC](https://discourse.nodered.org/t/project-nodes-vs-mqtt/101698/1 "2026-08-28T17:00:42Z")
Currently testing a proof-of-concept with FlowFuse Community Edition and I see that Project Nodes are not supported without an Enterprise license. My first thought was to just use MQTT messaging between instances.
Besides the obvious multiple ingress and egress points provided by project nodes, what are the advantages versus just using MQTT?
---
### Author:  [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [28 August 2026 20:54 UTC](https://discourse.nodered.org/t/project-nodes-vs-mqtt/101698/2 "2026-08-28T20:54:27Z")
The project nodes provide zero config inter-communication between hosted instances (in side your env) and remote instances (those controlled by the device-agent).
You can pretty much achieve the same thing with MQTT yes, but that is up-to you to deal with.
They are a value-add feature of licenced FlowFuse unfortunately. (we have to pay the bills 😉 )
---
### Author:  [@kenm](https://discourse.nodered.org/u/kenm)
#### Post date: [28 August 2026 21:23 UTC](https://discourse.nodered.org/t/project-nodes-vs-mqtt/101698/3 "2026-08-28T21:23:09Z")
Thanks Steve. That makes a lot of sense. I'm thinking small scale for my PoC but I can see the advantage in a large, dynamic environment where the context is automatic or at least auto-updated.
Added to my justification list.