One stack for display fleets, kiosk tablets, and managed Android devices

Run content, apps, and kiosk policy from one tight operator surface.

Topolo MDM turns existing Topolo runtime pieces into one clear control plane: enroll the device, choose a mode, assign a feed or app, confirm the launch.

Modes
3
Personal display, business display, managed device.
Control loop
Queued
Desired state flows through the existing device command queue.
Stack
Web first
Console, control plane, feed API, app catalog, and provisioned Android runtime.
Operator flow
Enroll, assign, confirm
Live contract
Device mode Business display
Clockme tablet
Tenant feed assigned, kiosk locked, default launcher target pinned.
Content
Preview current feed
See what the screen will show before the device polls again.
Apps
Install or launch catalog apps
Package browsing stays in the app library. Device control stays in MDM.
01
Pick the device mode
Personal display, business display, or a fully managed Android device.
02
Attach the right feed or app target
Reuse existing feed and launcher infrastructure instead of building parallel systems.
03
Watch queue-backed status settle
Desired state stays readable while the runtime still speaks the current command protocol.
Modes

One product, tuned for the simplest personal display flow through to fleet-grade operations.

Personal
Personal display

For a phone or tablet running stories, photos, or a lightweight feed loop with almost no admin burden.

Business
Business display

For retail, hospitality, and kiosk fleets that need feed assignment, default apps, lock task behavior, and straightforward tenant management.

Managed
Managed device

For operators who need system actions, package control, ADB toggles, settings access, and more robust fleet governance.

What stays in place

Tighten the experience around the stack that already exists.

Console
Astro + AppRoot

One operator surface for overview, devices, content, apps, and enrollment.

Control plane
Queue-backed desired state

Readable profiles in the web app, translated into the existing command queue on the backend.

Runtime
TopoloProvision + TopoloFeed

No new launcher, no new player, no duplicate CMS. Keep the on-device shell and content runtime.

Catalog
TopoloAppLibraryAPI

Package browsing belongs in the catalog service while state and device actions stay in MDM.

Start

Open the console and shape the device in minutes, not menus.

Sign in with Topolo Auth, enroll a device, assign the mode, and confirm the launch. Everything else stays available, but the main path stays obvious.