Evaluate device management capabilities on your own fleet, not on a feature list. Otukan device management runs enrolment, policy, apps, kiosk operation, remote actions, inventory, audit reporting and identity and access for Android and Apple phones and tablets. Each page in this collection takes one capability and shows what Otukan does with it on each platform, which role operates it and how you confirm it in a pilot on your hardware. Scope stays with phones and tablets, and every capability is described per platform and per enrolment mode.
Fleet scope
Ownership and platform shape every capability. A remote wipe erases a corporate-owned phone, but on a personal phone with a work profile it removes only the work side. Otukan describes each capability per platform and enrolment mode, so nothing is assumed across Android and iOS.
| Capability | The question it answers |
|---|---|
| Device enrollment | How does each device join management? |
| Policy management | Which settings apply, and did they arrive? |
| App management | Which apps are installed, at which version? |
| Kiosk management | How does a device stay locked to its task? |
| Remote device management | Who may lock, reset or wipe a device? |
| Inventory | What is in the fleet right now? |
| Audit reporting | Who changed what, and when? |
Operating model
Policy authority stays with your organisation. Otukan names the administrator role behind each capability, the platform services it depends on and the directory or security tools it connects to. It also states in writing which functions Otukan builds and operates and which a partner delivers.
Lifecycle
A capability earns its place when it holds up through change and recovery, not only at setup. Otukan tests each one through first enrolment, policy change, device recovery and offboarding before the wider rollout.