Softwr

Developer Tools · head to head

Atlantis vs Eclipse Mosquitto

Atlantis logo

Atlantis

Developer Tools

Runs Terraform plan and apply from pull request comments, self-hosted and free

From
Free
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

  • Each has a real cost: Atlantis there is no company, no service level agreement and no paid support at any price, and the six maintainers are volunteers with day jobs, which some risk committees will not accept for a component holding production cloud credentials.; 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: Atlantis covers Pull request plans, Eclipse Mosquitto covers MQTT 5.0 support.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

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

Attributes where Atlantis and Eclipse Mosquitto differ
AttributeAtlantisEclipse Mosquitto
PlatformsLinux, Docker, Kubernetes, Self-hostedLinux, Windows, macOS, Docker
CategoryDeveloper ToolsNetworking

Identical on both: starting price (Free), pricing model (Open source, no licence fee), free tier (Yes), user rating (Not yet rated).

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 Atlantis

  • Pull request plans
  • Comment driven apply
  • Workspace locking
  • Policy checking
  • Multi-platform webhooks
  • Custom workflows

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.

Atlantis

  • Making Terraform review meaningful by putting the actual plan output in front of the approvernot Eclipse Mosquitto
  • Removing local applies and the credential sprawl that comes with every engineer holding production keysnot Eclipse Mosquitto
  • Getting pull request driven infrastructure without paying a per-user subscription for a hosted platformnot Eclipse Mosquitto
  • Enforcing Conftest policies as a blocking check before an apply can runnot Eclipse Mosquitto

Eclipse Mosquitto

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

Where each one falls short

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

Atlantis

  • There is no company, no service level agreement and no paid support at any price, and the six maintainers are volunteers with day jobs, which some risk committees will not accept for a component holding production cloud credentials.
  • The security surface is inherently sharp, because it is an internet-reachable webhook endpoint that executes applies with privileged credentials, gated by pull request comment authorisation that is coarse next to a real policy engine.
  • It is stateful, holding a working directory and lock database on local disk, so high availability and horizontal scaling are awkward and you own upgrades, webhook plumbing, secret rotation and the host itself.
  • It lacks the features that distinguish the commercial alternatives, with no native drift detection, no cost estimation, no managed state interface and no policy engine beyond the Conftest integration.
  • Terragrunt and monorepo layouts are not first-class, requiring hand-written custom workflows and repository configuration that becomes a growing maintenance burden as the number of repositories increases.

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

Atlantis

Free
  • AtlantisFree
    • Apache-2.0, no usage limits and no seat count
    • No commercial edition and no paid support tier
    • Community support through GitHub and the CNCF Slack channel

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 Atlantis if

  • You need pull request plans.
  • You want to start without paying.
  • You work on Linux, Docker, Kubernetes, Self-hosted.
  • You also want comment driven apply.

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 Atlantis or Eclipse Mosquitto better?
Neither clearly leads. Atlantis starts at Free and Eclipse Mosquitto at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Atlantis or Eclipse Mosquitto?
Atlantis starts at Free and Eclipse Mosquitto at Free.
Does Atlantis or Eclipse Mosquitto run on more platforms?
Atlantis runs on Linux, Docker, Kubernetes, Self-hosted. Eclipse Mosquitto runs on Linux, Windows, macOS, Docker.
Can I use Atlantis for free?
Both have a free tier, so you can try either at no cost before committing.
What is Atlantis best used for?
Atlantis is most often used for making terraform review meaningful by putting the actual plan output in front of the approver, removing local applies and the credential sprawl that comes with every engineer holding production keys, getting pull request driven infrastructure without paying a per-user subscription for a hosted platform, enforcing conftest policies as a blocking check before an apply can run. Of those, making terraform review meaningful by putting the actual plan output in front of the approver and removing local applies and the credential sprawl that comes with every engineer holding production keys are not what Eclipse Mosquitto is typically brought in for.
What can Atlantis do that Eclipse Mosquitto cannot?
Atlantis covers Pull request plans, Comment driven apply, Workspace locking, Policy checking. Eclipse Mosquitto covers MQTT 5.0 support, Very small footprint, Bridging, WebSockets listener.

Answered from the vendors’ own pages

Atlantis: Is there a company behind Atlantis?

No. It runs as a series of LF Projects under the Linux Foundation and is maintained by volunteers. There is no vendor to buy support from and no service level agreement.

Eclipse Mosquitto: Can Mosquitto be clustered?

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

Atlantis: Is it a CNCF project?

No. It uses a channel in the CNCF Slack, which is often misread as membership, but the project sits under LF Projects rather than the CNCF.

Eclipse Mosquitto: What licence is it?

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

Atlantis: Does it work with OpenTofu?

Yes, there is a dedicated integration guide alongside Terraform, and it also has configuration for working with hosted Terraform backends.

Eclipse Mosquitto: How many clients can it handle?

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

Atlantis: What does it not do that a paid platform does?

Drift detection, cost estimation, a managed state and run interface, and a real policy engine. Atlantis does pull request plan and apply well and stops there.

Eclipse Mosquitto: Does it support MQTT 5?

Yes, along with 3.1.1 and 3.1.

Share

Related pages

Other head to heads