Everything between a working device and a paying customer

is undifferentiated infrastructure. Hyperwisor is that infrastructure — firmware to dashboard to app to storefront — so hardware teams can spend their time on the hardware.

Start building Read the docs

Firmware

device.updateWidget(
  targetId,
  "tempGauge",
  27.4
);

value

Dashboard widget

tempGauge

27.4°C

Command handler

device.setUserCommandHandler(
  [](JsonObject &msg) {
    // drive a GPIO, toggle a relay…
  }
);

command

Dashboard widget

pumpSwitch

Pump

One idea holds the platform together: firmware and widgets share a widget ID. Values flow up, commands flow down.

The integration tax

A shippable product needs all of this

Every row is weeks of work and a permanent maintenance liability. None of it is what makes your product good.

Layer

Build it yourself

Here

Device connectivity

Provisioning UI, a realtime server, reconnection, heartbeats

OTA updates

Signed firmware pipeline, partitioning, rollback

Dashboard

A web app, live data binding, a widget library, theming

Database

Schema, storage, per-user access rules

Accounts & onboarding

Auth, device-to-user linking, QR provisioning

Mobile app

A branded iOS/Android app, store submissions, updates

Distribution

A storefront, licensing, order and fulfilment tracking

Payments

A gateway, revenue splitting, payouts, tax

Core concepts

Four ideas, and the rest follows

One product design becomes many physical devices. Each device belongs to a user. Each user sees a dashboard. The platform makes no assumption about what the hardware actually is.

Product

The design, not the object. Commands, database schema, dashboard and firmware bundled into one reusable template.

Device

One physical unit running that product's firmware. It emits values and receives commands — nothing more is asked of it.

User

Owns one or more devices, onboarded by scanning a code. Monitors and controls them through the dashboard that shipped with the product.

Dashboard

A canvas of widgets bound to device data. Ships with the product, or gets built by a user across everything they own.

Product studio

A workspace per product

Grouped by the stage you're actually in, from first sketch to settled revenue.

Monitor

Live device status, database, users, rules, quotas, revenue and command flow — for one product, in one place.

Design

The dashboard designer. Build the interface your users get, bind it to device data, publish without an app release.

Develop

Code generator, a live device simulator, server-side backend processes, API commands, keys and a circuit builder.

Test

Exercise API commands and device responses before anything reaches a customer's hands.

Deploy

QR distribution, voice assistant integrations, firmware versions and OTA rollout.

Earn

List the product, license the design, charge for actions, and track what settles back to you.

Dashboard designer

Build the screen, not the front end

Drag a widget onto the canvas, bind it to a widget ID, and it's live in both directions. A thermostat, a soil sensor and a drone run the same loop — only the IDs and payloads differ.

See the platform

GaugeChartSwitchSliderJoystickMapHeatmap3D viewerVirtual twinWebRTC cameraCompassAttitudeSpectral graphVector plotterMission planning mapTableFormDatabase formCountdown timerColour pickerText to speechVoice to textVideo playerPDF exportPaymentScheduleRuleDynamic repeaterIndicatorStatusLabelMenuand more

The business layer

Most tooling stops at "connected"

This one keeps going to sold and earning. Build the primitive once, and let it carry any product in any vertical — the shape payments and commerce platforms already proved.

Marketplace

Sell a design as a template, bundle it with hardware, or license it to other makers as a kit.

White-label apps

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

Payments built in

Charge for an action inside a dashboard, split revenue, and let settlement be handled.

You keep

Your firmwareYour customersYour product

Hardware

Bring the board you already chose

Turnkey firmware SDKs ship for ESP32-class chips, and board support keeps widening. Underneath, devices speak standard protocols — so anything that can hold a WebSocket, MQTT or HTTPS connection can already talk to the platform.

WebSocket

MQTT

HTTPS

When this isn't the right tool

Worth knowing before you invest, rather than after.

You must own the entire stack on your own metal for regulatory or contractual reasons.

It's a one-off internal gadget with no users and no product ambitions.

It's an ultra-low-level or hard-real-time control loop that belongs in firmware regardless of platform.

If none of those apply, the maths favours building here.

Spend the next few days on your product

Rather than the next few months on infrastructure.

Create your first product Talk to us