Eclipse Ditto
Ranked #2 of 14 for digital twin platforms: Open source IoT middleware that models connected devices as digital twins.
A vendor never writes its own entry here, Eclipse Ditto included, although paid placement exists; see the disclosure for how links are marked.
Visit Eclipse Ditto See it in the digital twin platforms ranking
At a glance
| Headquarters | Not stated by the vendor |
|---|---|
| Deployment | Open source code |
| Best for | Engineering teams building their own twin layer over device data without licence fees |
| API | Eclipse Ditto mentions an API in the material we reviewed |
| Free plan | No free tier on record |
| Pricing model | Open source under EPL-2.0; the pages read list no prices and no hosting model |
What is Eclipse Ditto?
Eclipse Ditto is an open source framework for building digital twins of internet-connected devices. The project site calls it IoT middleware with an abstraction layer and says it is domain agnostic, so it can serve industrial, residential or agricultural setups. The main GitHub repository carries the Eclipse Public License 2.0.
Because the project is a framework rather than a product, the pages we read list no prices and no hosting model, and the footer shows the Eclipse Foundation logo without an address, so no country is stated. Ditto sits between devices and applications: it holds a twin for each device and exposes it through synchronous and asynchronous APIs. A team uses it when it wants to assemble its own stack and has engineers to run it.
Eclipse Ditto key features
- Device as a Service. The product page describes abstracting a physical device into a digital twin that applications talk to. Applications address the twin, so they do not depend on the device's own protocol.
- State management. Ditto separates reported, desired and current device state. That split lets an application record what it wants a device to do while still seeing what the device last reported.
- Resource-based access control. Access is enforced with a fine-grained, resource-based check. The pages we read do not describe how policies are authored, so that needs a look in the documentation.
- Connectivity options. External systems connect over AMQP 0.9.1, AMQP 1.0, Apache Kafka 2.x, HTTP webhooks, MQTT 3.1.1 and MQTT 5, each with payload mapping to translate message formats.
- Hono and Mosquitto links. Eclipse Hono and Eclipse Mosquitto are the named connections for linking devices to Ditto, so the project fits into the wider Eclipse IoT family.
- Synchronous and asynchronous APIs. Both API styles are described, with a link to the HTTP API documentation. A client can query a twin on demand or subscribe to changes.
- Domain-agnostic design. The site says the framework is not tied to an industry. The trade-off is that it ships no ready-made 3D views or industry templates according to the pages we read.
Who Eclipse Ditto suits
- IoT platform engineers. Build a device backend in which every device has a twin and applications use one API. Payload mapping helps when devices speak MQTT and back-office systems expect Kafka or HTTP.
- Product teams with connected hardware. Track reported versus desired state for equipment in the field, for example a setting an operator changed that a device has not confirmed yet.
- Research and education groups. Study twin architectures on an open codebase under EPL-2.0, where nothing is hidden behind a vendor console.
Getting started with Eclipse Ditto
The repository README lists the build requirements as JDK 25 or later and Apache Maven 3.9.x, so a developer can compile the project from source. The product page links to the HTTP API documentation and names Hono and Mosquitto as ways to connect devices.
The pages we read describe the framework rather than a managed signup, so there is no account to open: you run Ditto yourself and decide where it is hosted. A sensible first step is to connect one MQTT device, map its payload to a twin and query that twin over HTTP. Operating the service, including scaling and upgrades, falls to your own team.
Where Eclipse Ditto wins and where it does not
- Eclipse Ditto is a framework rather than a finished application.
- Marked in our records as open source.
- Marked in our records as EPL-2.0.
- Where it fits: Engineering teams building their own twin layer over device data without licence fees.
- Eclipse Ditto is tagged Device state in our records.
- The project site states neither a hosting model nor a country, leaving operations to the adopter.
- Less suited to: Facilities teams wanting a ready-made application with support.
- No dashboards, 3D views or analytics are described on the pages read, so those layers come from other products.
Our verdict on Eclipse Ditto
Eclipse Ditto is a framework rather than a finished application. It abstracts a connected device into a twin, keeps reported, desired and current state apart, and applies resource-level access checks.
Connections cover AMQP, Kafka, HTTP and MQTT with payload mapping, and the repository carries EPL-2.0. The pages read describe no dashboards or 3D views, and building it needs JDK 25 or later, so developers assemble the rest.
In our digital twin platforms ranking Eclipse Ditto stands at #2 of 14: Akenza sits directly above it and Twinzo directly below. Because challengers fill the first three places when a category has them, the number is a place on a list and not a rating.
The vendor states no country of establishment, so Eclipse Ditto is left out of the regional count for this list.
Eclipse Ditto pros and cons in practice
- The EPL-2.0 licence means the code is open to inspect and run.
- Six messaging protocols are covered, each with payload mapping.
- Reported, desired and current state are modelled separately.
- The domain-agnostic design suits mixed industrial, residential or agricultural projects.
- It is middleware, so dashboards, 3D views and analytics must come from other tools.
- Building from source needs JDK 25 or later and Maven 3.9.x.
- The pages state no hosting offer or support terms, so operations rest with your team.
- Policy authoring and scaling guidance are not described on the pages we read.
What Eclipse Ditto costs
In the catalogue: Open source under EPL-2.0; the pages read list no prices and no hosting model.
The pages we read list no prices. The main repository is published under the Eclipse Public License 2.0, shown by the licence badge in the README and by the link in the product page footer, so the software itself can be obtained and used under that licence. The product page states no hosting model, so the cost to a buyer is the infrastructure and the engineering time needed to run it, which the pages do not quantify. A company wanting a vendor to operate it would have to look at third parties, and nothing we read describes such an offer. Support arrangements are not described on the pages we read.
Source: the pricing material on eclipse.dev, as read for Best Digital Twin Platforms in 2026 and last reviewed on 15 November 2026.
Setup, support and exit with Eclipse Ditto
Ditto sits between devices and applications.
Its device-as-a-service function turns a device into a twin, and the state model separates what the device last reported from what an application wants.
Hono and Mosquitto are named as ways to reach devices, while AMQP 0.9.1, AMQP 1.0, Kafka 2.x, HTTP webhooks and MQTT 3.1.1 or 5 reach other systems.
Both synchronous and asynchronous APIs exist.
Expect to supply hosting, visualisation and support yourself.
Eclipse Ditto: data and security
The product page describes access control enforced with a fine-grained, resource-based check, which is the only security feature named. It lists no certifications, hosting regions or encryption statements. Because the project is a framework you deploy, data location and protection depend on the environment you choose. The country of the organisation is not stated on the pages we read.
What Eclipse Ditto connects to
Integrations the vendor names (9):
- Eclipse Hono
- Eclipse Mosquitto
- MQTT 3.1.1
- MQTT 5
- Apache Kafka 2.x
- AMQP 0.9.1
- AMQP 1.0
- HTTP webhooks
- HTTP API
Also in our records:
- Hono and Mosquitto are named as ways to reach devices, while AMQP 0.9.1, AMQP 1.0, Kafka 2.x, HTTP webhooks and MQTT 3.1.1 or 5 reach other systems.
- Both synchronous and asynchronous APIs exist.
Eclipse Ditto fact sheet
| Product | Eclipse Ditto |
|---|---|
| Vendor website | eclipse.dev |
| Price visibility | Model recorded, no figure |
| Rank there | #2 of 14 |
| Alternatives page | No dedicated page |
| Head-to-head pages | No comparison written |
| Primary guide | Best Digital Twin Platforms in 2026 |
| Source code | Open source, per our records |
| Catalogue tags | Open source, EPL-2.0, Device state |
| What we do not hold | headcount, funding and customer count |
| Headquarters | Not stated by the vendor |
Also ranked in
| Guide | Position |
|---|---|
| Best Digital Twin Platforms in 2026 | #2 of 14 |
Alternatives to Eclipse Ditto
We pick the closest products in the same guide by tags, price model and region.
- Akenza (#1 of 14): Not for: teams that need a modelled twin graph or a 3D scene. IoT data platform billed by device count with a monthly base fee.
- Twinzo (#3 of 14): Live 3D twin of plant logistics with forklift and material flow tracking.
- XMPro (#5 of 14): A good match for: Industrial operators wanting approvals and audit trails around automated decisions.
- Matterport (#9 of 14): Immersive 3D capture sold to real estate, facilities and construction teams. Watch out: plan names, prices and limits are missing from the plans page text, so the cost of scale is unknown.
- Ansys Twin Builder (#10 of 14): Simulation-based twin builder with hybrid analytics and exportable deployments. Watch out: the product page gives no prices, only a mention of flexible licensing.
Questions about Eclipse Ditto
9 answersWhere does Eclipse Ditto stand among digital twin platforms?
The digital twin platforms ranking has Eclipse Ditto at position 2 out of 14.
What else should I look at besides Eclipse Ditto?
The closest products in the same guide are Akenza, Twinzo, XMPro, Matterport and Ansys Twin Builder. Compare their entries before settling on Eclipse Ditto.
Is Eclipse Ditto a European company?
The vendor pages we reviewed state no country of establishment for Eclipse Ditto, so we do not give one.
Is Eclipse Ditto free, or what does it charge?
As recorded: Open source under EPL-2.0; the pages read list no prices and no hosting model. On free access, nothing is free to use, as far as we recorded.
Who should choose Eclipse Ditto?
Engineering teams building their own twin layer over device data without licence fees. It is a weaker match for the following: facilities teams wanting a ready-made application with support.
What licence does Ditto use?
The main GitHub repository shows the Eclipse Public License 2.0.
Does it cost anything?
The pages we read list no prices. Running it carries infrastructure and engineering costs that the pages do not estimate.
Which protocols can it connect to?
AMQP 0.9.1, AMQP 1.0, Apache Kafka 2.x, HTTP webhooks, MQTT 3.1.1 and MQTT 5, with payload mapping.
Where is the organisation based?
The pages we read do not state a country; the footer shows the Eclipse Foundation logo without an address.
Eclipse Ditto: sources
Read from the vendor’s own pages on 15 November 2026.
- eclipse.dev/ditto: Description, core functions, connections, protocols, APIs, footer
- github.com/eclipse-ditto/ditto: EPL-2.0 licence badge
- github.com/eclipse-ditto/ditto: Build requirements JDK 25 and Maven 3.9.x
- eclipse.dev/ditto: No prices, hosting model or address stated
How we rank
Four tests decide a position: how soon the product is useful, what the bill really becomes, how data leaves and who it suits. That puts Eclipse Ditto at #2 of 14. Method and commercial relationships are in our editorial process.