- BFSIBanking, Financial Services & Insurance
- HealthcareComing soon
- ManufacturingComing soon
- Retail & E-CommerceComing soon
Esper Airwave
Your devices are already in the field. A firmware fix shouldn’t need a technician per unit — Esper Airwave gives Android device makers a managed way to ship their own firmware over the air — canary first, then staged, with delta builds and auto-rollback, and no MDM required.
Buy through TechBag
Same software. Better outcome — at a lower cost.
How it’s rated
Full scoreboard ↓Quick answer
The Esper platform family
This page covers Esper Airwave — Esper’s standalone OTA firmware service for Android device makers. The rest:
Quick facts
30-second orientation- Product
- Managed OTA firmware infrastructure for companies that make Android devices
- Maker
- Esper.io Inc., Bellevue, Washington; founded 2018; co-founder and CEO Yadhu Gopalan
- Buyer
- Device makers shipping their own Android firmware, not IT teams managing staff phones
- Price
- Not published; Esper says Airwave pricing is customised to your scope
- Trial
- Esper offers a 50-device test cohort as the way to try it
- Android
- Android 8 to Android 15, by Esper’s own account
- MDM
- None required; Esper calls Airwave fully MDM-agnostic
- Rollouts
- A canary group first, then staged waves inside the maintenance windows you set
- India
- Bengaluru office; Esper’s cloud is hosted in North America on AWS, no India region
- In India via
- TechBag — cohort scoping, quote in INR with GST, first staged release
Understand managed OTA firmware before you buy it
Most product pages skip this. We start here — so you buy a capability, not a buzzword.
What is managed OTA firmware?
A hosted service that sends a device maker’s own firmware to units in the field, in stages, with a way back if it fails.
Zip files and site visits vs staged OTA releases — the honest table
What consolidation actually replaces, dimension by dimension.
| Dimension | Zip files and site visits | Esper Airwave |
|---|---|---|
| How a build reaches devices | A zip on a portal, side-loaded on site | Uploaded once, released by model and cohort |
| Who gets it first | Whichever site happens to update first | A canary cohort you pick in advance |
| When a build is bad | Technicians reflash units one by one | Rollback thresholds halt the rollout |
| Download size | A full system image every time | Delta builds that carry only the changes |
| Knowing who updated | Site reports gathered in a spreadsheet | Adoption tracked for each device |
| What it is NOT | — | An MDM, a price list, or an India-hosted service |
The cheapest test is the cohort: register one model, release one build to fifty units, and see whether a rollback threshold fires when it should.
The five pieces of the platform
Vendors love diagrams; buyers need to know what they’re actually operating. Here’s the whole platform, demystified.
Registry
Every device model is recorded by SKU, variant and build fingerprint, so a firmware package is tied to the exact hardware it was built for and nothing else.
Packages
Your build system uploads each OTA package to Airwave as a numbered version; full images and delta builds sit side by side, ready to be released to a model.
Rollouts
A release goes first to a canary group, then widens in stages inside maintenance windows you set, with auto-rollback thresholds watching each step.
Tracking
Adoption is tracked per device, so you see which units took a build; every action in the console can also be driven through Esper’s API from your own tools.
A model registry and versioned packages in Esper’s cloud — released canary first, in stages, with rollback thresholds.
Nine capabilities. Package, roll out, track.
Esper Airwave ships a device maker’s own Android firmware over the air, in stages, without needing an MDM.
Models known by fingerprint
SKU, variant and build fingerprint identify each hardware model, so a package built for one board never reaches another.
Every build kept and numbered
Packages are uploaded and versioned in one place, so the release history for each model is a list rather than a shared drive.
Ship only what changed
Delta builds carry the difference between two versions instead of a full image, which matters on metered or slow site links.
A small group goes first
A canary cohort takes each new build before anyone else, so a fault shows up on a handful of units rather than the fleet.
Widen the release in waves
After the canary, a staged rollout lets the build reach more devices step by step instead of every unit on the same night.
Update outside trading hours
Maintenance windows hold installs to the hours you choose, so a till or kiosk does not restart while a customer is waiting.
See which units took it
Per-device adoption tracking shows where each version is installed, so a stalled unit is found without a site visit.
Thresholds that pull a build
Auto-rollback thresholds sit on each rollout, and A/B partitions keep the previous system on the device to fall back to.
Release from your pipeline
Every Airwave action is exposed through the API, so a CI job can upload a build and start its canary without a console login.
Firmware fixes still travel by technician. Airwave ships them over the air, canary first.
Here’s what genuinely sets it apart — and exactly where it stops.
A release process you did not have to build
Without a service, a device maker writes and runs its own OTA server, client logic and rollout scripts. Airwave supplies that layer as a service: a model registry, versioned packages, canary and staged releases, delta builds and maintenance windows, from one console or the API.
Indifferent to the MDM your customers chose
Esper says Airwave needs no MDM and is fully MDM-agnostic. A maker selling terminals to many businesses can keep the operating system current while each customer runs Esper Deploy, another MDM or none, without asking anyone to re-enrol a device.
Room to recover from a bad build
A firmware fault in the field can mean a site visit per unit. Airwave puts a canary group in front of every release, watches each stage against auto-rollback thresholds, and works with A/B partitions so the previous system is still on the device if the new one has to be abandoned.
Where it stops
There is no public price, only a scoped quote and a 50-device test cohort. Esper lists Android 8–15 and nothing beyond it. Airwave updates firmware; it does not lock screens, push apps or wipe devices, which is Esper Deploy’s job. Packages sit in Esper’s North American cloud, with no India region.
The numbers behind the platform
What your Esper Airwave rollout looks like
Register the hardware models
Record each model by SKU, variant and build fingerprint, so every package you upload is tied to the right board.
Upload a build and pick a canary
Push one versioned package from your build system and name the small group of units that will always update first.
Run the 50-device cohort
Release to Esper’s 50-device test cohort, watch adoption per device, and confirm a rollback threshold actually fires.
Stage a release across sites
Widen a real build in stages inside maintenance windows, and compare delta and full-image download times on site links.
Drive releases from CI
Call the API from your build pipeline so each tagged build uploads itself and starts its canary without a console login.
The review scoreboard
Modelled on Gartner Peer Insights structure. *Counts and breakdowns are illustrative pending verified review collection.
Quick poll — what’s driving your evaluation?
Talk to an advisor“We used to email a zip to field engineers. Now fifty test terminals take each build before the other stores see it.”
“Each of our customers runs a different MDM. Airwave updates the OS underneath without asking any of them to switch.”
“A build that misbehaved on one board variant stopped at the canary stage, and the registry showed exactly which SKU it was.”
“No price on the website meant a scoping call before budget sign-off, and we would like Android 16 on the supported list.”
Where everyone sits — the grids
Analyst firms bury this view behind paywalls, and G2 retired its Grid. So here’s TechBag’s synthesis of the OTA firmware update market — tap any vendor to see why it sits where it does.
TechBag OTA Firmware Update Grid
Execution strength vs product vision — the classic market map, minus the paywall.
Quoted to scope, with a 50-device test cohort to start.
MDM Independence × Release Control
The grid nobody publishes — how far firmware delivery works without a particular MDM vs how much control you get over each release.
No MDM needed; canary, staged, delta and auto-rollback.
Positions are TechBag’s illustrative synthesis of public review-platform data and vendor documentation — not a reproduction of any analyst graphic. Verify before relying on it.
Esper Airwave vs the OTA firmware field
Against an in-house OTA pipeline, Memfault, Mender, 42Gears SureMDM and Scalefusion UEM — on Android coverage, price, release safety, MDM dependence, India data and exit.
| Dimension | Esper Airwave | In-house OTA pipeline | Memfault | Mender | 42Gears SureMDM | Scalefusion UEM |
|---|---|---|---|---|---|---|
| What it is | Managed Android OTA | Your own build | Device reliability cloud | Open-source Linux OTA | UEM with OEM firmware | UEM with FOTA module |
| Deployment | Esper’s cloud only | Wherever you host it | SaaS, global CDN | Hosted or self-hosted | Cloud or on-premise | Scalefusion cloud |
| Android coverage | Android 8–15 | Whatever you support | Android via Bort SDK | No Android support | Samsung and Zebra | OEM-dependent |
| Pricing model | Custom, by scope | Engineers + hosting | Monthly platform tiers | Monthly by device band | Per device, MDM licence | Per device, tiered |
| Published entry price | Not published | No licence fee | $3,495/month Growth | $34/month Basic | $3.99/device/month | $2/device/month |
| Included vs add-on | Standalone product | You build each part | OTA is optional | Deltas need Pro | E-FOTA licence extra | OEM support needed |
| Scale limits | Not published | As far as you build | 50,000 to custom | Unlimited on Enterprise | 7M+ devices overall | 10-device floor |
| Release safety | Canary + auto-rollback | A/B fallback only | Cohorts, roll forward | A/B with rollback | No downgrade | Windows and checks |
| MDM and API | No MDM, full API | Whatever you wire | SDK client or API | Proxy for Android | SureMDM enrolment | Scalefusion enrolment |
| Governance | SOC 2, ISO 27001 | Your controls | Audit logs on Enterprise | RBAC on Enterprise | OEM sets versions | File checks, reports |
| India data location | No India region | Your choice | Not published | US, EU or self-host | India region on offer | India-hosted |
| Support | Tiered, up to 24x7 | Your own on-call | Not on price page | Best effort below Ent. | India time zone | India time zone |
| Lock-in and exit | Packages are yours | Nothing to leave | Client in your image | Open source exit | Tied to the UEM | Tied to the UEM |
| Best fit | Makers of Android kit | Large in-house teams | Connected-product teams | Embedded Linux fleets | Rugged fleet owners | Managed fleet owners |
Which approach fits you?
Honest fit signals — because the fastest way to lose your trust is to pretend one product wins every scenario.
Choose Esper Airwave if…
- ✓You make Android devices and need canary, staged and windowed firmware releases without writing an OTA service yourself
- ✓Your customers run different MDMs, or none, and you need firmware updates that work regardless of which one
- ✓A bad build in the field would mean site visits, so auto-rollback thresholds and A/B partitions are worth paying for
Compare alternatives if…
- ✓You want crash data and fleet monitoring in the same tool as OTA — Memfault combines them
- ✓Your devices run embedded Linux or Zephyr rather than Android — Mender is built for those
- ✓You buy Samsung or Zebra hardware and only need the maker’s firmware pushed — SureMDM or Scalefusion can relay it
Do not expect…
- ✓A published Airwave price, or a ceiling on fleet size, before a scoping conversation with Esper
- ✓Firmware packages held in an India region; Esper’s cloud runs in North America
- ✓Kiosk lockdown, app pushes or remote wipe, which belong to Esper Deploy rather than Airwave
TechBag has no OTA firmware update guide yet, so Esper Airwave sits outside the category guides. Browse all products to compare it with the rest of the catalogue. →
What do hand-run firmware updates cost you?
Drag the sliders (devices you ship firmware to; engineer-hour cost). Estimates model engineering and field time spent building, pushing, chasing and recovering firmware updates at an assumed 1.5 hours per device a year, with 70% of it removed by staged releases and automatic rollback. Both figures are assumptions. Illustrative.
Loaded cost = salary + overheads per productive hour. Illustrative only — your TechBag quote models your actual environment and modules.
Three ways to consume it
Not published: Esper says Airwave pricing is customised to your scope, and its product page offers a 50-device test cohort as the place to start. Airwave is bought on its own — it needs no Esper Deploy subscription and no other MDM. Esper prices in US dollars with no INR list. TechBag scopes your models and fleet size first, then gets the quote in writing and bills it in INR with GST.
Airwave test cohort
Best for proving a release process
- 50 devices, as Esper’s page suggests
- Canary, staged rollout and rollback tested
- Pricing customised to your scope
+ Platform add-ons
Best for a broader rollout
- Scoped to your estate
- Add-on modules as needed
- Phased, right-sized deployment
Airwave fleet rollout
Best for makers shipping at volume
- Quoted to your models and fleet size
- Android 8–15, delta builds, API access
- No MDM or Esper Deploy subscription needed
Buy it for less — TechBag pricing beats list
Whatever the list prices above, TechBag negotiates a significantly better deal — with GST-compliant INR invoicing and local support. Ask us for your discounted quote.
Get an India-ready quote
Tell us your requirements and current tools — we’ll model it against what you spend today.
The 8 questions to ask every vendor
Take this into your next vendor call — including ours.
Are all your models on Android 8 to 15? Ask Esper when newer releases will be added to Airwave’s supported list.
Can every SKU and variant be told apart by its build fingerprint, so a package can never reach the wrong board?
Do your boards use A/B partitions? Without them, a failed update has nothing on the device to fall back to.
How large are full images on your slowest site links, and how much would delta builds save on each release?
Which MDMs do your customers run? Confirm Airwave sits alongside each one without a conflicting update policy.
Is North American hosting of packages and device data acceptable to you and to your Indian customers?
Which tier do you need: 9x5 with a 2-hour Sev 1 target, or Ultimate at 24x7 and 30 minutes?
Does the quote state device counts, term and what happens past the trial cohort? Ask for INR with GST.
Questions buyers ask
Ready to evaluate Esper Airwave?
Count the devices you ship firmware to first, or let a TechBag advisor scope a 50-device cohort with a real canary and rollback test.
Stats, ratings, review counts and pricing are illustrative and sourced from public materials; verify before purchase.