Softwr

Networking · head to head

Domotz vs Eclipse Mosquitto

Domotz logo

Domotz

Networking

Network monitoring for MSPs and IT teams priced per managed device or per collector, with published rates

From
On request
Rated
-
Eclipse Mosquitto logo

Eclipse Mosquitto

Networking

Small, EPL-licensed MQTT broker that runs on hardware other brokers cannot

From
Free
Rated
-

The short version

  • Only Eclipse Mosquitto has a free tier, so it costs nothing to try first.
  • Each has a real cost: Domotz the Managed Device Plan bills in bundles of ten, so a network with, for example, eleven devices to manage pays for twenty rather than a precise count; Eclipse Mosquitto there is no clustering: Mosquitto is a single process, so high availability means building your own failover and accepting session loss on switchover.
  • They diverge on capability: Domotz covers Device discovery and monitoring, Eclipse Mosquitto covers MQTT 5.0 support.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Domotz and Eclipse Mosquitto actually diverge.

Attributes where Domotz and Eclipse Mosquitto differ
AttributeDomotzEclipse Mosquitto
Starting priceOn requestFree
Pricing modelPer collector or per managed device per monthOpen source, no licence fee
Free tierNoYes
PlatformsWeb, iOS, AndroidLinux, Windows, macOS, Docker

Identical on both: user rating (Not yet rated), category (Networking).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Domotz

  • Device discovery and monitoring
  • Remote access without VPN
  • Two published pricing models
  • Automated alerting
  • MSP client segregation

Only in Eclipse Mosquitto

  • MQTT 5.0 support
  • Very small footprint
  • Bridging
  • WebSockets listener
  • Command line clients
  • Dynamic security plugin

What people use each for

The jobs each tool is most often brought in to do.

Domotz

  • An MSP with high device density per client site wanting predictable flat pricing per collector rather than counting individual devicesnot Eclipse Mosquitto
  • An IT integrator managing many small sites with few devices each, better served by per-device pricing than a flat collector feenot Eclipse Mosquitto
  • A field services or retail IT team needing remote access to branch equipment without configuring VPN tunnels to each sitenot Eclipse Mosquitto
  • A team wanting a directly comparable public price against Auvik before starting a sales conversation with either vendornot Eclipse Mosquitto

Eclipse Mosquitto

  • A home or building automation stack where the broker must run on the same small computer as everything elsenot Domotz
  • An industrial gateway that buffers local telemetry and bridges selected topics to a cloud brokernot Domotz
  • Local development and testing of MQTT clients without provisioning a cloud IoT servicenot Domotz
  • An air-gapped deployment where a broker with no licence server and no phone-home behaviour is a requirementnot Domotz

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Domotz

  • The Managed Device Plan bills in bundles of ten, so a network with, for example, eleven devices to manage pays for twenty rather than a precise count
  • The Collector Plan gives full access per collector regardless of device count monitored by that collector, which can be inefficient for a site with very few devices relative to the flat $35 fee
  • As a SaaS platform, ongoing monitoring depends on the local Collector maintaining connectivity to Domotz's cloud, so a site-level outage that also cuts collector connectivity limits remote visibility exactly when it is needed
  • Feature depth for large enterprise NOC-style operations is narrower than platforms built for that scale, since Domotz's roadmap centres on MSP and integrator use cases
  • Remote access without VPN configuration is convenient but depends on Domotz's own relay infrastructure remaining available and trusted, which is a different security posture than a customer-controlled VPN
  • Volume and annual discounts exist but the specific discount schedule is not fully published, so very large deployments still benefit from negotiating directly rather than relying on the list price

Eclipse Mosquitto

  • There is no clustering: Mosquitto is a single process, so high availability means building your own failover and accepting session loss on switchover.
  • Persistence is a local file rather than a replicated store, so a disk failure or an unclean shutdown can lose retained messages and queued QoS traffic.
  • Practical capacity is a few thousand concurrent clients on typical hardware, so a growing device fleet eventually forces a migration to a clustered broker.
  • The Eclipse Public Licence is weak copyleft rather than permissive, which some legal teams treat as a blocker when embedding the broker in a shipped commercial product.
  • There is no commercial support to buy from the project, so production incidents rely on community mailing lists or on paying a third party who happens to know the codebase.

Pricing, plan by plan

Domotz

On request
  • Collector Plan$35/month
    • Full platform access on every device that collector monitors
  • Managed Device Plan$1.5/month
    • Billed in bundles of 10 devices
    • All non-managed devices on the network discovered at no extra cost

Eclipse Mosquitto

Free
  • Eclipse MosquittoFree
    • Eclipse Public License 2.0 with Eclipse Distribution Licence
    • MQTT 5.0, 3.1.1 and 3.1
    • No client or message limits beyond your hardware

Which should you pick?

Choose Domotz if

  • You need device discovery and monitoring.
  • You work on Web, iOS, Android.
  • You also want remote access without vpn.

Choose Eclipse Mosquitto if

  • You need mqtt 5.0 support.
  • You want to start without paying.
  • You work on Linux, Windows, macOS, Docker.
  • You also want very small footprint.

Questions people ask

Is Domotz or Eclipse Mosquitto better?
Neither clearly leads. Domotz starts at On request and Eclipse Mosquitto at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Domotz or Eclipse Mosquitto?
Eclipse Mosquitto has a free tier; the other does not. Paid plans start at On request for Domotz and Free for Eclipse Mosquitto.
Does Domotz or Eclipse Mosquitto run on more platforms?
Domotz runs on Web, iOS, Android. Eclipse Mosquitto runs on Linux, Windows, macOS, Docker.
Can I use Eclipse Mosquitto for free?
Yes. Eclipse Mosquitto has a free tier, so you can try it without paying. Domotz starts at On request.
What is Domotz best used for?
Domotz is most often used for an msp with high device density per client site wanting predictable flat pricing per collector rather than counting individual devices, an it integrator managing many small sites with few devices each, better served by per-device pricing than a flat collector fee, a field services or retail it team needing remote access to branch equipment without configuring vpn tunnels to each site, a team wanting a directly comparable public price against auvik before starting a sales conversation with either vendor. Of those, an msp with high device density per client site wanting predictable flat pricing per collector rather than counting individual devices and an it integrator managing many small sites with few devices each, better served by per-device pricing than a flat collector fee are not what Eclipse Mosquitto is typically brought in for.
What can Domotz do that Eclipse Mosquitto cannot?
Domotz covers Device discovery and monitoring, Remote access without VPN, Two published pricing models, Automated alerting. Eclipse Mosquitto covers MQTT 5.0 support, Very small footprint, Bridging, WebSockets listener.

Answered from the vendors’ own pages

Domotz: Is pricing based on networks, sites or devices?

Devices. Domotz states explicitly there are no per-site, per-network or per-user charges.

Eclipse Mosquitto: Can Mosquitto be clustered?

No. It is a single process. High availability requires an external failover arrangement you build yourself.

Domotz: What is the difference between the two plans?

The Collector Plan is a flat $35/month per collector with full access to everything that collector monitors; the Managed Device Plan is $1.50/month per device, billed in bundles of ten.

Eclipse Mosquitto: What licence is it?

Eclipse Public License 2.0 alongside the Eclipse Distribution License, a weak copyleft rather than a permissive licence.

Domotz: Is there a free trial?

Yes, a 14-day free trial is offered.

Eclipse Mosquitto: How many clients can it handle?

A few thousand concurrent connections on ordinary hardware; beyond that, use a clustered broker.

Eclipse Mosquitto: Does it support MQTT 5?

Yes, along with 3.1.1 and 3.1.

Share

Related pages

Other head to heads