POS, KIOSKS, PAYMENT TERMINALS, CLINICAL DEVICES
Device Management Infrastructure for the Operating Edge
Recent Pipelines
1
Pipeline 05/7/2026 06:20:04
Live Run Status
RUNNING
Stage 1
SUCCESS
1
Esper Agent v10.0.3396 Update 04/27/2026
Live Run Status
SUCCESS
Stage 1
SUCCESS
1
Esper Agent v10.0.3285 Update 04/14/2026
Live Run Status
SUCCESS
Stage 1
SUCCESS
1
Esper Agent v9.4.3085 Update 03/19/2026
Live Run Status
SUCCESS
Stage 1
SUCCESS
View All Pipelines
Device Management Infrastructure
Device Management Infrastructure (DMI) is the full management system for company-owned hardware doing a single job — kiosks, point-of-sale systems, barcode scanners, signage. Traditional MDM handles policy and control, but it's only one layer; DMI is the whole foundation beneath it — the OS, provisioning, and updates that keep the hardware running the business. Devices that can't drift, can't wait for a tech, and can't be managed like personal devices. Esper is the infrastructure built to handle that specific demand.
LEARN MORE ABOUT DMI →One operational foundation. Built to be built on.
Each product solves a problem other tools weren't built to touch. All of them run on the same declarative core and expose the same API — so what your team scripts, wraps, and builds on Esper compounds with every product we ship.
DEVICE MANAGEMENT
Esper Deploy
Define what every device should be — apps, settings, OS config, security posture — once. The fleet converges and stays there.
Explore →Android · iOS · Windows · Linux
PROVISIONING
Esper Seamless Provisioning
The Esper agent ships inside the device image. Boot plus network equals enrolled — the device finds your tenant, pulls its Blueprint, and configures itself, typically in under 5 minutes. No staging room, no kitting, no technician. 40+ OEMs ship provision-ready today.
Explore →Android · Linux
CUSTOM OS
Esper Foundation for Android
Custom Android without the maintenance burden — Esper builds, patches, and supports the OS through its full lifecycle. The Foundation SDK is a Maven artifact you pull into your app, with direct access to OS subsystems a standard Android app can't reach.
Explore →Android
OTA INFRASTRUCTURE
Esper Airwave
Fully managed, end-to-end OTA firmware infrastructure for Android — staged rollouts, automatic rollback — shipping secure updates in hours, with no MDM enrollment and no servers to build.
Explore →Android
KIOSK BROWSER
Esper Titanium
When the browser is the app — kiosk, POS, clinical, signage — Chrome is the wrong tool. Titanium is the same Chromium engine with every default inverted: allowlist-only URLs, clean slate every session, zero Google telemetry or branding. Native on AOSP.
Explore →Android
ON-PREM GATEWAY
Esper Edgebox
An on-prem gateway that runs provisioning and operations locally instead of through the cloud. For large or bandwidth-constrained fleets: provisioning to ~2 min/device, update bandwidth down up to 98.75%.
Explore →Android · iOS · Windows · Linux
WINDOWS TO ANDROID CONVERSION
Esper Firebolt
A hardware refresh isn't always in the budget. Firebolt converts your fielded Windows x86 devices to Foundation for Android — extending device life past EOL and bringing the fleet onto Esper's OTA and management stack. Every engagement is scoped to your device and peripheral configuration.
Explore →Windows → Android
ONE PLATFORM
Stop stitching vendors together
Provisioning to OTA to browser lockdown — one console, one API, one Blueprint model, across every OS you run.
Their words. Not ours.
“
To support better customer and employee experiences across our POS, tablets, and other devices, we needed a solution that worked for our next generation enterprise Android apps. Esper is a true partner. Working with them allows us to move fast, save money, and now we can make strategic decisions about what hardware to use.
Mas Yoshida
Director, Taco Bell
“
Esper's seamless deployment ensures that even patients who are not as comfortable with technology can successfully use our service. Device set-up is simple, there is zero configuration needed by the patients, and Esper's full-service solution detects connectivity and sensor failures ahead of time and alerts the Spire team for proactive outreach to our patients — often before they even notice an issue.
Neema Moravej, PhD
Co-founder & Chief Scientist, Spire Health
85%
reduction in provisioning time
REMOTE PATIENT MONITORING COMPANY
60%
OpEx saved
MAJOR RETAIL CHAIN
4,000
support tickets prevented
MULTI-BRAND RESTAURANT GROUP
70,000
devices configured with a single command
MAJOR RESTAURANT CHAIN
80,000
active devices moving 60 TB with zero hitches, crashes, or dropped connections
GLOBAL DEPLOYMENT
SECURITY & COMPLIANCE
Runs on audited infrastructure
Esper is audited to PCI DSS v4.0 (SAQ-D), SOC 2, and ISO 27001. Role-based access gives L2/L3 engineers full control and front-line staff view-only. Every remote session is logged, so you always know who connected to a device, and when.
PCI DSS v4.0
SOC 2
ISO 27001
RBAC
Session audit logs
Esper's Device Management Infrastructure, layer by layer
Every layer does one job. Here's what each one solves — and why teams stop building it themselves.
Deploy
Foundation
Firebolt
Airwave
Provisioning
Titanium
Edgebox
DEVICE MANAGEMENT
Esper Deploy
Define desired device state once; the fleet converges and stays converged — every device, every OS you run, every location, without a ticket or a technician.
THE PROBLEM
Traditional MDM is imperative and reactive: push a policy, hope it sticks, dispatch a tech when it doesn't. That model breaks the moment the fleet stops being individually knowable and becomes a system — the manual tax scales linearly with device count.
WHY ESPER IS THE CHOICE
Deploy is declarative and continuous where MDM is imperative and reactive — the shift CloudOps made over manual ops, applied to physical hardware. And it's the substrate: every other Esper product reads and writes the same Blueprint model and the same API, so what your team builds on it compounds instead of bolting on.
WHAT THAT MEANS
Devices that can't drift, without anyone watching them.
IN THE FIELD
70,000 devices configured with a single command — major restaurant chain.
CUSTOM OS
Esper Foundation
A purpose-built Android OS Esper owns end-to-end — built, patched, and supported by Esper through the device's full lifecycle, for problems that live below the layer MDM operates on.
THE PROBLEM
An aging OS you can't patch, can't extend, and can't afford to replace. CVEs compliance won't sign off on. Developers blocked by an OS that won't expose what they need. And a hardware refresh cycle finance keeps deferring.
WHY ESPER IS THE CHOICE
Esper owns the OS image itself, so it delivers what's architecturally impossible from on top. The Foundation SDK is a Maven artifact you pull into your app, with direct access to OS subsystems a standard Android app can't reach. And on x86, Firebolt converts end-of-life Windows machines to Foundation — a forced refresh becomes a software decision.
WHAT THAT MEANS
A custom OS without owning the maintenance.
IN THE FIELD
“Esper is a true partner… we can make strategic decisions about what hardware to use.” — Mas Yoshida, Director, Taco Bell
WINDOWS TO ANDROID CONVERSION
Esper Firebolt
Convert fielded Windows x86 devices to Foundation for Android — extend device life past EOL and bring the fleet onto Esper's OTA and management stack, without buying new hardware.
THE PROBLEM
Windows EOL turns working hardware into a compliance liability. The replacement math is brutal: new devices, new peripherals, re-certification, truck rolls — for hardware that still powers on every morning.
WHY ESPER IS THE CHOICE
Esper Firebolt is only possible because Esper owns the OS on the other side of the conversion. Every engagement is scoped to your exact device and peripheral configuration — this is a conversion program, not a download.
WHAT THAT MEANS
The hardware refresh becomes a software decision.
OTA INFRASTRUCTURE
Esper Airwave
Fully managed, end-to-end OTA firmware infrastructure for Android — staged rollouts, automatic rollback — shipping secure updates in hours, with no MDM enrollment and no servers to build.
THE PROBLEM
Building a production OTA pipeline means servers, a CDN, signing, rollout/rollback logic, and a team to run it — a multi-quarter project that just keeps the lights on. The alternative, deferring updates, is a compliance and sales problem: RFPs now require documented patch management.
WHY ESPER IS THE CHOICE
The one Esper product that runs fully standalone — any AOSP build, any MDM (Esper's, a competitor's, or none). Staged rollouts with verified boot, and automatic rollback when an update fails — a bad push reverts instead of bricking the field.
WHAT THAT MEANS
OTA infra without the overhead.
PROVISIONING
Esper Seamless Provisioning
Zero-touch provisioning for dedicated Android, Linux and Windows fleets — drop-ship to location, and the device configures itself on first boot. No kitting, no staging, no one touching it.
THE PROBLEM
Every new location, refresh, or expansion means devices received, configured, tested, and re-shipped before they can work — via a kitting facility or 3PL. A physical tax that scales with the fleet: more devices, more touches, more cost, more room for error.
WHY ESPER IS THE CHOICE
The Esper agent ships inside the device image, so provisioning starts at first boot — no dependency on Google's zero-touch portal, OEM enrollment programs, or GMS. Boot plus network equals enrolled, typically in under 5 minutes. 40+ OEMs ship provision-ready hardware today.
WHAT THAT MEANS
From box to deployed as soon as you power it up.
IN THE FIELD
85% reduction in provisioning time — remote patient monitoring company.
KIOSK BROWSER
Esper Titanium
A custom enterprise browser for dedicated hardware — every consumer default inverted, locked down at the engine level and managed through the same Blueprints as the device.
THE PROBLEM
Consumer browsers were built for a person at a desk with twenty tabs. Kiosk mode hides the UI but leaves the consumer architecture underneath — uncontrolled updates, telemetry to the vendor, lockdown a determined user can bypass. Building and maintaining your own browser means owning every CVE patch cycle forever.
WHY ESPER IS THE CHOICE
Esper Titanium builds allowlist-only URLs, a clean-slate session, and update control into the browser engine itself — not bolted on top — so the gaps a determined user finds in kiosk mode don't exist. Zero vendor telemetry or branding, with builds coming for Android, Windows, iOS, and Linux.
WHAT THAT MEANS
The browser engine, locked to a single job.
ON-PREM GATEWAY
Esper Edgebox
An on-premises gateway that runs provisioning and device operations locally instead of through the cloud — for fleets where cloud-only bandwidth-and-time math breaks.
THE PROBLEM
Every cloud operation is a cost multiplied by device count. Provision a thousand devices and each pulls its full config separately; push an update to a hundred and you move the payload a hundred times. On constrained connections, provisioning misses deadlines and rollouts throttle the network everything else depends on.
WHY ESPER IS THE CHOICE
The gateway talks to Esper Cloud once, then serves the fleet locally — orchestration stays in the cloud while the heavy lifting moves to where the devices are. Building that split yourself means running and securing on-prem infrastructure at every site.
WHAT THAT MEANS
One download serves every device on site.
IN THE FIELD
Provisioning down to ~2 minutes per device; update bandwidth cut by up to 98.75%.