Documentation

Install the CLI. Drive the stack.

Install the umbrella sys9 CLI, then choose a guide below. The launcher installs supported tools on demand; authentication and workspace setup belong to each product.

terminal

# 1 · install the umbrella CLI
$ npm i -g @sys9/cli

# 2 · see the tools it manages
$ sys9 status

# 3 · create a database and run SQL
$ sys9 db create --name my-app
$ sys9 db sql my-app -q "SELECT 1"

# 4 · inspect run9 authentication before using compute
$ sys9 run auth login --help

Start by product

Sandboxes · run9 Quickstart: sign in, create a Box, execute a command, and work with Snaps. Postgres database · db9 Quickstart: create a database and run SQL. The overview covers branching and file storage. Object storage · drive9 Official README: platform installation, workspace setup, files, search, and vault grants. Agent memory · mem9 Setup and runtime integrations. Use the API reference for custom clients. Agent transcripts · owl9 Official runtime plugins. Configure your own private space before the first transcript upload. Agent runtime · smith9 Product setup: authenticate, configure a provider, create an Env and Session, and submit a Turn. Teamwork · chord9 Open the workbench: sign in, connect a local Host or use cloud execution, and start a Session. Queues · task9 Product setup: choose a unique space and worker identity before creating and claiming tasks. Realtime · inbox9 · pulse9 · tape9 Product setup for inbox9, pulse9, and tape9, including credentials and message acknowledgements.

Reference and setup details

db9 overview · mem9 API reference · owl9 space and capture setup · chord9 local and cloud workflow

smith9 currently manages Codex, Claude Code, Gemini, Pi, and OpenCode runtimes after provider configuration. chord9 has its own runtime catalog; Pi there is Experimental and must be enabled.

For private transcript and message spaces, configure a unique space and its secret before the first request. For compute, complete the product login and select the correct project. See each guide for limits and retention.

Planned products

These pages describe planned directions, not currently available APIs or CLI commands:

web9 · planned Browser — scope and release timing are not finalized. vault9 · planned Secrets — scope and release timing are not finalized. gate9 · planned Model gateway — scope and release timing are not finalized. hub9 · planned Skills & tools — scope and release timing are not finalized. eval9 · planned Evals — scope and release timing are not finalized. cron9 · planned Scheduling — scope and release timing are not finalized. auth9 · planned Auth — scope and release timing are not finalized.

For AI agents

Agents use the same CLI and product credentials. Start with --help; use JSON only on commands that document structured output. Interactive and streaming commands have different output contracts:

Install @sys9/cli from npm, then run sys9 --help

Need something that isn't here yet? x@db9.ai or contact us.