obniz
Platform Architecture

From hardware to solutions,
seamlessly connected.

obniz is a single platform built from six tightly integrated layers.

Hardware, OS, connectivity, cloud, and applications — all the way up to use-case solutions like temperature management, leak detection, and PLC remote control. Every layer follows the same design philosophy. Here we walk through each one and how the SDKs fit together.

Why obniz

From design to operations, one consistent IoT foundation

Hardware, firmware, cloud, security — domains that take years to build in-house. obniz has been refining all of them into a single platform for over a decade.

Patented
Zero

Firmware rewrites on the device

Our patented Firmwareless Technology lets you add or change features without ever touching the device firmware. On-site logic can be updated from the cloud as many times as you like, even after deployment — no need to recall devices, and no downtime.

ISO 27001 certified
Zero

Servers to operate yourself

TLS 1.2 encrypted communication, per-device public-key authentication, OTA updates, and connection monitoring are all built into the platform. obniz runs everything under ISO/IEC 27001 certification — there is nothing for you to provision or operate.

Track Record
40,000 +

obnizOS devices in production

Since development began in 2014, more than 40,000 cumulative devices have been deployed across 300+ companies. Temperature management, facility monitoring, PLC integration — the platform has been battle-tested for over eight years in real operations.

Multi-Network
4 types

Connectivity for any environment

LTE / LTE-M, NB-IoT, Wi-Fi, and Ethernet are all unified on a single platform. Pick the best option for the site — outdoor, mobile, closed network, or office — while the upper layers and your code stay exactly the same.

AI × Lua
1 / 100

Data traffic, slashed to a fraction

Lua Plugin lets you push decision, aggregation, and compression logic onto the device itself. With AI generating Lua code dynamically based on what is happening on-site and pushing it live, only the data you actually need gets sent — cutting traffic by tens to hundreds of times.

Layers in Detail

What each layer does — and the services tied to it

Where you start is up to you. Use the SaaS as-is, build a custom app on the SDK, or just embed the hardware into a product line — pick the entry point that fits.

02 · Application

Application

SaaS and custom apps that drive operations on the ground

Use a SaaS like obniz Now off the shelf, or build your own application with obniz.js / SDK. Either way, the same obniz Cloud sits underneath.

03 · Cloud Platform

obniz Cloud

The management backbone connecting devices and apps

Manage tens of thousands of devices through a unified API. Reach it via REST, GraphQL, or WebSocket, with device authentication and OS update delivery built in. Everything you need for IoT, in one place.

04 · Network

Connectivity

Connection options matched to each environment

LTE / LTE-M for outdoor and mobile deployments, Wi-Fi / Ethernet for offices and factories. All cloud communication is encrypted with TLS 1.2.

LTE / LTE-M / NB-IoT

Embedded SIM models supported

Wi-Fi

2.4GHz b/g/n, WPA3 / WPA2 Enterprise

Ethernet

Wired connection with static IP support

05 · Operating System

obnizOS

A cloud-connected OS running on the microcontroller (MCU)

A purpose-built embedded OS running on every obniz device. It handles connection recovery, key management, power control, and OTA updates, so application developers never have to think about this layer.

Open documentation

TLS 1.2

End-to-end encrypted communication

Public-key authentication

Per-device key management

OS updates

Automatic OTA upgrades

Auto recovery

Reconnect on disconnection

Power management

Sleep / wake control

Lua Script

Live-update lightweight intelligence without rebooting

Self-hosting

Connect to your own cloud instead of obniz Cloud

06 · Hardware

Hardware

A family of devices running obnizOS

Certified hardware running obnizOS. Pick the right device for the job — every layer above (OS / Cloud / App) stays the same regardless of which one you choose.

SDK & Integrations

The developer experience starts with obniz.js

The SDK is what bridges the application layer to the cloud. Choose the right one for the job — from the lightweight JavaScript SDK to the App SDK built for production-scale SaaS.

Quick Start

Talk to a device in five lines

Load obniz.js, supply an OBNIZ_ID and access_token, and you are connected. The same code runs in the browser and in Node.js. The access_token enforces authorization, blocking unauthorized connections.

obniz.js reference
connect.js
const obniz = new Obniz("OBNIZ_ID", {
  access_token: "token_xxx"
});

obniz.onconnect = async () => {
  const voltage = await obniz.ad0.getWait();
};

Let's design the right layers for your project, together.

SaaS off the shelf, a custom app on the SDK, or hardware embedded into your product line — we will help you put together the configuration that fits.