Topolo Device Platform
Topolo platform-owned TopoloFeed delivery, analytics, Android playback, and device-side app-catalog consumption surfaces.
Documentation Map
What It Is
Topolo platform-owned TopoloFeed delivery, analytics, Android playback, and device-side app-catalog consumption surfaces.
Architecture
Owners: device-platform
Source repos:
Dependencies: topolo-auth, topolo-mdm, topolo-developers
Repo shape
No repo surface entries were detected from the registered repo paths.
Runtime Surfaces
Hosts:
https://feed-api.topolo.app https://topolo-feed-assets.topolo.app https://feed-analytics-api.topolo.app https://feed-api.stg.topolo.us https://feed-analytics-api.stg.topolo.us No wrangler surface was discovered under the registered repo paths.
API Reference
Coverage: curated
Source: PlatformApplications/TopoloDocs/src/content/public/applications/device-platform.mdx
Source exists in repo: no
Canonical device-platform coverage lives in the docs application. TopoloFeed contains the feed delivery API, feed asset host, feed operator UI, Android playback runtime, and feed analytics worker. Feed delivery is the callable platform service slug `topolo-feed`, with `feed` retained as a registry alias, at https://feed-api.topolo.app; feed media assets are served from the `topolo-feed-assets` R2 bucket at https://topolo-feed-assets.topolo.app; and feed analytics remains a deploy target for device telemetry at https://feed-analytics-api.topolo.app. The Topolo-owned staging mirror uses https://feed-api.stg.topolo.us and https://feed-analytics-api.stg.topolo.us. TopoloMDM owns device management and Android provisioning. Mobile app catalog metadata belongs to Topolo Developers and is consumed through Developers-owned /api/apps routes. The former Nodo Host Network Pages site at https://nodo.topolo.io is retired, while retained Nodo-origin mobile surfaces are represented in Developers as first-party Topolo Feed, Topolo Provision, and Topolo MDM Mobile records.
App API page: /reference/apps/topolo-device-platform
This system currently relies on a curated or README-derived contract surface instead of a source-controlled OpenAPI spec.
Auth and Permissions
Depends on Topolo Auth: yes
Service IDs:
srv_IgInB3xJeF5x API key scopes
View feed engagement and analytics
Resource pattern: none
View feed entries and aggregations
Resource pattern: none
Publish and update feed entries
Resource pattern: none
Service permissions
analytics:read, feed:read, feed:write
Data Ownership
No storage bindings were derived from wrangler configuration.
Queues / Cron / Workflows
Queue bindings:
No queue bindings were detected.
Cron triggers
No cron triggers were detected.
Workflow signals
No explicit queue/workflow script or cron signal was discovered.
Environment Variables and Bindings
Environment variables:
No environment variables were derived from wrangler configuration.
All wrangler bindings
No bindings were derived from wrangler configuration.
Deployments
Deployment environments: default only or not declared
Routes: workers.dev or Pages-only delivery
Observability enabled: no explicit setting found
Failure Modes
- No wrangler.toml surface was discovered under the registered repo paths.
- The registered contract source is missing: PlatformApplications/TopoloDocs/src/content/public/applications/device-platform.mdx
- Neither OpenAPI nor README-derived interface detail was found.
Debugging Runbooks
Start with these entrypoints:
- PlatformApplications/TopoloDocs/src/content/public/applications/device-platform.mdx
Change Log / Verification
Lifecycle: active
Last verified: 2026-05-14
Any code change to this system is expected to update the canonical docs in PlatformApplications/TopoloDocs and refresh the verification date.