IoT Data Manager

Your sensor data,
collected and served.

IoTMan collects sensor data from your devices, stores it durably, and makes it accessible — to your teams through a dashboard, and to your applications through an API. No custom development required.

Real workspace with live sensor data. No account needed.

Building sensor
21.4 °C
Water meter
0.42 m³/h
Air quality
PM2.5: 14
MQTT gateway
Connected
Custom API
GET /readings/avg
WebSocket
/data/out/stream
OAuth scope
data:read
IoTMan
managed · hosted
What it does

Everything needed. Nothing extra.

Device ingestion

Devices send JSON over HTTP or MQTT. No SDK required. Every payload stored durably in PostgreSQL.

REST & WebSocket access

Retrieve sensor data through a clean REST API with time-based filtering. Subscribe to live updates via WebSocket.

OAuth 2.1

Standard OAuth 2.1 flows for application and device access. Authorization Code + PKCE for user-facing apps, Client Credentials for devices and services.

Automatic tagging

JSONPath-based rules extract values from payloads and assign tags automatically. No code required.

Who it is for

Organisations that operate sensors.

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.

Operates IoT infrastructure
Sensors, meters, or monitoring equipment already in the field.
Needs reliable data access
Specific teams or internal applications need access to operational data.
No in-house backend team
No specialist software staff to build or maintain a custom solution.
Requires EU data residency
Data must remain within EU jurisdiction — for compliance or sovereignty.
Scope

We do one thing well.

Your devices send data to us. We don't touch them.

Configure sensors once to POST JSON to an endpoint. No SDK, no agent, no device management overhead.

No features you'll never use.

No enterprise bloat, no months-long sales cycles, no seat licences for capabilities you will never need.

No vendor lock-in.

Built on Linux, PostgreSQL, and Rust — open-source foundations that belong to no single vendor.

How it works

Simple by design.

01

Devices send data

Configure sensors or gateways to POST JSON to your IoTMan endpoint over HTTP or MQTT. IoTMan authenticates the request and stores the payload.

02

Data is stored durably

Every payload is persisted in PostgreSQL. No data loss, no expiry by default, no proprietary format. Manage and monitor from the dashboard.

03

Grant access to clients and partners

Invite external users by email or register OAuth 2.1 client applications. Assign exactly what they can access — scoped per user, per application, revocable at any time.

04

They retrieve data with a token

Authorised clients authenticate via OAuth 2.1 and query a stable REST or WebSocket endpoint. No shared passwords, no workspace accounts required.

device → IoTMan
# Device sends a measurement
curl -X POST \
  https://iotman.io/data/:token \
  -H "Content-Type: application/json" \
  -d '{"sensor_id":"bldg-3","celsius":21.4}'

✓  200 OK — stored
application → Data Access API
# Application retrieves data
GET /data/out/:endpoint_id?limit=50&from=1710000000
  Authorization: Bearer <oauth_token>

{ "data": [...], "next_page": "..." }
End-user access

Share data with your clients.

Invite external users by email and define exactly what they can access. No shared passwords, no workspace accounts — access is scoped and revocable.

Invite by email, scoped to what they need
Assign named permission scopes per user. A tenant sees only their building's data. A partner sees only what you authorised.
OAuth 2.1 for apps and services
Third-party applications authenticate with Authorization Code + PKCE. M2M services use Client Credentials. Standard flows, no custom SDK.
No workspace membership required
End-users authenticate via a one-time email link. They are not IoTMan users — they only receive a scoped token for your application.
End-user access — workspace: Building A
alice@tenant-corp.com
sensor:readbuilding-a:view
bob@facility-mgmt.io
sensor:readsensor:export
api-client@partner.eu
sensor:read
✓ Access revocable per scope, per user

Ready to connect your first device?

Free tier available. No credit card required.

Get startedSee pricing