01
Boot & lock screens
Logo on first boot. Wallpaper. Ambient display. Your name where the OS would otherwise say "HardenedOS."
White label
One OS.
Every brand.
HardenedOS is built to be white-labeled. Resellers ship the same hardened system under their own name, colors, app catalog, and support page — without rebuilding the OS, without their customers ever seeing "HardenedOS" anywhere.
Three brands, one image
Same Pixel. Same kernel. Same surveillance ceiling.
Three different reseller skins of the same HardenedOS build. Pushed over the air via the partner API; applied on the next manifest sync. No flashing, no re-provisioning.
9:41
Saturday, May 9
Sentinel Mobile
Government tier · classified
9:41
Saturday, May 9
Pacific Health
Corporate · HIPAA fleet
9:41
Saturday, May 9
OMEMO Global
Basic · privacy first
The reseller logos and pill colors above are bundle artifacts — uploaded via the admin panel, signed by HardenedOS infrastructure with ECDSA P-256, served over a signed-URL CDN, verified on-device against a key pinned in the OS image.
What you customize
Every surface a customer sees, you control.
02
OS name override
The string the user sees in About → Phone, the Settings header, and OTA notifications. Show them your product, not ours.
03
Accent & system colors
Single hex value. The OS recolors checkboxes, switches, focus rings, sidebar accents — the whole UI tints to your brand.
04
App catalog
Upload your APKs. Mark them required, recommended, or optional per tier. The device pre-installs on activation, syncs new apps OTA.
05
Support page
One URL. Replaces every "Help" / "Contact us" link in the OS. Customers reach your support, not ours.
06
MDM management surface
Branded admin panel for your IT team. Same backend; their dashboard wears your colors and points at your endpoints.
MDM, white-labeled too
Same panel. Their brand.
The reseller admin runs identical code on identical infrastructure. Their IT team sees their wordmark, their accent color, their support URL — not ours. Switch tenants and the chrome is the only thing that changes.
mdm.hardenedos.com
Demo Reseller
Reseller rsl_demo
Balance
$1,000.00
Devices
14
Active codes
23
Recent devices
- dev_a8f1…Pixel 8aCORP
- dev_b2c4…Pixel 9CORP
- dev_e3d7…Pixel 7aPERS
fleet.sentinelmobile.com
Sentinel Operations
Reseller rsl_sentinel
Balance
$50,000
Devices
1,247
Active codes
312
Recent devices
- dev_4c2a…Pixel 9 ProGOV
- dev_8e1b…Pixel 9 ProGOV
- dev_3f7d…Pixel 8 ProCORP
The DOM, the routes, the database — all identical. The reseller's IT team logs into a panel they understand to be theirs. Their support tickets reference their domain. Their auditors see their brand in the screenshots. We never appear in their workflow.
Try it
Configure a brand. Watch the device change.
Type a name, pick a color, swap a logo. The lock screen on the right updates as you go. This is the same configuration the admin panel takes — minus the "Save" step.
How it works
Upload once. Every device picks it up on the next sync.
01
Upload via admin panel
Drag in your logo, set the accent color, type in your OS name override and support URL. Drop in APKs for the catalog. Click Save.
Logoacme-logo.png · 96 KB
Wallpaperacme-bg.jpg · 1.4 MB
Accent#f59e0b
OS name"Acme Mobile"
02
HardenedOS signs the bundle
Server packages everything into a versioned bundle, signs with ECDSA P-256 against the offline-held infrastructure key, drops it on the signed-URL CDN.
# server emits { "bundle_version": 3, "bundle_url": "https://repo.hardenedos.com/branding/...", "bundle_sha256": "a3f8...", "signature": "<ECDSA P-256 ASN.1>" }
03
Device verifies + applies
DPC fetches on next manifest sync. Verifies the signature against the pinned public key in the OS image. Applies overlay, restarts the launcher, done. ~2-5 minutes from save to device.
# adb logcat -s HardenedOS/Branding I bundle v3 fetched · 1.6 MB I signature verified I overlay applied I launcher restarted
Your name. Our hardening. Your customers.
Open the admin panel and configure your first reseller bundle. Or talk to us about onboarding a fleet.