Content Extend is the working name for OpenTechnologyApp's built-in Extend Platform — Stream + Content Ops project template — a tracking and control-plane layer for the tools actually running on your machines: OBS, ComfyUI, Blender, Krita, NodeCG, and the Docker/Postgres/Redis backing stack.
It ships today as one of the app's five built-in templates — pick it from the template picker at project creation, no JSON import or setup required.
What it tracks
Twelve queues, one per concern:
| Queue | What lives there |
|---|---|
| Machines & Bridges | One row per host — what's installed, its health, when it last reported in |
| Tool & Service Inventory | Per-tool install status, version, and health (OBS, ComfyUI, Blender, Krita, NodeCG, Docker, and more) |
| Health Checks | Every monitored metric as a tracked item, grouped by tier and run status |
| Control Commands | Allowlisted actions (scene switches, service restarts) with an approval/lease/run state machine |
| Stream Scenes & Sources | Desired vs. actual state for OBS scenes and sources |
| Content Workflows | Versioned ComfyUI/Blender workflow definitions |
| Content & Render Jobs | One item per render run, grouped by pipeline stage, failures get flagged automatically |
| Asset & Model Library | Checkpoints, overlays, and other output assets with license/attribution metadata |
| Incidents | Post-mortems, linked back to the health check that caught them |
| Daily Reports / Weekly Reports | One rollup item per cycle |
| Setup & Change Runs | Install/upgrade history with rollback notes |
Checks in three tiers
- T1 — Broadcast: continuous checks while you're live (stream vitals, broadcast graphics)
- T2 — Pipeline: render-queue depth, GPU/VRAM pressure, job failures
- T3 — Infra: backing services, storage, tool version drift
Every check item carries a tier and a run status (Pass / Flagged / Error / Not Run / Disabled), so a triage pass is a filtered queue view, not a spreadsheet.
What ships automated today
Four automations come with the template — modest, but real:
- A flagged health check gets bumped to high priority automatically
- A completed control command marks itself done
- A critical incident gets bumped to urgent
- A failed render job gets bumped to high priority
There's no fancier orchestration wired in yet — no auto-pause-render-while-live rule, no outbound Slack notification. Those are reasonable follow-ups to build with the automation editor once you're using it for real; the template gives you the register and the fields to hang them on, not a finished rulebook.
The part you build yourself: the bridge
Everything above lives in OpenTechnologyApp. Getting live data in and commands back out to OBS, ComfyUI, or Blender needs a small bridge process on each machine — outbound-only, so it can poll for control events and push telemetry without opening an inbound port. The template's own seed data assumes this split explicitly: OpenTechnologyApp holds status and issues allowlisted commands; the bridge is what actually talks to your tools.
That bridge isn't a shipped, working script today. An earlier prototype exists in this blog's own content-management package, but it's a reference stub — it logs the OBS/ComfyUI calls it would make rather than making them. If you want this wired to real hardware, budget for writing that piece; the app-side tracking is the part that's actually done.
Playbooks
Unlike some of the other built-in templates (IT Device Audit ships five), Extend Platform doesn't come with playbooks yet. If you're the kind of team that wants a checked runbook for bridge setup or incident triage, that's a gap worth filling yourself for now — the queue/field structure is there to hang one on.
Get it
New Project → Extend Platform — Stream + Content Ops from the template picker at opentechnologyapp.com. You'll have all twelve queues, the four automations, and three dashboards (Operations Overview, Stream & Health Monitor, Content & Assets) — the tracking layer is ready. The bridge connecting it to your actual machines is the part you build next.