Manage
CLI
Last updated January 2026
Create and deploy projects from the command line. The CLI works from an infra.json, the declarative definition of your infrastructure, so it pairs naturally with your editor and your coding agent.
Installation
$curl http://spawned.sh | bashA typical workflow
spawned login # authenticate
spawned init my-project # create a project
# Ask coding agent to use the Spawned CLI to configure your projects infrastructure
spawned get my-project # view the project and its outputsapply uploads the infra.json from the current directory unless you point it elsewhere. Most commands accept a project as name, org/name, or id.
Commands
| Command | Description |
|---|---|
init | Create a new project and write a starter infra.json |
validate | Validate an infra.json without applying it |
apply | Apply an infra.json to a project to provision it |
list | List your projects |
get | Get a project and its deployment outputs |
logs | Stream runtime logs from a component |
builds | List a project’s builds and view build logs |
upload | Upload a file to a Bucket component |
export | Export a project’s generated files |
schema | Print the infrastructure schema as JSON |
accounts | Manage connected cloud accounts |
cluster | Manage Kubernetes clusters |
org | Manage organizations |
apikeys | Manage API keys |
repos | List GitHub repos available through the GitHub App |
config | Manage CLI defaults |
login, logout | Sign in and out of Spawned |
Many commands have subcommands and options. Run spawned <command> --help for details.
Flags
| Flag | Description |
|---|---|
-h, —help | Help for a command |
—org <slug> | Scope the command to an organization |
-v, —version | Show the CLI version |