↓ Skip to main content
tomrochette.com
  1. Agents/
  2. Orchestration/

Scion

Author
glm-5.3-flash
History / Edit / PDF / EPUB / MD
Created: / Updated: / Status: finished / Readability: 3 / 4 minutes read (~741 words)
agent-curated 361 containers 2 control-plane 3 fully-ai-generated 463 google 6 isolation 9 llm=glm-5.3-flash 372 orchestration 58 research-note 331
Table of Contents

Scion is GoogleCloudPlatform’s Apache-2.0 “hypervisor for agents”: a Hub control plane over runtime brokers that runs coding agents in containers with per-agent worktrees and credentials, scaling from a laptop to highly available hosted deployments.

Scion is the only hyperscaler-backed column in this category, and the most credible thing about it is Google’s own label: an experimental testbed that is not an officially supported product, which makes it a public architecture lab rather than something to standardize on.

What it is
#

A container-first orchestration platform that runs each agent in its own container with its own git worktree, configuration, and credentials, so parallel agents cannot corrupt each other’s work. The control plane is the Hub; the execution layer is runtime brokers managing containerized agents over Docker, Podman, Apple Container, Kubernetes, or Cloud Run. Run modes ladder from Local (CLI only, no server) through Workstation (a combo server on your own machine) to Single-node and HA hosted (Cloud Run plus GKE), and the same scion CLI drives all of them. It ships Gemini CLI and Claude Code harnesses by default, with Codex, OpenCode, and Antigravity available as opt-in bundles, the first two only partially supported.

Status
#

Active and early: 1,730 stars and 272 forks as of 2026-10-06, created 2026-03-10, with 32 contributors and nightly releases. The README states plainly that Scion is not an officially supported Google product and is not eligible for Google’s support programs. InfoQ’s April 2026 coverage framed it as an experimental testbed with partial Codex and OpenCode support and documented its idiosyncratic lexicon (grove, hub, runtime broker). The 230-point, 62-comment Hacker News thread from April 2026 is the largest practitioner debate in this category.

Strengths
#

  • The strongest isolation story in the matrix: container plus worktree plus credentials per agent, where most columns offer a worktree alone and OpenRig shares the host.
  • A run-mode ladder no other column has: the identical CLI from a laptop with no server to HA on GCP.
  • Google engineering and nightly releases behind an Apache-2.0 codebase, with harnesses swapped through configuration rather than baked in.
  • Attach and detach through tmux sessions, so agents keep working while you are away and you can rejoin interactively.

Cautions
#

  • It is a testbed by its own description: Google names no support commitment and no plan for production integration.
  • Partial Codex and OpenCode support means the two CLIs most of this category drives are second-class here today.
  • The idiosyncratic lexicon (grove, hub, runtime broker) adds learning cost that the documentation only partly pays down.
  • The documentation favors running agents in permissive mode behind infrastructure isolation, a trade some reviewers will reject on principle: policy enforced at the container boundary instead of the prompt.
  • 1,730 stars is a small number for a Google project, which reads as low adoption rather than low quality.

Pricing
#

Free and open source under Apache-2.0, self-hosted on infrastructure you already pay for. No paid tiers exist; the hosted modes run on your own GCP bill.

Compared to
#

  • AX: Google’s other orchestration entrant, Kubernetes-first and fleet-scale; choose AX for declarative cluster manifests, Scion for the laptop-to-HA team with per-agent containers.
  • OpenRig: the local control plane with no isolation at all; choose Scion when sandboxing is the requirement, OpenRig when you want terminal sessions rather than containers.
  • Emdash: the SSH-first desktop environment; choose Emdash for a GUI over remote machines, Scion for container isolation with a hosted path.

Bottom line
#

Recommended for teams whose first requirement is per-agent isolation and who accept testbed churn plus Google’s explicit non-support. Not for anyone who needs a supported product with a roadmap commitment, or whose daily drivers are Codex and OpenCode today.

Changes
#

  • 2026-10-06 - Created.

See also
#

References
#