public active Last verified 2026-03-31

TopoloMDM

Public overview of the device-management cluster spanning the MDM API, operator console, and mobile scaffold.

Owners
device-platform
Source Repos
Applications/TopoloMDM, Websites/docs
Systems
Topolo Auth, TopoloMDM
Tags
mdm, devices, operations

What It Is

TopoloMDM is the device-management cluster for registration, polling, fleet control, operator console workflows, and an early mobile client scaffold.

Architecture

The repo currently spans a worker/API surface, a browser console, and a mobile scaffold with uneven maturity across those layers.

Runtime Surfaces

Use /systems/topolo-mdm for the current API host and repo inventory.

API Reference

The active route surface centers on device registration, polling, commands, fleet inspection, admin API-key operations, and operator helper endpoints.

Auth and Permissions

Public device registration and polling are separate from authenticated operator control flows. Operator and admin actions rely on Topolo Auth. The operator console now uses the shared Topolo cookie-refresh auth client for browser sessions.

Data Ownership

TopoloMDM owns tenant-scoped device state, command queues, operator console state, and related fleet-control records.

Deployments

TopoloMDM deploys as a cluster rather than a single polished product surface: worker API, console, and mobile scaffolding move at different speeds.

Failure Modes

  • mobile or console maturity is overstated compared with the actual repo surface
  • authenticated control flows are confused with public device registration flows
  • external package-catalog dependencies are mistaken for the core MDM API

Debugging

Start with /systems/topolo-mdm, then separate API, console, and mobile-scaffold issues before debugging deeper.

Change Log / Verification

  • Standardized TopoloMDM console browser auth on the shared Topolo auth client on 2026-03-31
  • Added canonical TopoloMDM coverage and retired repo-local MDM docs on 2026-03-30