The whole stack, at a glance.
Every sys9 product and the capability it gives you, on one page. A stack of small, composable services, grouped by what they do — pick the ones you need and compose them into real systems.
Run agents and their code.
run9
availableCreate Linux Boxes from images or filesystem Snaps. Fork one Snap at a time; persistent Volumes are separate. Execute through the CLI or SSH, within project quotas.
Explore run9 →smith9
availableHosted agent Envs and persistent Sessions on run9. Configure a provider, then submit Turns; an Env can inherit project provider settings or override them.
Explore smith9 →web9
plannedPlanned managed browser sessions for agent workloads. Product scope and release timing are not finalized.
Explore web9 →Store state, files, memory, and secrets.
db9
availableServerless Postgres with database branching and built-in file storage. Create and query databases from the CLI with credentials scoped to your workload.
Explore db9 →drive9
availablePersistent files across sandboxes and sessions, with FUSE mounts, semantic file search, and explicit vault grants. Configure the context used by each agent.
Explore drive9 →mem9
availablePersistent memory across supported agents and sessions, with tools to inspect, import, and export it. Follow the runtime integration or API setup guide.
Explore mem9 →vault9
plannedPlanned standalone credential management. Current run9 managed egress and drive9 vault grants have separate security boundaries.
Explore vault9 →Models, tools, and quality.
gate9
plannedPlanned model gateway for routing and provider configuration. Product scope and release timing are not finalized.
Explore gate9 →hub9
plannedPlanned registry for agent skills and tools. Product scope and release timing are not finalized.
Explore hub9 →eval9
plannedPlanned evaluation tools for agent workloads. Product scope and release timing are not finalized.
Explore eval9 →Make agents work together.
task9
availableShared tasks with dependencies and atomic claims. Optional pulse9 owner-liveness releases offline owners during subsequent task reads or claims.
Explore task9 →Realtime
availableinbox9 messages, pulse9 worker leases, and tape9 append-only logs. Configure each service and implement scheduling, acknowledgements, and recovery in your application.
Explore inbox9 · pulse9 · tape9 →chord9
availableA workbench for native coding-agent Sessions on local or cloud Hosts. Organize work in Workspaces and Projects, continue conversations, and share artifacts.
Explore chord9 →cron9
plannedPlanned scheduling and event triggers for agent workloads. Product scope and release timing are not finalized.
Explore cron9 →See what ran and who can act.
owl9
availableCapture native sessions and linked sub-sessions after configuring a supported runtime integration and space. Enable collection for the sessions you choose.
Explore owl9 →auth9
plannedPlanned identity service. Continue using current product authentication and application authorization.
Explore auth9 →sys9 CLI — one entry point for supported tools.
The umbrella sys9 CLI installs supported tools on first use.
Use sys9 run, sys9 db, and other listed subcommands.
Individual tools have their own setup; managed db9 and drive9 binaries are not automatically added to your PATH.
npm install -g @sys9/cli sys9 status sys9 db create --name my-app sys9 db sql my-app -q "SELECT 1" # Inspect run9 login requirements before creating a Box sys9 run auth login --help
Compose the stack into your system.
Install the CLI and follow product-specific setup. run9, smith9, and chord9 require authentication; private spaces need credentials before first use.