public active Last verified 2026-03-31

Topolo Social Studio

Public overview of the hybrid desktop and Cloudflare runtime used for AI-assisted social content planning and generation.

Owners
socialize
Source Repos
Applications/topolo-social-studio
Systems
Topolo Auth, Topolo Nexus, Topolo Social Studio
Tags
desktop, social, generation, creative

What It Is

Topolo Social Studio is a hybrid desktop and web production surface for planning, generating, and managing social-first creative work.

Architecture

The system combines a marketing/web shell, an authenticated API worker, a queue worker for generation orchestration, and a macOS desktop shell. Auth manages identity and Nexus now owns the external AI provider invocation path.

Runtime Surfaces

The primary public surface is https://studio.topolo.app, backed by Cloudflare-hosted worker runtimes and a local desktop shell for creator workflows.

API Reference

Use /systems/topolo-social-studio for the current runtime and worker route inventory. Provider-facing AI operations are invoked through Nexus rather than documented as direct vendor contracts here.

Auth and Permissions

Studio relies on Topolo Auth for session verification and workspace access. Its web and desktop shells now use the shared Topolo browser auth client through a thin application wrapper, including service-aware cookie refresh and logout propagation. AI-assisted routes preserve org and user attribution when they invoke Nexus-backed provider workflows.

Data Ownership

Studio owns workspaces, projects, briefs, creative plans, scenes, assets, and generation state. Nexus owns the provider keys and platform-level usage attribution for supported AI vendors.

Deployments

Studio deploys as a hybrid surface with separate marketing/web, API worker, queue worker, and desktop packaging flows.

Failure Modes

  • auth context missing for protected workspace routes
  • queue worker unavailable for generation processing
  • Nexus connectivity or provider configuration missing for AI-assisted planning or generation

Debugging

Start with /systems/topolo-social-studio for deployment and runtime detail. If AI planning or generation fails, verify the app can reach Nexus and that the expected org/user context is being forwarded.

Change Log / Verification

  • Standardized Social Studio browser auth on the shared Topolo auth client on 2026-03-31
  • Added canonical system coverage and documented the Nexus-backed AI integration path on 2026-03-29