Skip to content
OnTwins

What is OnTwins?

OnTwins is a digital twin platform for physical sites. You describe what exists at your site, connect the data your equipment already produces, and compose screens that people can watch and act on — all in a browser.

It is built to stay light. There is nothing to install for the people who use it, the structure you build stays close to how your site is actually organized, and a single team can carry a site from an empty project to a live screen.

The problem it solves

Section titled “The problem it solves”

A working site already produces plenty of data. What it usually lacks is a single place where that data means something.

Readings arrive from separate systems, each with its own screens and its own name for the same piece of equipment. Knowing that T-204 is the temperature of the room at the far end of the second floor lives in the head of whoever installed it. Seeing the site as a whole — not one system at a time — means building something custom, and rebuilding it whenever the site changes.

Digital twin platforms exist to close that gap, but most of them ask for a great deal first: infrastructure to run, specialists to operate, and a modelling exercise finished before anything is visible.

OnTwins takes the opposite starting point. One place holds the structure of your site, the data bound to it, and the screens built on top. You describe only as much detail as you actually need, and you see the result as you go.

Who it is for

Section titled “Who it is for”

OnTwins is for organizations that run a physical site and want to understand and operate it from one place.

The work divides into four kinds — bringing the data in, describing the site and building its screens, watching the site and responding, and managing people and access — and OnTwins ships one app for each. One person may well do all four; the apps are separated by task, not by job title. The four apps introduces each one.

Developers are a first-class audience too: every app is built on the same public API, so anything our apps can do, yours can as well.

Tenants and projects

Section titled “Tenants and projects”

Two words carry most of the structure, and they mean something specific here.

A tenant is your organization inside OnTwins. It owns your people, your permissions, and everything built under it. Tenants do not see each other.

A project is one body of twin work: the structure you describe, the data flowing into it, and the screens built on top, with its own history. How much of the physical world a project covers is yours to decide — it might stand for a single building or for every site in a region. A tenant can hold several projects, and they stay independent of one another, so work in one never disturbs another.

Inside a project you work with entities — the digital twin of one real thing, a pump, a floor, a whole site. Entities are what data attaches to and what screens display. This documentation says entity throughout, since that is the word the API uses; twin means the same thing.

Where to go next

Section titled “Where to go next”