Exposure check Contact
Exposure check Contact

MDM

Mobile device management

Otukan device management enrols, configures and controls Android and Apple phones and tablets, with kiosk modes and control over where fleet data lives.

Discuss your device management requirements
A fleet of devices under one policy; a few devices drift out of policy and are brought backOne policy across every device

  • Built for each platform

    Otukan manages Android through Android Enterprise and Apple devices through Apple's device management framework, using each platform's own modes rather than a lowest common denominator.

  • From enrolment to operations

    Enrolment, policy, app delivery and remote actions run as one connected workflow, so a device reaches the state you intended and stays there.

  • Your data, your rules

    You decide where management data lives, who administers the fleet and when supplier support may reach your tenant.

Fleet risks Otukan brings under control

Pick a risk to see how Otukan spots it, what the fleet does about it and what your administrators can read afterwards.

Device outside management

  1. Detect

    Zero-touch or QR provisioning on Android and Automated Device Enrollment on Apple devices bring company hardware into management at first set-up.

  2. Respond

    The device joins its group with the right ownership mode, then receives its policy and apps.

  3. Report

    The inventory lists each managed device with model, OS version, policy status and managed apps.

Weakened device settings

  1. Detect

    Each device reports whether its passcode, restriction, network and certificate settings arrived.

  2. Respond

    Settings that did not arrive are visible per device, so administrators correct the group or the device before the gap matters.

  3. Report

    Policy status per device shows which units match their group and which do not.

Missing device holding work data

  1. Detect

    When the loss is reported, the inventory pinpoints the device by model, group and managed apps.

  2. Respond

    An administrator locks or wipes it remotely from the console.

  3. Report

    Every lock, restart and wipe is logged against the administrator who ran it.

Dedicated device used off-task

  1. Detect

    Dedicated Android devices run in single-app or multi-app kiosk operation, limited to the apps you approved.

  2. Respond

    Users stay inside the approved apps, and maintenance exit is reserved for authorised staff.

  3. Report

    Kiosk devices appear in the inventory with their policy status and managed apps.

Work data on personal phones

  1. Detect

    Personally owned devices enrol in the platform's own mode: a work profile on Android, User Enrollment on Apple devices.

  2. Respond

    Work apps and data stay in the separated work area, and the employee's personal side stays private.

  3. Report

    Administrators see the managed work apps, not the owner's personal content.

Supplier reaching your tenant

  1. Detect

    Supplier support access to your tenant is controlled rather than standing, and administrator roles are separated.

  2. Respond

    Support reaches the tenant only with the approval your organisation gives.

  3. Report

    An audit log your own auditors can read records who accessed the tenant and what changed.

What Otukan device management does

Each capability handles one part of running a fleet, and each works through the management framework of the platform it serves.

  • Enrolment

    Brings corporate-owned, personally owned and dedicated devices under management through the enrolment path that fits each group.

  • Policy management

    Applies passcode, restriction, network and certificate settings per group, and confirms on the device that they arrived.

  • App management

    Installs, configures and updates required apps, including in-house apps, through managed distribution.

  • Kiosk and dedicated devices

    Keeps shared and single-purpose Android devices on approved apps, with controlled maintenance access and recovery after restarts confirmed on each model.

  • Remote actions

    Locks, restarts or wipes a device from the console, with each action recorded against the administrator who ran it.

  • Inventory and visibility

    Shows model, OS version, policy status and managed apps for each device, so drift is visible before it becomes a problem.

  • Data and administrative control

    Separates administrator roles, controls supplier support access and keeps an audit trail your own auditors can read.

  • OEM management channels

    Lets a device maker offer management to its own customers, with one tenant per customer and clear support boundaries.

How it works

  1. Map the fleet

    We map your devices, OS versions, ownership models and the workflow that matters most.

  2. Enrol devices

    Devices join management through the enrolment path that fits their platform and ownership.

  3. Apply policy

    Groups receive their settings and apps, and each device reports back what it applied.

  4. Operate the fleet

    Inventory, remote actions and audit logs keep devices in the state you intended.

Otukan device management gives an institution one controlled workflow for its phones and tablets: devices enrol through the path that fits their ownership, receive the right policy and apps, and stay in the state you intended, with you deciding where fleet data lives and who administers it. Otukan manages Android through Android Enterprise and iPhone and iPad through Apple’s device management framework, using each platform’s own modes. Device makers can also offer Otukan management to their own customers. Every workflow is proven on your own devices in a pilot before the wider rollout.

Fleet scope

Otukan starts with the fleet you actually run: which devices, on which operating systems, owned by whom. Those answers decide which management modes each platform allows, and Otukan configures every group on its own platform’s terms.

Operating systems

Android and Apple devices are managed through different frameworks, set by the platform owners. Otukan works natively with both.

AndroidiOS and iPadOS
Management frameworkAndroid Enterprise, with a device policy controller app on the deviceApple device management protocol, with push notifications through Apple’s service
Corporate-owned devicesFully managed device, or work profile on a company-owned deviceSupervised device, usually through Automated Device Enrollment
Personally owned devicesWork profile, separating work and personal dataUser Enrollment, tied to a managed Apple account
Single-purpose devicesDedicated device, using lock task modeSingle App Mode and related options on supervised devices
Bulk provisioningZero-touch enrolment, QR code or other provisioning methodsApple Business Manager or Apple School Manager

The rows are not equivalents across columns: each platform sets its own administrator powers in each mode. Otukan configures every workflow per platform and tests it on the operating system versions and device models in your fleet, so each task is proven on the hardware you run.

Ownership models

Corporate-owned, personally owned and dedicated devices carry different privacy expectations and different administrator powers. Otukan applies the mode that fits each group: full control on corporate-owned hardware, a separated work area on personal devices, and a locked task on dedicated devices. Staff keep their privacy, and the organisation keeps control of its data.

Management tasks

Otukan connects the tasks that run a fleet into one chain, so each step builds on the one before it.

  1. Enrolment. The device joins management with an identity, an ownership mode and a group.
  2. Policy. Passcode rules, restrictions, network and certificate settings arrive per group.
  3. App delivery. Required apps are installed, configured and kept up to date.
  4. Operations. Inventory, remote lock, restart and wipe, and reporting keep the fleet where you want it.

Each task has a clear definition of done that Otukan checks on the device: enrolled into the right group, policy confirmed, app at the required version. Those same checks become the acceptance tests for your pilot.

For enrolment paths and prerequisites, see MDM device enrollment. For shared and single-purpose Android devices, see Android kiosk management. Policy is covered on mobile device policy management. How to weigh each workflow against your fleet, from setup to retirement, is covered on Otukan device management capabilities. Tying each device to a user from your directory is covered on identity and access.

Technology ownership

Institutions need to know who builds, runs and supports each part of a management service. Otukan answers that per workflow, in writing.

What you getWhy it matters
A statement per workflow of what Otukan builds and operates, and which platform services it relies onSupport, updates and responsibility are clear from day one
Your choice of where management data is hostedHosting decides who can reach fleet data
A map of the platform-owner services in the data pathSome management traffic passes through Apple or Google services wherever the server runs
Separated administrator roles and approved, logged supplier accessAdministrator access is access to every managed device

Public institutions specifying a managed fleet should read government mobile device management. Institutions that need to keep management data under their own control should read MDM data sovereignty. Device makers that want to offer management to their own customers should read OEM mobile device management.

Device management works beside Otukan’s app protection and device security. The difference is covered on MDM vs mobile device security. The MDM requirements checklist lists the questions Otukan answers in writing for your fleet.

Common questions

  • Is mobile device management the same as mobile device security?

    No. Device management applies enrolment, configuration and policy through the operating system's management framework. It can require a passcode or restrict features, but it works above the operating system. Otukan's firmware-level device security and in-app protection address threats that management policy cannot reach, and they complement device management rather than replace it.

  • Which devices does Otukan device management cover?

    Phones and tablets. Android devices are managed through Android Enterprise and Apple devices through Apple's device management framework. The two platforms differ in enrolment, supervision and what policy can enforce, so Otukan configures each on its own terms and tests every workflow on the operating system versions and models in your fleet before rollout.

  • Can device management data stay inside our organisation?

    Otukan lets you decide where management data lives and who administers it. Some management traffic still passes through the platform owners' services wherever the server runs, for example Apple's push notification service for Apple devices. Otukan maps each flow with you, covering storage location, administrator access, key custody, retention and exit, so the answer is written down rather than assumed.

  • Can we manage devices we supply to our own customers?

    Yes. Otukan supports device makers and suppliers that offer management to their customers, with a separate tenant for each customer, a defined view for the supplier's own support staff, and written ownership of licensing, support and exit for the life of the devices.

Related

Take control of your mobile fleet

Tell us whether the devices are your own fleet or devices you supply to customers, your Android and iOS mix, and the workflow that matters most. We never ask for administrator credentials, enrolment tokens or device lists with personal data.

Discuss your device management requirements
Or request a technical demo