Enrollment
Generate a QR, watch a device come up as a pending enrollment, and see the organization-owned promotion the dashboard hands you.
A real device-management server, yours for twelve hours.
Not a screenshot tour and not a shared sandbox. One click gives you your own Wyrd instance on its own subdomain, with its own database and its own admin account — the same binary our customers install on their own hardware.
Write the password down now. It is shown here and nowhere else — we do not email it, and the server will not show it to you again. Lose this page and you can reopen demo.wyrd.link from the same network to get it back.
Install the client on the phone's personal user. It is served straight from your own instance:
Sideload it and open it:
adb install -r wyrd.apk
In the dashboard, create a device and scan its enrollment QR with the app. Android builds a managed profile and the device connects back to your instance's device socket at — straight through, with its own TLS, no proxy in the path.
Promote the profile to organization-owned, which is what unlocks the device-wide controls:
adb shell dpm mark-profile-owner-on-organization-owned-device --user 10 link.wyrd/.admin.WyrdDeviceAdminReceiver
No phone to hand? Skip all of this — the sample fleet already has devices in it, and everything except live command delivery works without one.
Generate a QR, watch a device come up as a pending enrollment, and see the organization-owned promotion the dashboard hands you.
Set a policy, then compare it against what each device reports back as actually applied — the gap between intent and reality is the whole job.
Build a rule, target it at a group, and see it fire. The sample fleet ships with offline, failed-unlock and patch-exposure rules already raising alerts.
Hardware and app inventory per device, battery, and locations on a basemap the server hosts itself rather than borrowing from a tile vendor.
Devices are matched against the Android Security Bulletin catalog, so the exposure page shows real advisories against real patch levels.
Upload an APK and push it with a signed download URL, drive per-app managed configuration, or install a CA certificate across the fleet.
After twelve hours the instance is stopped and its data directory is deleted. There is no warning, no extension and no export. Anything you want to keep, copy out first.
This is a shared demo host, not your infrastructure. Do not enroll a device you care about, and do not upload anything you would mind losing or having seen.
One live demo per network address. Ask again while yours is still running and you get the same instance back rather than a second one — which is also how you recover the password.
Production Wyrd requires GrapheneOS hardware attestation at enrollment. The demo turns it off, because a stock phone cannot produce it — that is the one setting here that differs from a real install.