Can I migrate from Loriot to Datacake without their support team?

Yes. Migration is fully self-serve. You re-use the same DevEUI, JoinEUI/AppEUI and AppKey on Datacake's LNS, run both stacks in parallel during the cut-over, and decommission Loriot when ready.

Will I lose anything by leaving Loriot's Public Community tier?

Loriot's Public Community is fair-use limited. Datacake's free tier is not; production traffic is the default. So practically you gain throughput and feature scope (dashboards, rules) by moving.

How does Datacake handle Loriot's per-organisation tenant model?

Datacake offers workspace-level multi-tenancy with white-label support. You can mirror Loriot's organisational structure as Datacake workspaces, each with its own theming, custom domain and dashboards.

Can I keep my MQTT and webhook integrations from Loriot?

Datacake offers equivalent MQTTS and HTTPS webhook outputs. Endpoint URLs and field-name mappings will need to be updated, but the JSON payload format is similar enough that consumers usually need only minor adjustments.

Is Datacake's regional support a match for Loriot's coverage?

Yes: EU868, US915, AU915, AS923, IN865 and KR920 are all supported under LoRaWAN 1.0.x and 1.1, the same coverage Loriot offers for production deployments.

← Datacake LoRaWAN Network Server

Migration guide

Migrate from Loriot to Datacake's free LoRaWAN Network Server

A practical, no-firmware-re-flash migration path from Loriot to Datacake's managed LNS. Run both stacks in parallel during the cut-over so you never lose a device, then decommission the old server when you're ready.

Re-use the same DevEUI, JoinEUI/AppEUI and AppKey: no firmware re-flash
Cut over gateway-by-gateway with zero downtime
400+ device templates ready, with payload decoders included
Free LNS in every Datacake plan, no per-gateway fees

Create a free Datacake account Jump to the steps

Loriot 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	Loriot	Datacake
LNS pricing	PartialPer-tier pricing (Public Community, Pro, Business, Enterprise)	Free LNS in every plan, no per-gateway fee
Built-in dashboards		Template-driven dashboards
Built-in rules / alerting		Email, SMS, push, webhook
MQTT / Webhook outputs
Re-use existing devices (no re-flash)		Same DevEUI, JoinEUI/AppEUI and AppKey
On-prem / private deployment	Loriot Enterprise tier	Managed SaaS only
Multi-tenancy / white-label		Workspace-level tenant separation, white-label UI

Capabilities reflect the public product documentation of Loriot and Datacake at the time of writing. Loriot's tier scope evolves, so please cross-check feature scope on loriot.io.

Migration in 5 steps

A self-serve path from Loriot to Datacake. Re-use existing device keys, keep existing gateway hardware, run both stacks in parallel during the cut-over.

1
Create a free Datacake account
Sign up at app.datacake.de. Datacake's LoRaWAN Network Server is included free in every plan, so the migration costs nothing in commercial commitments up front.
2
Point your gateways at Datacake
In your gateway's packet-forwarder configuration (Semtech UDP or LoRa Basics Station), add Datacake's LNS endpoint. For zero-downtime cut-over, run Loriot in parallel where the gateway supports two backends, or migrate gateway-by-gateway during a maintenance window.
Compatibility:Datacake works with the same gateway hardware you operate on Loriot: RAK, Kerlink, Multitech, Tektelic and others.
3
Re-register your devices on Datacake
Add devices using the same DevEUI, JoinEUI/AppEUI and AppKey from your Loriot organisation. If the hardware is in Datacake's template catalog (which covers most popular models), applying the template auto-configures the payload decoder, dashboard and downlink hooks.
Bulk import:Datacake supports CSV bulk-import of device identifiers and keys, so re-registration scales cleanly to thousands of devices.
4
Verify uplinks on Datacake
Watch the Datacake device list for joins and uplinks. If a device hasn't joined yet, trigger a re-join from the device side. Decoded values should appear on the dashboard within seconds of the next uplink.
Sanity check:Compare uplink timestamps and decoded values against Loriot for several minutes per device. When they match, the device is fully migrated.
5
Cut over and decommission Loriot
Once devices are stable on Datacake, remove the Loriot endpoint from your gateways and decommission the Loriot organisation (or downgrade to a free tier for archival purposes). Re-point MQTT and webhook subscribers to Datacake equivalents.
Rollback:No firmware was changed. To roll back, re-point your gateway at Loriot and re-activate the existing Loriot device entries.

Still evaluating?

Compare Loriot vs Datacake side by side

Pricing, hosting model, integrations and where each platform wins, laid out in a single comparison table.

Read the Loriot comparison

Loriot migration FAQ

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.