Introducing IotMan: IoT Data, Direct to the Web

Most IoT platforms are built for engineers managing fleets of devices. IotMan is built for a different goal: getting IoT data in front of end users, on the web, with as little friction as possible.

The Problem

You have a sensor. You want a website that shows its data in real time. The sensor part is easy. The website part is easy too, coding assistants have made building polished frontends almost trivial. The painful part is everything in between: persistence, authentication, CORS, real-time updates, public endpoints.

That gap is what IotMan fills.

What IotMan Provides

IotMan is a Backend-as-a-Service focused on IoT data. It handles:

• Data persistence: time-series storage for device readings
• REST API: query historical data from any HTTP client
• WebSockets: push live updates to connected browsers
• OAuth provider: authentication for protected resources
• CORS handling: serve data directly to browser-based apps

The result: your IoT application can be a fully static page. No backend to deploy, no server to maintain.

A Concrete Example

wind-venice.pages.dev is a wind data dashboard for Venice, built as a static page hosted on Cloudflare. A Cloudflare cron worker runs every five minutes, fetches current wind data from a public weather endpoint, and forwards it to IotMan. This is the IoT device in this setup: ephemeral data from an external source, ingested on a schedule. IotMan persists each reading and exposes it over a public endpoint. The page connects over WebSocket and updates in real time.

The frontend is a static file. The backend is IotMan. That's it.

The Bet

Building a static page that looks great is no longer the hard part. Any coding assistant can scaffold one in minutes. The hard part is wiring it to real-world data reliably and securely.

That's the problem IotMan is designed to solve.