Nodrix

Nodrix

An open-source IoT backend that runs entirely on your own Cloudflare account, with no broker, server or third party in the middle.

Open SourceOtherWeb, Self-hosted, Cloudflare Workers, API
Nodrix screenshot

What is Nodrix?

Nodrix is a free, open-source IoT backend platform that deploys directly into your own Cloudflare account. It uses Cloudflare primitives such as Workers, Durable Objects, D1, R2 and KV to handle device telemetry, real-time dashboards, visual automations and a read API without any external broker or hosted server. Hardware sends JSON over HTTPS or WebSocket and variables create themselves on first sight, so there is no schema, MQTT broker or SDK to set up. The whole project is single-tenant and MIT licensed, meaning every deployment lives on your own infrastructure.

Key Features

Telemetry Protocol

Hardware POSTs JSON or opens a WebSocket and variables create themselves on first sight, with no schema, MQTT broker or SDK required.

Real-time Dashboards

Drop widgets onto a grid, bind them to variables and watch values update live over hibernating WebSockets.

Visual Automations

Build flows that fire on variable thresholds, a clock, sunrise or sunset, or events, then branch on conditions and set variables.

Read API

An edge-cached REST endpoint exposes latest state, recent time-series and variable listings behind a single bearer token.

MCP for AI

A built-in MCP server lets any AI client query projects, read state and, with an explicit toggle, drive automations.

Single-tenant Architecture

Every deployment lands in your own Cloudflare account on your own D1, R2 and Durable Objects.

One-click Deploy

Provisions D1, R2, KV and the Worker straight into your Cloudflare account with nothing to host or maintain.

Pros & Cons

Advantages

  • It is fully open source under the MIT licence with no cost and no vendor lock-in.
  • Everything runs on your own Cloudflare account, so you keep full ownership of your data and infrastructure.
  • Devices connect using plain HTTPS or WebSocket JSON, removing the need for an MQTT broker or a dedicated SDK.
  • Deployment is a one-click process that provisions all required Cloudflare resources automatically.
  • It includes dashboards, visual automations, a read API and MCP support in a single package.
  • The single-tenant model means each instance is isolated to one owner's account.

Limitations

  • It requires a Cloudflare account and familiarity with Cloudflare Workers, D1, R2 and KV, so it is aimed at developers rather than non-technical users.
  • As a self-hosted open-source project there is no managed hosting, official support tier or service-level agreement.
  • Being a single-tenant deployment, it is not designed for running multiple isolated customer tenants from one instance.
  • Features and maturity depend on community development, with a public roadmap rather than guaranteed releases.

Use Cases

Hobbyists and makers who want to collect and visualise data from microcontrollers and sensors on their own infrastructure.

Developers building IoT prototypes who want telemetry, dashboards and automations without standing up servers or brokers.

Teams already using Cloudflare who want an IoT backend that runs natively on Workers, D1, R2 and KV.

Engineers who need a self-hosted, data-sovereign alternative to commercial hosted IoT platforms.

AI tinkerers who want to query device state and drive automations through an MCP server.

Home automation projects that need threshold, schedule and sunrise/sunset based triggers.