I am running ChirpStack on Kubernetes. Is migration to Datacake disruptive?

No. Datacake re-uses the same DevEUI, JoinEUI/AppEUI and AppKey, so devices do not need to be re-flashed. You can route gateways gateway-by-gateway, validate uplinks on Datacake, and decommission ChirpStack only when you are confident.

Does Datacake support all the same LoRaWAN spec versions as ChirpStack?

Datacake supports LoRaWAN 1.0.x and 1.1, including OTAA / ABP join, Class A / B / C, and the major regional parameter sets (EU868, US915, AU915, AS923, IN865, KR920), the same coverage as ChirpStack for production deployments.

What about my custom JS payload codecs from ChirpStack?

Most of the hardware that runs through ChirpStack is already covered by a Datacake template, so the codec is applied for you and you typically do not need to migrate it. For unusual hardware that genuinely requires a custom decoder, the JS code can be pasted into Datacake's per-device decoder field. The function signature is close enough to ChirpStack's codec runtime that minor adjustment is usually sufficient.

How does TCO compare between self-hosted ChirpStack and Datacake?

ChirpStack as software is free; the cost is hosting + database + redundancy + monitoring + on-call + expert hours. Datacake's all-in cost for a typical deployment under ~50,000 devices is usually lower than the fully-loaded TCO of running ChirpStack reliably yourself. Above that scale, the calculation depends on team and infrastructure choices.

Can I keep my existing MQTT / webhook integrations?

Yes. Datacake offers equivalent MQTTS and HTTPS webhook outputs. You will need to update endpoint URLs and field-name mappings, but the JSON payload format is similar enough that downstream consumers usually need only minor adjustment.

If I migrate to Datacake, can I still go back to ChirpStack later?

Yes. Because no firmware was changed, rolling back is always possible: re-point the gateway and re-add the device on ChirpStack with the same keys. Datacake does not lock device identity.

All comparisons

Datacake vs ChirpStack

Datacake: a managed alternative to running ChirpStack yourself

ChirpStack is an excellent open-source LoRaWAN Network Server. The catch is the operations: install, patch, scale, monitor, stay on top of LoRaWAN spec changes, secure the host. Datacake operates the equivalent stack as a managed service so your team focuses on the application, and the LNS is included free in every plan.

Free LNS in every Datacake plan: operations included, not extra
Built-in dashboards, rules, exports and white-label
400+ device templates with payload decoders
Lossless migration: re-use DevEUI / JoinEUI / AppKey, no firmware re-flash

Get started free See the LoRaWAN Network Server

ChirpStack vs Datacake at a glance

A side-by-side view of the parts of the LoRaWAN stack that change when you migrate. We've kept it factual. Both products have their strengths.

Capability	ChirpStack	Datacake
Hosting model	Self-hosted (Docker / Kubernetes / bare metal)	Managed SaaS, hosted by Datacake
Operating cost	PartialSoftware is free; you pay for hosting, monitoring, on-call, expertise	Free LNS in every plan; you pay only for device licenses
Patching, version upgrades, LoRaWAN spec changes	Your responsibility	Datacake operates and patches the stack continuously
Built-in dashboards	Bring your own (Grafana, Datacake, ThingsBoard)	Template-driven dashboards
Built-in rules / alerting		Email, SMS, push, webhook with escalation
Built-in payload decoders	PartialPer-device codec, manually maintained or via the device repo	400+ Datacake-maintained templates
Multi-region support		EU868, US915, AU915, AS923, IN865, KR920
MQTT / Webhook outputs
On-prem / air-gapped deployment	Strong fit for sovereign / regulated deployments	Managed SaaS only
Required ops expertise	Linux, Docker, Postgres, Redis, networking, observability	None: Datacake handles operations

Capabilities reflect the public ChirpStack documentation and Datacake at the time of writing. ChirpStack is an open-source project (originally LoRa Server). Your TCO depends on hosting choice, team expertise and uptime requirements.

Why Datacake

Where Datacake comes out ahead

No infrastructure to operate
Running ChirpStack means owning a Postgres + Redis + LNS service stack and keeping it patched against LoRaWAN spec updates. Datacake hides all of that. You focus on the application, not the network server.
Lower TCO for most teams
ChirpStack is free as software, but hosting, monitoring, on-call and expert hours are not. For most teams below ~50,000 devices, the all-in cost of operating ChirpStack reliably is higher than Datacake's per-device pricing.
Dashboards, rules and reporting included
ChirpStack ships only the network server and a basic application server. Datacake bundles dashboards, alerting, scheduled reporting, exports and white-label on the same account.
Lossless migration
Re-use the same DevEUI, JoinEUI and AppKey from your ChirpStack application: devices keep their flashed identity, and Datacake and ChirpStack run side by side until you finish the cut-over.

Honest take

When ChirpStack might be the better fit

Sovereign / air-gapped deployment is required
If regulation, government contract or critical-infrastructure requirements mandate that the LNS run inside your own network, ChirpStack is the natural answer. Datacake is a managed SaaS and does not offer on-prem.
Deep customisation of the LNS internals
ChirpStack is open source: you can fork it, modify scheduler logic, add custom application-server behaviour. Datacake exposes integrations but not the network-server source.
You already have an ops team running it well
If you have a dedicated team that already operates ChirpStack reliably, the marginal cost of adding more devices on it is low. Datacake's value proposition is mainly for teams that do not want that ops surface.

Ready to switch?

Migrate from ChirpStack to Datacake

No firmware re-flash. Re-use the same DevEUI, JoinEUI/AppEUI and AppKey. Run both stacks in parallel during the cut-over so you never lose a device.

Read the ChirpStack migration guide

Same DevEUI / JoinEUI / AppKey
Bring your existing gateway hardware
Parallel operation during cut-over
Self-serve: no vendor coordination

Datacake vs ChirpStack: frequently asked questions

Ready to get started?

Create your free account and start monitoring temperature, humidity and air quality in minutes, or book a demo to see how Datacake fits your use case.

Get Started Free Book a Demo

Get in touch

We typically reply within one business day.