public active Last verified 2026-03-29

Topolo Studio

Public overview of the legacy studio/media-generation surface that now standardizes AI provider access through Nexus.

What It Is

Topolo Studio is the legacy studio/media-generation application surface currently maintained in its own repo alongside Showcase-era branding.

Architecture

The runtime is a Cloudflare-backed worker and web surface for media-generation workflows, with Auth for identity and Nexus as the standard provider-key ownership layer for outbound AI integrations.

Runtime Surfaces

See /systems/topolo-studio for the current runtime inventory and deployment entrypoints.

API Reference

Use /systems/topolo-studio for the current runtime inventory. Future outbound AI provider integrations should be described through the Nexus contract rather than direct vendor APIs in this app doc.

Auth and Permissions

Studio depends on Topolo Auth for identity and should not own long-lived AI provider keys directly.

Data Ownership

Studio owns its own application data and runtime behavior. Nexus owns the external AI provider credentials and cross-app attribution layer for supported vendor calls.

Deployments

Studio deploys as a worker/API surface plus a web shell using the repo-local Wrangler and build scripts.

Failure Modes

  • stale worker configuration copied from older Showcase-era deployment patterns
  • drift between worker config and the current Nexus standard

Debugging

Start with /systems/topolo-studio and verify the deployment config points at Nexus-backed provider access rather than app-local provider secrets.

Change Log / Verification

  • Added canonical system coverage and documented the Nexus standard for this legacy studio surface on 2026-03-29