Autonomous Video Studios
HomePART III · ChannelForge
CHAPTER 15 · CHANNELFORGE

Multi-tenancy, security and isolation

A SaaS that runs customers' code-generating agents on shared GPUs must keep tenants apart at every layer. ChannelForge does this by design, not by convention.

  • Workspaces, projects, teams and roles. Every row carries its workspace; teams restrict which projects a member sees; API keys can only be made by owners and admins and carry scopes.
  • GPU job sandboxes. Each job runs as its own slot user in a private folder no other job can enter. Its network is loopback only — its own tunnels to the model gateway and the voice service; no DNS, no internet — and no job can reach the cloud's metadata service or private networks. A film runs alone on its box, behind a default-deny rule.
  • No secrets on GPU boxes. The boxes hold no tenant secret and no model key: every model call goes through the gateway, which holds the one real credential and meters and caps each job.
  • Safe outbound calls. Addresses a tenant chooses — webhooks, Bluesky hosts — are reached only over HTTPS, only at public addresses, and redirects are never followed (no server-side request forgery).
  • Privacy. A deleted workspace's platform tokens and data are purged 144 hours after the deletion; the YouTube data of a disconnected or refused account is purged on YouTube's own schedule.
  • Abuse controls. Trial credits are not given to disposable e-mail addresses, and trials are capped per network.
  • Posting guard. After a database restore the guard arms itself and every account is read before its next post, so nothing posts twice.
  • Accounts. Every new password is checked offline against 100,000 known-leaked ones; a workspace can require two-factor sign-in for all its members; staff capabilities are checked by every admin action.
  • Data at rest. The key that seals tenants' platform tokens rotates, with background re-sealing; fetches of addresses a member gives are pinned against DNS rebinding; a member can download all their data, checked against the whole schema.
  • Proven, not assumed. A planted-defects harness hides deliberate bugs in a copy of the code and checks the tests catch them — 13 of 13 on 8 November — and a guard refuses destructive database commands on production.
  • Operator controls. An admin console — 42 pages — shows the GPU fleet, model spend, jobs, incidents, publishing failures, finance and the append-only audit log.
Figure 30. Connections: a workspace links its own platform accounts, each with its health (development build, demonstration data).