IoTMan is the managed backend that treats every reading from your devices as an unchangeable, queryable event. No more stitching together databases and message queues. Just durable storage, live views, and standard APIs.
Real workspace with live sensor data. No account needed.
Devices send JSON over HTTP or MQTT. No SDK required. Every payload stored durably in PostgreSQL.
Retrieve sensor data through a clean REST API with time-based filtering. Subscribe to live updates via SSE. Receive signed HTTP POSTs on tag matches via webhooks.
Standard OAuth 2.1 flows for application and device access. Authorization Code + PKCE for user-facing apps, Client Credentials for devices and services.
JSONPath-based rules extract values from payloads and assign tags automatically. No code required.
Buildings, factories, public infrastructure, utilities — anywhere sensors are deployed and the data needs to be reliably collected and made accessible.
Designed for organisations without a dedicated software team to build and maintain a data backend — but that need one.
Your sensors are sending readings right now — but the data is trapped in device silos, discarded, or buried in CSV exports. You need a single, durable system of record for every reading.
You need to answer questions you haven't thought of yet. A compliance requirement, a tenant dispute, or an energy audit — you replay and analyze historical sensor data instantly, not just see the latest value.
No specialist software staff to build or maintain a custom solution.
Data must remain within EU jurisdiction — for compliance or sovereignty.
Configure sensors once to POST JSON to an endpoint. No SDK, no agent, no device management overhead.
No enterprise bloat, no months-long sales cycles, no seat licences for capabilities you will never need.
JSON over HTTP and MQTT for ingestion. JSONata and JSONPath for shaping views. OAuth 2.1 for authentication. Standard protocols, no proprietary SDK — your data, always accessible.
Sensors POST JSON to your endpoint over HTTP or MQTT. Each payload becomes an unchangeable event — no proprietary format, no lock-in.
Every event persisted forever in PostgreSQL. No data loss, no expiry by default. Manage and monitor from the dashboard.
Invite external users by email or register OAuth 2.1 client applications. Assign scoped access to live, materialized views — per user, per application, revocable at any time.
Authorized clients get REST snapshots or real-time SSE streams. No shared passwords, no workspace accounts — just a scoped token.
Invite external users by email and define exactly what they can access. No shared passwords, no workspace accounts — access is scoped and revocable.
Assign named permission scopes per user. A tenant sees only their building's data. A partner sees only what you authorised.
Third-party applications authenticate with Authorization Code + PKCE. M2M services use Client Credentials. Standard flows, no custom SDK.
End-users authenticate via a one-time email link. They are not IoTMan users — they only receive a scoped token for your application.
Start with a single curl. Save your sensor data. Views, dashboards, and integrations come later — when you need them.