ODevice
Build customer-facing IoT apps from Python without writing frontend code.
IoT teams have the data — but answering "how do customers actually use this?" costs a whole frontend team.
IoT projects usually have devices and backends ready, but all of them hit the same question: "the data arrives — how do customers actually use it?" System integrators rebuild dashboard/control UIs on every project; small hardware companies have no iOS/Android/frontend team at all. The customer-facing app that should be the selling point becomes the most expensive cost of the project.
- Rebuilding dashboard/control UIs every project despite identical patterns
- Integrators lack frontend/mobile skills — work doesn't end at the backend
- Hardware companies need iOS + Android + Web teams just to sell one piece of hardware
- Hardcoded UIs require redeployment whenever schema or devices change
- Realtime control — commands, schedules, automation — is complex to build every time
- Surveying Smart Farm, Pump, Cold Storage and Energy projects revealed ~16 repeating widget patterns — the origin of Dynamic Widgets.
- Integrators use diverse stacks (ESP32, STM32, MQTT, Modbus) but customer UIs need the same thing: monitor + control + alert.
- Python is the common denominator of the IoT/embedded world — a Python-first SDK lowers the adoption barrier the most.
- A shared runtime across web/mobile reduces maintenance surface to a single set.
Canonical Device Schema
Every device maps into one schema, letting the runtime render UI without knowing specific device types.
Generic Runtime over generated code
The runtime reads schema and renders live — change the schema and the UI follows immediately, no frontend rebuild.
Shared Ionic Vue runtime (Web + Capacitor)
Web and mobile share one UI engine — new features land on both platforms simultaneously.
FastAPI + WebSocket backbone
Realtime telemetry and commands are first-class from day one — not bolted on later.
16 Dynamic Widgets
Cover patterns proven in real field projects instead of a generic-everything toolkit that's hard to use.
Backend / SDK
Web
Mobile
- MVP RuntimeWeb + Mobile from a single schema
- Python SDKDefine devices, properties, commands
- 16 Dynamic WidgetsField-tested patterns
- Public deploymentPlanned — no public URL yet
Public deployment + documentation site
Open a demo instance with docs so developers can connect a real backend within 10 minutes.
Widget ecosystem & plugin API
Expose the widget API so the community can extend beyond the 16 base widgets.
Managed hosting runtime
A hosted, pay-per-device ODevice runtime for integrators who don't want to operate infrastructure.
Vertical templates
Ready-made templates per vertical — farm, energy, cold storage — cutting time-to-demo to minutes.