Content automation microservice that handles ingestion, transformation, and distribution. Wired directly into MGT Studio as the /factory module — one backend powering the full content pipeline.
1
Dedicated microservice
/factory
Studio route group
Beta
Current status
100%
Solo built
What It Does
Accepts raw content from multiple sources — video files, text, metadata — and normalizes it into a unified pipeline format.
Processes ingested content through configurable steps: transcoding, thumbnail generation, metadata extraction, and format conversion.
Routes finished content to its destination — platform uploads, CDN delivery, or webhook-triggered downstream services.
Runs as a route group inside MGT Studio. The frontend lives at /factory, giving operators full visibility into pipeline status.
Every pipeline stage fires webhooks on completion. External services can subscribe to events and react in real time.
Factory runs as its own backend process with a dedicated port. It shares secrets with Studio but can be deployed and scaled independently.
How It Fits
Factory started as a standalone backend called ClawFactory. When I unified everything into MGT Studio, Factory became the /factory route group on the frontend while keeping its own backend process and port.
It shares secrets and environment variables with Studio, but runs in its own process. The ecosystem start/stop scripts manage all four backends together — no manual port juggling.
Tech Stack
Pipeline Stages
Factory is in active beta as part of MGT Studio. Follow the build in Discord or book a call to discuss content automation for your workflow.