Is Datacake a self-serve product or do I need to talk to sales first?

Datacake is fully self-serve. There is a free tier with included device licenses for production traffic, and per-device pricing is published on the pricing page. You can sign up, register devices, build dashboards and ship without a sales conversation.

I run Losant on top of TTN or TTS today. What does the migration look like?

The TTN / TTS application becomes optional once Datacake takes over. Datacake's bundled LoRaWAN Network Server accepts the device under the same DevEUI, JoinEUI/AppEUI and AppKey: no firmware re-flash, no on-site visit. Operationally the gateway is re-pointed to Datacake, the device is registered with the existing keys, and the Losant workflow that used to parse the TTN webhook is replaced by a Datacake template (or a small rule, where logic is genuinely custom).

Does Datacake have an equivalent to Losant Experiences?

Not directly. Datacake offers workspace-level white-label with custom domain, theming and per-workspace branding, enough to ship a branded customer portal that surfaces dashboards and alerts. If you need a fully bespoke web application on top of the platform data, the standard pattern is to consume the Datacake API from your own front-end.

What about my Losant workflows?

Datacake's rule engine covers most threshold, transformation and notification scenarios. For complex multi-step workflows, the typical pattern after migration is to keep the most platform-shaped logic on Datacake (rules, alerts, scheduled reports) and move arbitrary branching logic to a small downstream service called via webhook.

How does pricing compare between Losant and Datacake?

Losant's commercial tiers are quotation-based, so a precise side-by-side requires a quote on their side. Datacake publishes per-device licenses on the pricing page and the LNS is free at every tier, so you can model your projected fleet cost end-to-end before any sales conversation.

Will my non-LoRaWAN devices that currently publish into Losant over MQTT still work?

Yes. Datacake exposes per-device MQTTS and HTTPS ingestion endpoints that accept the same payload shape Losant accepts today. The migration is typically a broker hostname swap and a credential rotation pushed via OTA or a config update. The device firmware does not need a code change. Inbound webhooks to your existing systems are configured per Datacake rule, mirroring the way Losant outputs route through workflows.

All comparisons

Datacake vs Losant

Datacake: a transparent, self-serve alternative to Losant with a free LoRaWAN Network Server

Losant is a US-based enterprise IoT platform with a strong workflow engine and an end-user web-app builder ('Experiences'). Pricing and onboarding are quotation-based. Datacake is self-serve from day one: public per-device licenses, a free starter tier, a bundled LoRaWAN Network Server and 400+ ready-to-use device templates, so you can evaluate, deploy and budget without a sales conversation.

Self-serve: free starter tier and public per-device pricing
Free, bundled LoRaWAN Network Server in every plan
400+ device templates with payload decoders out of the box
MQTT and HTTPS ingestion for non-LoRaWAN devices

Get started free See the Datacake IoT platform

Losant vs Datacake at a glance

A side-by-side view of the platform capabilities that matter when you evaluate. We've kept it factual. Both products have their strengths.

Capability	Losant	Datacake
Hosted IoT platform	Managed SaaS	Managed SaaS hosted in the EU
Bundled LoRaWAN Network Server	Ingests LoRaWAN via TTN / TTS / ChirpStack as upstream	Native LNS, included free in every plan
Public, self-serve pricing	Quotation-based: sales conversation to start	Per-device licenses published on the pricing page
Free starter tier	PartialDeveloper Sandbox available with usage limits	Free tier with included device licenses for production use
Device template catalog with payload decoders	PartialBring-your-own decoder via workflows; no curated LoRaWAN template catalog	400+ Datacake-maintained templates plus the LoRa Alliance / TTN device repo
Built-in dashboards	Widget-based dashboard editor	Template-driven dashboards per device type, with manual editing
Workflow / automation engine	Visual workflow editor with deep conditional logic	Rules with email, SMS, push and webhook actions plus escalation
End-user web-app builder ('Experiences')	Build branded end-user portals on top of platform data	PartialWorkspace-level white-label with custom domain; not a generic web-app builder
Multi-protocol ingestion (MQTT / HTTPS / LoRaWAN)	MQTT and HTTPS; LoRaWAN via upstream LNS	MQTTS, HTTPS and native LoRaWAN

Capabilities reflect the public product documentation of Losant and Datacake at the time of writing. Both products evolve quickly, so please cross-check current pricing and feature scope on losant.com and datacake.co before purchase.

Why Datacake

Where Datacake comes out ahead

Sign up and ship: no quotation gate
Losant is a quotation-driven enterprise sale: pricing, tier scope and platform limits are negotiated per contract. Datacake publishes per-device licenses on the pricing page and offers a free tier you can run production traffic on, so an engineer can prove the architecture end-to-end before procurement gets involved.
LoRaWAN included, not a separate workflow
On Losant a LoRaWAN device flows in through an external network server (TTN, TTS, ChirpStack) and a custom workflow that parses the uplink. Datacake ships the LNS in the same product, so registering a LoRaWAN device is a one-screen action: pick the template, paste the keys, the dashboard appears.
Templates replace the day-one workflow build
Onboarding a new device type on Losant typically starts with a payload-parsing workflow and a hand-built dashboard. Datacake's 400+ device templates ship the decoder, the dashboard and the downlink hooks pre-wired for popular hardware. The workflow build happens only where genuinely custom logic is needed.
Migration without a re-keying event
LoRaWAN devices that feed Losant today via a TTN or TTS application keep their identity on Datacake: same DevEUI, JoinEUI/AppEUI and AppKey, no firmware re-flash. The Losant device-and-workflow pair is replaced by a Datacake template plus rules; the upstream LNS account is no longer needed.

Honest take

When Losant might be the better fit

End-user web apps ('Experiences') are central to your product
Losant's Experiences module lets you build branded end-user portals on top of platform data, a real differentiator if your business model includes shipping a customer-facing application alongside the IoT backend. Datacake offers workspace-level white-label, not a generic web-app builder.
Deep workflow logic with arbitrary branching is required
Losant's visual workflow editor is purpose-built for complex multi-step pipelines with conditionals, sub-workflows and timers. If your application logic is genuinely workflow-shaped, that surface is a real strength.
Enterprise procurement requires SAML / SSO and quotation contracts
Losant's enterprise tiers are built around SAML-based SSO, custom contracts and quotation-driven procurement, natural for large organisations whose vendor onboarding requires that shape. Datacake offers SSO on higher tiers but is self-serve at heart.

Datacake vs Losant: 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.