Zonix EM is a SaaS platform: there is no server to install and no console agent to maintain. All management happens through the web console, and devices talk to the platform infrastructure over the internet.
On the device side, Android management runs on Google’s Android Management API (AMAPI). That means the device needs Google Play services and internet access at provisioning time, and needs neither root nor any system modification.
— A Zonix EM account with an active organisation (tenant).
— An Android Enterprise enterprise linked to the account — the console walks you through that provisioning with Google.
— Android devices with Google Play services and internet access.
— An up-to-date browser to reach the web console.
Until the Android Enterprise enterprise is linked, device and policy operations respond with an "enterprise not configured" error — it is the first thing to check when something does not work on a new account.
Supported platforms and devices
Support for each platform sits at a different stage of maturity, and that difference is worth knowing before planning a rollout.
— Android via Android Enterprise (AMAPI) — generally available in production. This is the primary platform.
— Zonix EM Agent for Android — generally available in production. Extends what AMAPI offers with detailed telemetry, geofencing, clock-in/work hours, kiosk and inventory checkout.
— Microsoft Intune integration — available.
— Apple (iOS, iPadOS, macOS) — Private Beta.
— Windows — Private Beta.
Private Beta means the capability exists in the product but is not open for general purchase. If your fleet depends on Apple or Windows in production today, treat that as a requirement to confirm with the sales team before deciding.
From sign-up to first device
The normal path has four steps, all done through the console, with no manual server work.
— Create the account and confirm the email address — email verification is mandatory at sign-up.
— Link the Android Enterprise enterprise to the organisation through the guided console flow.
— Create at least one policy, choosing the management mode that matches how the device will be used.
— Generate an enrollment token and provision the device — in practice, scanning a QR Code on the welcome screen of a freshly reset device.
Enrollment tokens are valid for 24 hours by default, and the duration can be set at creation time. When a QR Code stops working from one day to the next, it is almost always expiry rather than a configuration error.
How device state reaches the platform
Understanding this flow saves diagnostic time. Device state is not queried on demand every time a screen opens: it arrives through notifications.
Google publishes device state changes to a Google Cloud Pub/Sub topic provisioned for your organisation. The platform receives those notifications through a webhook and updates the local cache that feeds the console. In parallel, when the Zonix EM Agent is installed, it sends its own telemetry and inventory, and receives commands pushed through Firebase Cloud Messaging rather than polling the server.
The practical consequence is that a device that is switched off, offline, or has had the agent removed keeps showing its last known state until it communicates again.