Isovara Ecosystem
Isovara Ecosystem program

Build the device. We built the rest.

Isovara Cloud already runs monitoring businesses for operators who sell under their own brand. Certify your hardware and it joins them: enrolled with the code on its label, managed in every operator's portal, next to Isovara v3.

Apply to the program What certification means
Who gains

A market for makers, a catalog for operators, one app for customers

Device makers

A cloud you don't build

  • Enrollment, per-device credentials, broker accounts
  • Email and SMS alerts, 13 ready-made rules, charts, CSV
  • Customers, viewers, technicians, plans and billing
  • Operators who already sell monitoring, hosted or licensed
Operators

A wider catalog, one portal

  • Sensors Isovara v3 doesn't have, without a second platform
  • The same alerts, rules, groups, jobs and rollouts
  • Certified: published checklist, ten scenarios, 72 hours
  • The same plans, Stripe account and branding
Customers

One app they can trust

  • Added with the code on the label
  • A private connection with its own credentials
  • Signed updates that roll back if they fail
  • Safe to pass on: a reset erases its credentials
Your hardware, first class

Declare it once; every screen follows

  • Capabilities file: your sensor types, operating modes and optional hardware. Screens show only what your device has.
  • Device template: your device page's tabs and operations, from an OpenAPI document. No portal code to write.
  • Extra values: up to 32 per reading, usable in rules as extra.<name>; numeric values you mark get history and charts.
  • Your keys: sign firmware with your own offline Ed25519 key. Operators roll it out in stages, with SHA-256 checks and automatic rollback.
  • Brand-ready: support the brand template and operators sell your device under their name, from one signed image.
Admin panel, Device capabilities: each hardware platform with its sensor types and categories
Each platform registers a capabilities file. Here, the built-in legacy and Isovara v3 platforms.
Participation

Three levels

The mark belongs to a product, not a company. Fees in brackets are placeholders.

Developer

Build and test

You get

  • Hardware Developer Guide and OpenAPI documents
  • A staging tenant and a reserved platform ID
  • Factory and enrollment codes for test units
  • Technical support

You commit to

  • Testing only against staging installs
  • The NDA; no use of the mark
[program fee or free]
Certified

Sell through operators

You get

  • The Isovara Certified mark and a certificate number
  • A listing in the operator catalog
  • Production registration, hosted and licensed

You commit to

  • Staying conformant; recertifying on triggers
  • Answering security reports within [N] days
  • Publishing your extra fields
[certification fee per product]
Partner

Grow together

You get

  • Co-marketing and introductions to operators
  • Early access to protocol changes
  • A roadmap seat, priority lab slots, a named engineer

You commit to

  • An annual joint plan and references
[by agreement]
Certification

One mark, two classes

Isovara Certified seal, Native, Class A

Native · Class A

The HTTPS device API, then the device's own MQTT-over-TLS cloud channel. Live commands with acknowledgments, full configuration, remote console, signed cloud updates and brand pushes. Required for new designs that can hold a connection.

Reporting · Class B

The HTTPS device API only. Readings, settings in each reply and configuration by polling. For battery-powered, sleeping or very small devices.

AreaWe verifyWhy it matters
Identity and hardwareA device ID from hardware, printed on the label; a truthful hardware report; memory headroom; A/B firmware slotsCustomers add the right device; screens show only what is fitted
Enrollment and trustFactory and enrollment codes; refusals handled; trust bootstrap for private installs; no plain-HTTP cloud addressesOnly the rightful owner can claim a device
Cloud channelOnline and offline status; one report path; credential refresh; reconnect with backoffAccurate status and alerts; no reconnect storms
Messages and commandsPublished formats; acknowledgments within 2 seconds; no repeated actions; atomic configurationActions from the app happen once, as asked
UpdatesSigned images for its own platform only; progress reported; automatic rollbackA bad image never becomes the running one
SecurityNo secrets in reports, logs or crash dumps; admin password; sign-in lockout; setup timeoutCustomers' networks and accounts stay private

Plus ten test scenarios and a 72-hour run with readings every 15 minutes. Certification covers behavior with Isovara Cloud; electrical safety, radio approvals, environmental ratings, accuracy and warranty stay with the maker.

The path

From application to listing in seven steps

  1. Join

    Agreement, NDA, staging tenant, platform ID

  2. Register

    Capabilities file, device template, public signing key

  3. Self-test

    The checklist and the ten scenarios

  4. Submit

    Evidence, a signed release, sample units

  5. Lab review

    We rerun the scenarios; you fix and resubmit

  6. Certified

    Certificate number, the mark, a catalog listing

  7. Stay certified

    Signed releases; recertify on major changes and yearly
Admin panel, Device templates: each platform's template with its operations and OpenAPI document
Device management templates give each platform its own device page, built from an OpenAPI document.

A suspended listing never cuts off devices already in the field.

Questions makers ask

Before you apply

Do we have to use an ESP32?

No. Any microcontroller or embedded Linux device that meets the guide's minimums qualifies. A Native device must hold one TLS session and an MQTT client open with room to spare.

Where do our devices connect?

To whichever Isovara Cloud the operator runs: the hosted service or a licensed install on their own servers. Both run the same software.

Who signs our firmware?

You do, with your own offline key. You register only the public key; nobody else ever holds your private key.

Our device measures things Isovara doesn't know about.

Declare them in your capabilities file and report them as extra fields. Operators can chart them and write rules on them.

Can operators sell it under their own brand?

Yes, if your firmware supports the brand template and the brand commands. One signed image serves every brand.

Apply to the Isovara Ecosystem program

[Program contact: email, phone and web address to be added]