MGT Studio
One platform. Four modules. Every system I've built now runs under a single roof — video clipping, content automation, agent orchestration, and ops all unified into 26 clean routes.
26
Routes
4
Backends synced
20+
Agents deployed
Beta
Current status
What It Does
AI Video Clipping
Upload long-form footage and get back short-form clips automatically. The pipeline handles detection, trim points, and export.
Factory Module (/factory)
Content automation microservice integrated directly into Studio. Ingestion, transformation, and distribution — all wired up.
Mission Control (/control)
Full agent orchestration panel. Dispatch Claude agents, monitor runs, and route outputs — all from one dashboard.
Ops Dashboard (/ops)
System health, pipeline status, error logs, and deployment controls migrated from the legacy MGT Suite.
Feature Flags
ENABLED_MODULES env variable controls which route groups activate. Each module can be toggled independently in prod.
Multi-Service Scripts
One command starts or stops all 4 backends. No hunting for processes. No manual port juggling.
The Architecture
One frontend. Four microservices.
Studio, Factory, Mission Control, and the legacy Suite were separate apps talking past each other. I unified them — one Next.js frontend with route groups, four backend microservices with synced ports and shared secrets.
Feature flags via ENABLED_MODULES mean I can ship modules independently without touching the rest of the platform.
Tech Stack
Next.js 15TypeScriptTailwind CSS v44 backend microservicesFeature-flag routingWebSocket agent commsVercel
Related
Want early access?
Studio is in active beta. Follow the build in Discord or book a call to discuss a custom deployment.