We've just announced that we're working with Deutsche Telekom to connect their NB-IoT Satellite connectivity service into Blynk.
What that means: if your device connects through DT's network, the data flows straight into Blynk. Dashboards, mobile apps, alerts, OTA updates, fleet management. No middleware to build.
DT handles connectivity. Blynk handles the application layer. You build the product.
NB-IoT Satellite is where we're starting. A Nordic nRF9151 connects via Deutsche Telekom's IoT connectivity. The data lands in Blynk as structured telemetry, ready for dashboards, native mobile apps, automations, and fleet management.
But this is just the beginning. The goal is to let you connect all your connectivity into a single application layer with DT and Blynk. Whatever network your devices use, the application experience is the same.
We wrote about how NTN satellite connectivity works in a previous post. The short version: 3GPP extended NB-IoT to work over satellite links. Same modem, same firmware, same SIM. The satellite is just another cell tower, except it's in orbit.
The first reference setup uses a Nordic nRF9151 with a DT eSIM. Device data arrives through DT's Device-to-Cloud service and lands in Blynk via our Data Converters, which map the incoming payload to your device model automatically.
From there, it's standard Blynk: configure your dashboard, set up automations, deploy a branded mobile app, manage your fleet. The connectivity path is invisible to your application.
We're building out the developer experience now and will publish a step-by-step getting-started guide ahead of launch.
Agricultural sensors, remote infrastructure, asset trackers, environmental monitoring. The devices that are hardest to connect are usually the ones that need monitoring the most.
If you're building something that needs to work where there's no signal, we want to hear about it. We're launching later this summer and looking for early collaborators to build on this stack as it comes together. Reach out to our team.
.png)
