People searching for a Datacake alternative are usually weighing one thing against its strengths: per-device pricing as a fleet grows. Datacake is a slick low-code platform, but the bill scales with devices and your data lives on its cloud. nodrix is the opposite trade — it’s open-source (MIT) and you deploy it to your own Cloudflare account in one click, with no per-device license and every reading in your own tenancy.
This is an honest comparison, including where Datacake is the better pick.
What Datacake gets right
Datacake nails low-code. The dashboard builder is fast, device templates make onboarding hardware easy, and the LoRaWAN / The Things Network integration is genuinely turnkey — for LPWAN sensor fleets that’s a big head start. It also offers white-labeling and a rule engine, so for a reseller or a client deployment it’s a capable, polished product you don’t have to assemble.
What sends people looking is the cost model and ownership: billing scales by device, and your telemetry sits on Datacake’s infrastructure rather than your own.
Datacake vs nodrix, honestly
| Datacake | nodrix | |
|---|---|---|
| Model | Low-code hosted SaaS | Open-source; you deploy it to your own Cloudflare |
| Where data lives | Datacake’s cloud | Your Cloudflare account (single-tenant) |
| Pricing | Per device | No license cost; you pay Cloudflare for usage |
| Open source | No | MIT, full stack |
| LoRaWAN / TTN | Turnkey integration | Via gateway/network-server webhook to /v1/telemetry |
| Dashboards | Low-code builder | Drag-and-drop, embeddable Web Components |
| Rules / automation | Rule engine | Visual trigger → condition → action at the edge |
| Device connection | HTTP / MQTT / LoRaWAN | Plain HTTPS + WebSocket, no SDK |
| Data access | API | Read API: latest state + time-series behind one token |
When Datacake is the better choice
- Your project is LoRaWAN-first and you want turnkey TTN integration and device templates.
- You need white-labeling and a low-code builder for client or reseller deployments.
- Per-device pricing is fine for your fleet size and you’d rather not own the stack.
If that’s you, Datacake is a strong, purpose-built answer.
When nodrix fits better
- You want to drop per-device pricing for costs that track actual Cloudflare usage.
- You want open source and ownership — your telemetry in your account, not a third-party cloud.
- Your devices speak plain HTTPS/WebSocket (or forward LoRaWAN payloads via webhook) and you don’t want a vendor SDK.
- You want a read API for Grafana or your own app, plus edge automations you fully control.
Moving a device across
If your hardware already POSTs to Datacake’s HTTP endpoint, repoint it at nodrix — each metric becomes a variable automatically:
// HTTPS POST https://nodrix.you.workers.dev/v1/telemetry
// Authorization: Bearer tok_your_project_token
// { "metrics": { "temperature": 23.4, "soil": 38 } } -> 204For LoRaWAN, set your network server’s HTTP integration (the webhook that fires on uplink) to send
the decoded payload to the same /v1/telemetry endpoint. Commands flow back via GET /v1/control
or the control WebSocket — the full firmware is in
Connect an ESP32 over HTTPS.
The bottom line
If LoRaWAN and low-code white-labeling are the job, Datacake is a fine tool. But if per-device pricing is the friction — or you want open source, ownership, and a usage-based cost model — deploy nodrix to a Cloudflare account, point a device (or a network-server webhook) at it, and own the stack end to end.