Topolo Device Platform

Public overview of Topolo's device distribution, feed delivery, analytics, Android playback, and provisioning surfaces.

publicverified 2026-08-01device-platformdevicesfeeds

What It Is

Topolo Device Platform is a family of Topolo-owned surfaces for feed delivery, feed media assets, feed analytics, Android playback, TopoloMDM-owned Android provisioning, and device-side consumption of Developers-owned app catalog metadata.

Architecture

The product family spans several first-class PlatformApplications roots rather than one unified application. TopoloFeed owns feed delivery, feed media assets, feed operator UI, Android playback, and feed analytics under apps/TopoloFeed. TopoloMDM owns device management and Android provisioning. Topolo Developers owns the Android and iOS app-catalog metadata that device install flows consume. The retained Nodo-origin mobile surfaces now appear as Topolo-owned mobile apps in the Developers workspace: Topolo Feed, Topolo Provision, and Topolo MDM Mobile.

Runtime Surfaces

Use /systems/topolo-device-platform for the current inventory of host acquisition, workers, UIs, and Android surfaces.

API Reference

The active contracts are curated in the docs platform and include TopoloFeed's https://feed-api.topolo.app feed worker, https://topolo-feed-assets.topolo.app media asset host, https://feed-analytics-api.topolo.app telemetry worker, Developers-owned /api/apps mobile artifact listings, and the Android consumers that depend on them.

Auth and Permissions

Auth expectations vary by surface. Some workers are lightweight delivery or analytics endpoints, while admin and provisioning flows should align with broader platform standards.

Devices sign in with their own credential rather than a person's account, and that credential can be rotated for a single device without disturbing the rest of the fleet.

Data Ownership

Device-platform surfaces own feed configuration, feed analytics, playback state, and provisioning-related artifacts depending on the subcomponent. Feed-specific delivery belongs inside TopoloFeed; mobile app listing and distribution metadata belongs inside Topolo Developers.

Device-identifying values held by Feed are encrypted at rest and scoped to your organization.

Mobile Experience

The checked-in mobile experience contract is approved in native_capability mode. Its fallback route is /dashboard/devices, its offline policy is read_through_cache, and it requires organization context.

Published permissions: feed:read.

  • /dashboard/devices uses /api/widget with the record.list template and feed.devices.list data source.
  • /dashboard/media uses /api/widget with the record.detail template and feed.media.detail data source.

The native clients consume this manifest as an explicit rendering contract. A web mode record intentionally opens the product web experience; native_capability publishes the listed native routes and actions. Do not infer unlisted native behavior.

Deployments

Treat Topolo Device Platform as a retained product family with several separately deployable surfaces rather than a single product runtime. The callable platform service registry exposes feed delivery through the stable topolo-feed service slug, with feed retained as a registry alias; feed analytics remains a device telemetry surface, and feed media assets are served from TopoloFeed's topolo-feed-assets R2 bucket. The former Nodo host-acquisition Pages site is retired and no longer has an active Cloudflare deployment.

Failure Modes

  • the product family is documented as if it were one coherent app
  • retired host-acquisition copy is reintroduced as an active runtime surface
  • provisioning, feed delivery, and analytics responsibilities are conflated
  • lifecycle maturity is overstated for the provisioning branch
  • mobile app catalog ownership is reintroduced as a separate device-platform API instead of staying in Developers

Debugging

Start with /systems/topolo-device-platform, then identify the exact sub-surface before debugging or documenting behavior.

Use It

Open Topolo Device Platform for the human product surface. The system handbook records its current hosts, ownership, Auth scopes, storage, deployment, failure modes, and machine artifact.

Discover the credential-scoped automation surface before making an API call:

topolo services --query topolo-device-platform --json
topolo actions --service topolo-device-platform --json
topolo actions capabilities --service topolo-device-platform --json

Choose an action, inspect it with topolo actions get <action-id> --json, then validate and plan a published example. The Agent Actions reference exposes the same public schemas, effects, examples, verification, and recovery guidance.

Example workflow:

  1. Confirm the active identity and organization with topolo whoami --json.
  2. Discover Topolo Device Platform and select one published action rather than guessing a route.
  3. Inspect its input/output schemas and published example.
  4. Validate and plan the exact payload; obtain confirmation for a mutation.
  5. Execute and perform every published verification step.

Change Log / Verification

  • Reconciled this page against apps/TopoloFeed origin/staging e157a439a3f2 on 2026-08-01 after reading a2ac292 (feat: close Feed enterprise privacy and device auth). Recorded per-device credentials with single-device rotation and at-rest protection of device-identifying values. No surface boundary changed.

  • Verified the native_capability mobile experience contract and its 2 published route(s) against apps/TopoloFeed origin/staging d6b87c5d8495 on 2026-07-27.

  • Reconciled this page against apps/TopoloFeed origin/staging d57457e4594f on 2026-07-24 after reviewing every docs-relevant commit since its previous verification watermark. Dependency-only currency commits were checked by the fleet production-dependency gate and did not change this page's product contract.

  • Consolidated TopoloFeed browser administration onto the live shared-shell operator console on 2026-07-11 and removed the undeployed mock API Explorer from the workspace build graph.

  • Reconciled workspace verification on 2026-06-28 against apps/TopoloFeed commits through f50a827; reviewed 211 commits since 2026-05-27, including f50a827 chore(deps): refresh @topolo-io/app-shell pins (package.json + lockfile); 88626af Stop blocking startup on i18n readiness; 4d3f170 Adopt canonical Topolo typography; 2073b78 Lazy load Feed startup surfaces.

  • Retired the Nodo host-acquisition Cloudflare Pages surface on 2026-05-10.

  • Moved TopoloFeed media delivery onto the Topolo-named topolo-feed-assets R2 bucket on 2026-04-23.

  • Added the Nodo host-acquisition website surface at nodo.topolo.io on 2026-05-02.

  • Added the TopoloFeed asset host and clarified TopoloFeed/TopoloMDM ownership boundaries on 2026-04-23.

  • Re-established the TopoloFeed production hosts and callable feed service registry entry on 2026-04-23.

  • Registered retained mobile surfaces as first-party Topolo app records in Developers on 2026-04-23.

  • Moved mobile app catalog ownership from the standalone AppLibrary API into Topolo Developers on 2026-04-22.

  • Folded the feed API and operator UI into apps/TopoloFeed on 2026-04-22

  • Promoted the retained app-library, feed API, and feed runtime repos to first-class PlatformApplications/* roots on 2026-04-22

  • Renamed the feed runtime container to TopoloFeed on 2026-04-22

  • Added canonical device-platform coverage and retired repo-local cluster docs on 2026-03-30