oeili

How it works

oeili is built on Google's Android Management API (AMAPI). Devices enroll as Device Owner once, then operate under a managed policy that oeili controls on your behalf. There are two paths to a working fleet — pick the one that fits how you want to source devices.

Path A — Bring your own phones

For teams that already own Android hardware or want full custody of their devices.

  1. 1

    Factory-reset the phone

    Start from a clean device. AMAPI Device Owner provisioning requires a fresh Android setup.

  2. 2

    Scan the oeili QR code

    During the welcome wizard, tap the screen 6 times, then scan the enrollment QR code we generate for your account. The device downloads Google's Device Policy Controller and provisions itself in 30-60 seconds.

  3. 3

    Policy + agent are pushed automatically

    AMAPI silently installs the oeili agent app via Managed Google Play, applies your fleet's security policy, and registers the device with our control plane. No manual steps.

  4. 4

    Connect via the REST API

    Your applications authenticate against api.oeili.com and route traffic through the device of your choice. SOCKS5 and HTTP CONNECT both supported.

Path B — Use oeili-operated capacity

For teams that want IPs without the hardware logistics.

  1. 1

    Specify your fleet

    Tell us how many devices you need, which regions and carriers, what your concurrency target is. We provision an isolated pool dedicated to your account.

  2. 2

    oeili operates the devices

    Hardware lives in our facilities. Each device runs the same AMAPI-managed agent, under the same policies and isolation guarantees as a bring-your-own deployment.

  3. 3

    Same REST API, same controls

    There's no difference at the API layer. Your code targets your pool the same way it would target your own devices — backends, sticky sessions, banlists, rotation all work identically.

Why AMAPI?

Android Management API is Google's official cloud-hosted management surface for Android Enterprise devices. By building on AMAPI we inherit Google-grade device security, policy enforcement, and silent app distribution — none of which we'd get from a custom MDM stack. For our customers it means devices behave as proper enterprise endpoints, not jailbroken consumer phones, with all the regulatory and operational implications that follow.

Talk to us about your fleet

We're working directly with early customers to size deployments and tune policies for their workloads. Tell us what you're building.

Contact us