The technical answer to what this is underneath
Architecture
The product pages are written for the people who sign. This one is written for whoever has to run it, and says what the platform is made of, where the data sits, and what you take on if you host it yourself.
What is under it, and why it is that
Columnar storage for the measurements
Time-series and events land in ClickHouse, which reads over 10 billion rows per second in our setup and compresses industrial time-series around 100 times. That combination is what turns keeping full-resolution history into a storage decision rather than a retention argument.
A model for what the measurements mean
Assets, processes and the relationships between them are held as a model rather than as columns, so a new kind of relationship does not need a schema migration. Measurements attach to that model, which is what lets a query start from a pump instead of from a tag name.
One API, three SDKs, and an MCP server
Everything the console does goes through the same REST API, with SDKs for Java, Python and Rust over it. Agents reach the model through an MCP server rather than a bespoke integration, so what an agent can see is governed by the same rules as what a person can see.
What you are agreeing to operate
Self-hosting is real self-hosting. You run PostgreSQL, ClickHouse and the platform services, and upgrades and backups are yours. That is a genuine operational load, and it is the price of the code being yours under AGPL-3.0. If you would rather not carry it, we host it on hardware we own and operate.
Read it before you talk to anyone
The platform documentation covers deployment and operations. The SDK documentation covers writing code against it. Both are open, and neither asks for an email address first.