A distributed IoT database platform that turns PostgreSQL into a managed, multi-tenant cloud for industrial time-series and object data.
Real PostgreSQL under the hood. Every instance is a real Postgres database. You get the reliability, query power, and ecosystem of PostgreSQL — without managing schemas, roles, or migrations yourself.
Distributed by design. Deploy across multiple hosts. Each node runs independently with its own API and Instance Manager, while the central Database Manager keeps everything in sync. A node failure doesn't take down other nodes.
Fine-grained security. Permissions cascade from instance → project → object structure → individual object. Separate permission sets for users and devices. API keys with optional permission restrictions. Full audit trail of every change.
Flexible data modeling. Define object structures and data tables through a GUI or templates. Columns are physically generated in PostgreSQL with enforced types, constraints, regex validation, min/max limits, and unique combinations. Localization built in.
Multiple access paths. JSON-RPC API, RexArcView graphs, Grafana, Telegraf bridge, direct DB access via assigned roles — or future protocols like MQTT and OPC UA.
Templates for consistency. Enforce structure standards across projects. Templates lock down required columns, data types, and flags while still allowing customization where needed.
| I want to… | Start here |
|---|---|
| Browse data, learn the basics | Getting Started → Common Tasks |
| Design object structures & data tables | Creating Tables → Templates |
| Manage an instance (users, groups, permissions) | Instance Overview → Permissions |
| Administer the platform (hosts, services, clients) | Administration → Admin Permissions |
| Deploy & maintain the system | System & Deployment → Installation |
| Integrate via API | API Overview → JSON-RPC (Postman) |
| Bridge data from REXYGEN / Telegraf | REX IoT Telegraf |
| Concept | What it is |
|---|---|
| Database Manager (DBM) | Central admin app. Manages hosts, users, clients, services, synchronization. |
| Host | A node running catalog DB + Instance Manager + IoT API. |
| Instance | An independent PostgreSQL database on a host. Contains projects, users, data. |
| Project | Organizational unit (PG schema) holding object structures, data tables, objects, and data. |
| Object Structure (OT) | Defines columns of an object table. Once generated, objects can be inserted. |
| Data Table (DT) | Defines columns for data records (typically time-series), attached to an OT. |
| Object | A row in a generated OT. Can have child objects, a data table, and per-object permissions. |
| Data | Rows in an object's data table — typically time-series measurements. |
| Individual | A user or device — the entity that owns API keys and accumulates permissions. |
| Role | A user profile or a group. Permissions are assigned to roles, not directly to individuals. |
| Template | A versioned blueprint that pre-defines required columns and constraints for OT/DT. |
| Client Interface | An external program (service, driver, script) that accesses instances via catalog API. |
| Service | A host-bound runtime of a client — JSON-RPC API, RexArcView, MQTT, etc. |