One console for every client's phones
MobileLinkUp is device management for the people who look after other companies' hardware. Every client in one list, kept apart from each other, counted by the device so the numbers match your invoices.
Runs on your own server. One binary and one database file.
What you get
Six things, because those are the six that come up when you manage handsets you do not own.
Every device in one list
Search across all your clients at once. The handsets with something wrong sort to the top: deprovisioned, out of compliance, or quietly stopped reporting.
Clients stay apart
An engineer can be restricted to named clients. One client cannot discover that another exists, and a device outside an engineer's remit answers the same way as one that was never there.
Lock, wipe, erase
From the device page, with the reason recorded. Switch on two-person approval and no single engineer can wipe a handset alone.
Enrollment without a site visit
Factory reset the phone, scan a QR code at the first setup screen, wait a few minutes. Nothing to install by hand, and nothing of yours exposed to the client's network.
Apps and settings per group
Force-install, make available, block, or lock a handset to a single app. Warehouse scanners and office phones get different rules without two consoles.
An audit log you can hand over
Every action records the engineer, the client, the target, the reason and the address it came from. The log is hash-chained, so an edited entry stops verifying.
Getting a client on board
Three steps, and the only one that needs the client is the middle one.
-
Add the client
Pick an identifier. It is permanent and it appears in URLs, so choose the short version of their name.
-
They sign up with Google
Their IT admin completes Android Enterprise signup with a work email address. It is free for them, and it is the only thing they have to do.
-
Scan at first boot
Tap the first setup screen six times to open the QR reader, point the camera at the code, and the handset comes up managed.
Billing that matches how you invoice
Device counts per client per month, recorded at the month's peak rather than whatever the number happens to be on the first. A client who ran forty handsets for three weeks is billed for forty, not for the twenty-eight still switched on when you looked.
Exports to CSV. Put it straight into whatever you raise invoices with.
What it runs on
Your server, not ours. There is no tenant of ours holding your clients' device records.
- Deployment
- Any Linux VPS, behind your own TLS
- Footprint
- One static binary, ~7 MB resident
- Data
- One SQLite file, credentials encrypted at rest
- Sign-in
- Entra ID, Okta, Google Workspace, or local accounts
- Backups
- Nightly, encrypted, off the host
- Android platform
- Google's Android Management API, no EMM partnership
Where it stands
Worth saying plainly, because finding out later wastes your time and ours.
| Android | Working | Enrollment, policies, apps, lock, reboot and wipe, through Google's Android Management API. Handsets need Google Mobile Services, so Pixel and Samsung are fine and no-name tablets are not. |
|---|---|---|
| iOS | In progress | The MDM protocol, SCEP and profile signing are built and tested against a simulated device. Live enrollment waits on Apple's vendor certificate, which they approve by hand. Ask us where that is. |
| Windows and macOS | Not started | Not on the roadmap yet. If it decides a deal for you, say so and it will be. |
Have a look before you commit to anything
The demo runs on real console code against invented clients. Nothing in it reaches a real handset, so click whatever you like.