Event-Sourced Digital Twin Platform | Dweve Twin

Twin is an event-sourced digital twin platform with three clocks on every event, branching scenarios and self-hosted operation. Publishing in round nine.

What is Dweve Twin?

Dweve Twin is an event-sourced digital twin platform for physical and operational assets. Its append-only event log is the system of record; current and historical state are derived by replaying that history.

  • Every event carries event time, processing time and validity time, so Twin can distinguish when a change happened, when it arrived and when it should count.
  • Replay folds the ordered log to reconstruct a selected state without overwriting the history.
  • Twin runs on infrastructure the operator controls, from one machine to a cluster. Repository access is by request, and supplied source is offered under Apache-2.0 terms once access is granted.
  • Replay proves the Twin record, not an external side effect. A command that changes a device or calls another service needs a receipt from the target system before that outcome can be treated as confirmed.

Choose the audience that matches your question

The page contains three selectable readings of the same subject.

For consumers

Twin is a digital twin for the things people rely on: every change gets a line and the old lines remain.

For businesses

Twin is an event-sourced digital twin platform. It keeps the operational record on your estate so you can replay history and answer questions after a change. It is open source under Apache-2.0, and it publishes in the ninth round of Dweve's foundation release programme, with its documentation at docs.dweve.com the same day.

For engineers

An event-sourced digital twin where the log is the record and every current state is derived from history.