Most browsers are built for a person at a desk — tabs, sign-ins, extensions, auto-updates. Deploy it on a kiosk, POS, or patient tablet and you inherit every one of those as a liability. Titanium is that same web platform with every consumer default inverted for dedicated hardware — managed from the same Esper console as the rest of your fleet.
Titanium renders your web app pixel-for-pixel like the browser users already know — then strips out everything that makes a consumer browser wrong for dedicated hardware. Full lockdown, allowlisting, and clean-slate sessions for Android.
Your web app renders exactly as it does on a modern desktop browser — full standards support, current web APIs, real performance. Not a stripped-down webview that silently drops the feature your app depends on.
Allowlist the URLs you want and nothing else resolves. No settings surface, no escape hatch, no leftover session for the next user. Enforced in the browser itself — not an OS overlay someone can slip past.
Your name, your icon, your splash screen, your error pages. Home screen, new tab, and every chrome surface are yours to define — zero third-party branding anywhere the customer can see.
Every URL blocked unless you allowlist it. The settings menu and the shortcuts that reach it are hidden and disabled. Long-press and context menus switch off via managed config. Enforcement inside the browser — no bypass path.
No tab or session persistence between users. Once the browser leaves memory, the next person starts fresh — no leftover tabs, no cached credentials, no previous-user data. Configurable inactivity timeout.
Do Not Track and Network Isolation ship on, where a consumer browser needs an explicit flag for either. The browser can't reach anything outside your allowlist, including analytics endpoints. Diagnostic data routes through Esper — never a browser vendor.
Runs on any Android hardware — GMS or non-GMS alike. No dependency on Google Mobile Services, a vendor account, or an app store. Native on Esper Foundation, AOSP, and Foundation x86 — the environments a consumer browser barely survives.
The question isn't whether browser kiosk mode works. It's whether it holds at fleet scale, across hundreds of locations, without a team patching the gaps.
Consumer-browser kiosk mode is a personal browser with restrictions bolted on. Titanium is a dedicated-hardware browser with full web rendering built in.
Titanium started as a request from a customer running Esper Foundation. They'd already locked their browser to an allowlist — and users still got out. The About page linked to a service agreement, the agreement linked to a site, the site opened a new window, and that window was a fresh browser.
Consumer browsers are built for people who want to explore; lockdown bolted onto that architecture always leaves a thread to pull. So we inverted it: enforcement lives in the engine, not in a policy overlay a determined user can slip past. It got bug-bashed in one of the most adversarial environments there is.
If your surface is a menu board, a check-in flow, or signage, it's already a web app. Native Android means SDK work, peripheral APIs, and a full redeploy for every change. Titanium is the vessel: update your site, every device reflects it — no rebuild, no store submission, no app to maintain. Platform-agnostic, buildable by any web developer you already have.
The same web app runs the counter terminal, the customer-facing display, and the handheld — no per-device native port to maintain.
Ship a fix at 2pm and it's live on every device — no app-store gate, no version fragmentation across locations.
You bring the web app or CMS; Titanium and Esper MDM lock it to the hardware. Allowlists, config, and diagnostics live in the same Esper console as the devices — one place, not a second tool to run.
Titanium is the vessel for a web app you already run — signage, a menu board, a check-in flow, an education portal. If your team can build a website, they can build for Titanium; no native Android skills, and you update it server-side without pushing a new app to the whole fleet. When the app is your web surface, Titanium is the fit.
Fleets across hundreds of locations — POS, kiosks, check-in tablets — absorbing the operational cost every time a consumer browser acts like one.
Shipping hardware where the browser is the product surface, who'd otherwise carry a custom browser fork as a permanent engineering tax.
Clinical EDC, healthcare check-in, correctional, public terminals — where “locked down” has to be a guarantee, not a policy.
The strongest quantified story isn't a Titanium performance stat — it's cost displacement. A POSDATA/Levata account on ~584 Ivanti Browser licenses was force-migrated to subscription pricing. Titanium at $2/device/month is the wedge. Chase a cleared customer quote or the Intel deployment story to fill this slot — don't drop in a number we can't source.
Counter and dual-display checkout that can't drift or crash mid-rush.
Kiosks and self-checkout with every escape route closed at the engine.
Patient-facing tablets — telemetry through Esper, silent media capture via config.
Web-rendered content that stays on and never drifts to a vendor sign-in.
Check-in & concierge that looks like your product, not a browser vendor's.
Lockers and micro-stores locked to a single web surface.
Full-screen, no settings surface, no consumer-app audit flags.
Pin web content securely without a native app or a custom browser fork.
Bring a URL, leave with a kiosk. See Titanium lock a web app to your hardware — managed from the same console as the rest of your fleet.
Schedule a demo →