Ship firmware to every camera, safely.
Publish signed, encrypted firmware releases, roll them out to your devices in stages, watch your fleet check in, and get alerted when a security vulnerability is found in software your devices run.
From the command line
CLIEverything the dashboard does is a CLI verb, so a release can ship from your CI pipeline.
pip install openmv-ota git clone https://github.com/openmv/openmv git -C openmv submodule update --init --depth=1 git -C openmv/lib/micropython submodule update --init --depth=1
One package carries the project tools, the builder, the flasher and the client. Clone OpenMV's firmware source next to it, and run every later command from this same folder.
openmv-ota project new my-product -f openmv -b OPENMV_N6 --ota --install-sdk openmv-ota client login openmv-ota project keys desk create bench-1 my-product openmv-ota project keys desk push my-product
Generates your signing keys and, the first time, installs the OpenMV SDK. Then put your organization's account_id in the [product] section of my-product/openmv-ota.toml: Getting started shows yours once you sign in. Log in with one of your organization's API tokens. The two desk commands make this computer a desk: its key signs the record that registers each camera you flash, and the cloud accepts registrations only from desks it knows.
openmv-ota build firmware my-product -b OPENMV_N6 openmv-ota build factory-romfs my-product -b OPENMV_N6
The firmware that boots the camera, and the partition image written at manufacture.
openmv-ota flash factory my-product -b OPENMV_N6 openmv-ota client release publish my-product -b OPENMV_N6 -o my-product/build/factory
Write the camera over USB: as you are logged in, that also claims it for your organization. Then publish those same bytes so later releases can go out as small patches against them.
openmv-ota build ota-romfs my-product -b OPENMV_N6 openmv-ota client release publish my-product -b OPENMV_N6 --percent 100
Raise app_version in my-product/app/settings.json, then build the update and offer it to every camera. A smaller --percent rolls it out in stages.
What you get
Docs-
Signed and encrypted updates
Every release is signed with your keys, optionally held in an HSM or cloud KMS, and encrypted, so the copy we store is ciphertext. Your own firmware holds the key that opens it — or, if you encrypt for each camera, no firmware does, and each camera gets that key in a lockbox only it can open. Devices verify against a key baked in at the factory; anti-rollback blocks old builds.
Learn more -
Staged rollouts
Offer a release to a cohort, a percentage at a time, and raise it when the numbers look right. One rollout per product and cohort, so nothing overlaps.
Learn more -
Rollback and recovery
A device that fails to boot new firmware returns to the build that worked, and the rollout pauses once failures cross your limit. If nothing boots, firmware recovery fetches an image that does.
Learn more -
Delta updates
A release ships compressed patches against the versions your fleet is actually running, so most devices download kilobytes instead of megabytes.
Learn more -
Fleet visibility
See which release every device runs, how a product splits across versions, when each camera last checked in, and which build it would fall back to.
Learn more -
Device data
Whatever your cameras log and measure is kept and charted, per device or across a whole product, and read back through the API, the CLI, or a CSV download.
Learn more -
Live view
Watch what a camera sees from its own page, on a grant that expires in minutes. Cameras only connect outward, so nothing reaches into the network they sit in.
Learn more -
Vulnerability monitoring
Every release's software bill of materials is scanned against public vulnerability databases, and your team is emailed when a new advisory affects software your fleet is running.
Learn more -
Team access and the API
Invite your team with roles, issue scoped tokens for CI, and read the hash-chained record of every change. Everything here is an API call your own scripts can make too.
Learn more
Run it yourself The update server is open source, so your fleet is never locked to us.
Self-hostingTalk to it directly
ReferenceEach service generates its own reference from the code it is running, so what you read is what it speaks.
-
Update API
Releases, rollouts, devices, cohorts and the audit trail. This is the API the command line calls, and the one your CI can call instead.
ota.cloud.openmv.io -
Data API
Topics and series for one device or a whole product, and the ingest endpoint your cameras post their measurements to.
data.cloud.openmv.io -
Live relay
The edge relay your cameras push frames to and your dashboards watch from. Every endpoint wants a short-lived token.
live.cloud.openmv.io