Platform

The whole chain, already fitted together

Individually, every piece is solvable. The cost is in making them fit. Hyperwisor is the integration, not just the parts.

Layers

What the platform covers

01

Firmware SDK

Provisioning, the realtime connection and reconnection are handled by the library. You call begin() and loop(), and push values to widgets by ID.

  • Turnkey SDKs for ESP32-class chips
  • Any board that speaks WebSocket, MQTT or HTTPS can connect
  • OTA-ready from the first build

02

Dashboard designer

A canvas of widgets bound to device data. Drop a widget, give it an ID, and it reads values and sends commands in both directions without a front-end build.

  • Gauges, charts, maps, 3D and camera widgets
  • Ships with the product for every user
  • Users can compose their own across devices they own

03

Product studio

The manufacturer workspace for a single product — grouped by the stage you're in rather than by feature.

  • Live device and user monitoring
  • Database and schema
  • Code generation and simulation

04

White-label apps

A branded web and mobile app for your device line, from one codebase, with screens generated per product rather than a generic widget grid.

  • Web and native from one source
  • Runs in mock mode before you connect anything
  • Single or multi-product catalogues

05

Marketplace and payments

List a design as a template, bundle it with hardware, or license it to other makers — and charge for actions inside a dashboard.

  • Templates, hardware bundles and manufacturer kits
  • Per-action charges
  • Revenue sharing and settlement

Neutrality

The primitive makes no assumptions

The platform tracks an identifier carrying a payload. What the device is — a thermostat, a soil sensor, a drone — is defined entirely by how the dashboard maps that payload. That neutrality is what lets one piece of infrastructure carry any vertical.

See the developer model

Build the product, not the platform

Create a product, wire up a board, and see it on a dashboard.