CLI reference
The nimbus binary is the entire product surface: server, dev loop, deploy
client, codegen, and operator tooling ship as one executable. Every command
requires an explicit subcommand — there is no default action.
nimbus <command> [subcommand] [flags]| Command | What it does |
|---|---|
start | Start a Nimbus server in the foreground |
dev | Start a local development server with watched codegen |
deploy | Push app artifacts to a self-hosted Nimbus instance |
run | Invoke functions and reserve target-scoped workload execution |
target | Manage the named-target registry |
explain | Explain effective configuration and runtime admission |
validate | Validate project config or policy |
list | List Nimbus resources |
sandbox | Reserve target-scoped sandbox lifecycle commands |
codegen | Generate app artifacts from nimbus/ or convex/ source |
init | Scaffold a new Nimbus project |
kv | Run the loopback RESP (Redis) KV listener |
object-storage | Administer the object byte plane |
token | Local admin token management |
backup | Offline backup and restore of the local data directory |
auth | Console sign-in URLs and remote deploy credentials |
ui | Open the operator console in a browser |
machine | Manage local developer machines (macOS Linux guest) |
node | Install and manage node service-manager artifacts |
compose | Compose-backed local service lifecycle |
policy | Validate and explain operator policy files |
encryption | At-rest encryption admin operations |
packages | Provision embedded Nimbus JS packages into an app |
For what each surface currently supports, see Current capabilities.
nimbus start
Section titled “nimbus start”nimbus start [flags]Starts a Nimbus server in the foreground. Binds loopback by default; pass
--allow-network (after rotating the local admin token) to bind a
non-loopback interface. With --app-dir it runs one codegen preflight and
serves that app; without it, the server starts empty and waits for deploys
through the admin API. See Self-host for the
deployment walkthrough.
Most-used flags:
| Flag | Env var | Default | What it does |
|---|---|---|---|
--port | — | 8080 | Port to listen on. |
--host | — | 127.0.0.1 | Host interface to listen on; defaults to loopback for local safety. |
--allow-network | — | false | Opt in to binding a non-loopback interface; requires an explicitly rotated local admin token (nimbus auth rotate-admin). |
--cors-allow-origin | NIMBUS_CORS_ALLOW_ORIGINS | loopback only | Additional allowed browser origin for CORS (repeatable; env var is comma-separated). Exact match; wildcards rejected. |
--data-dir | NIMBUS_DATA_DIR | ./data | Local data directory for embedded tenant databases and, by default, the control plane. |
--tenant-provider | NIMBUS_TENANT_PROVIDER | sqlite | Tenant persistence provider: sqlite, libsql-replica, redb, postgres, or mysql. |
--config | NIMBUS_CONFIG | unset | Optional YAML or JSON config file; CLI flags override env vars, which override file values. Without it, Nimbus also auto-discovers ./nimbus.yaml. |
The protocol adapters — Firestore and Cloudflare routes on the main
listener, plus the MongoDB, DynamoDB, and S3 wire listeners on 27017,
8000, and 9000 — are served by default; a busy conventional port skips
that listener with a warning. --no-firestore, --no-cloudflare,
--no-mongodb, --no-dynamodb, and --no-s3 switch a surface off,
--mongodb-port / --dynamodb-port / --s3-port pin an explicit port
(busy is then a hard error), and credentials come from the generated
wire-credentials.json in the data directory unless overridden —
--mongodb-username with the env-only NIMBUS_MONGODB_PASSWORD, repeatable
--dynamodb-access-key KEY_ID:SECRET:TENANT or NIMBUS_DYNAMODB_ACCESS_KEYS,
and repeatable --s3-access-key KEY_ID:SECRET:TENANT or
NIMBUS_S3_ACCESS_KEYS.
nimbus start accepts further flag families — TLS termination
(--tls-cert + --tls-key), app loading (--app-dir,
--skip-codegen, --debug-node-apis), Compose services (--compose-file),
systemd socket activation (--systemd-socket-activation), licensing
(--license-file, falling back to NIMBUS_LICENSE_FILE then
~/.config/nimbus/license.json), per-provider storage settings
(--libsql-*, --postgres-*, --mysql-*), runtime limits
(--runtime-heap-mb, --runtime-timeout-secs, and the other
--runtime-* flags), and at-rest encryption (--encryption-key-provider
and the other --encryption-* flags). The full flag ↔ environment variable ↔
config-key cross-reference lives in Configuration.
nimbus dev
Section titled “nimbus dev”nimbus dev [flags]Starts a local development server with dev defaults: watched codegen reruns,
local generation activation, an auto-created tenant (demo, or the
discovered Firebase project id for Firestore client apps), and automatic
browser launch of the operator console. When --app-dir is omitted, the app
directory is auto-detected by walking up from the current directory to the
nearest .git boundary. See Quickstart.
Adapter detection is automatic. nimbus dev reads the app’s
package.json and sources to pick the adapter (Convex, Cloud Functions,
or the Firestore client wiring), writes Nimbus-owned NIMBUS_* keys to
the app’s .env.local when it detects the mongodb or
@aws-sdk/client-dynamodb driver, and re-runs detection live when
package.json changes — an adapter added mid-session is adopted without
a restart. The server keeps serving even when no adapter is detected.
| Flag | Env var | Default | What it does |
|---|---|---|---|
--port | — | 3210 | Port to listen on. |
--app-dir | — | auto-detected | App directory containing an adapter source root. |
--data-dir | — | <app-dir>/.nimbus/dev | Shared local dev persistence root for tenant data and control state. |
--compose-file | COMPOSE_FILE | discovered | Ordered Compose file list for local service dependencies; repeat to merge overlays. |
--once | — | false | Run startup only, without the watched codegen loop. |
--skip-codegen | — | false | Skip initial codegen before starting; watched reruns still use codegen. |
--debug-node-apis | — | false | Diagnose Node.js builtin imports that should move behind "use node". |
--tail-logs | — | pause-on-sync | Runtime log tailing mode: always, pause-on-sync, or disable. |
--no-open | — | false | Suppress the default browser auto-open and print a launch-URL banner instead. |
Browser auto-open is also suppressed automatically in non-interactive
environments ($CI or $NO_BROWSER set, or stdout is not a TTY).
nimbus deploy
Section titled “nimbus deploy”nimbus deploy [TARGET] [flags]Packages generated app artifacts and pushes them to a self-hosted Nimbus
instance, printing a diff of functions, HTTP routes, schema, and
runtime-bundle changes. The target resolves from the positional TARGET (a
URL or a configured target name) first, then the NIMBUS_TARGET /
NIMBUS_TARGET_URL environment variables, and defaults to the running local
server when omitted; the token resolves from --token, then
NIMBUS_DEPLOY_TOKEN, then tokens stored by nimbus auth login. The deploy route also requires the
server’s local admin token: when the target URL is a loopback address on
the same machine, nimbus deploy reads it from the local token file
automatically; for a remote server, pass --admin-token or set
NIMBUS_ADMIN_TOKEN. The server-side contract is documented in
Deploy & admin API.
| Argument / Flag | Env var | Default | What it does |
|---|---|---|---|
TARGET (positional) | NIMBUS_TARGET / NIMBUS_TARGET_URL | local server | URL or configured target name; omitted deploys to the running local server. |
--token | NIMBUS_DEPLOY_TOKEN | credentials file | Deploy admin bearer token. |
--admin-token | NIMBUS_ADMIN_TOKEN | local token file (loopback targets) | Local admin token sent as X-Nimbus-Admin-Token. |
--app-dir | — | auto-detected | App directory containing a nimbus/ or convex/ source root. |
--convex-silo | NIMBUS_CONVEX_SILO | — | Required for Convex artifacts. Binds the deployed auth configuration to exactly this trusted silo. |
--dry-run | — | false | Validate and diff without activating the new generation. |
--skip-codegen | — | false | Skip codegen and package already-generated artifacts. |
--verbose | — | false | Show packaging and deploy phase detail. |
nimbus run
Section titled “nimbus run”nimbus run [TARGET] functions <selector> [jsonArgs] [flags]Invokes a Nimbus function on a selected target. TARGET is one optional
positional: a URL (http/https), a configured target name (see
nimbus target), or omitted to discover the running local server.
NIMBUS_TARGET and NIMBUS_TARGET_URL are accepted as env fallbacks.
Most-used flags:
| Argument / Flag | Env var | Default | What it does |
|---|---|---|---|
TARGET (positional) | NIMBUS_TARGET / NIMBUS_TARGET_URL | local server | URL or configured target name; omitted resolves the running local server. |
--kind | — | inferred | Function kind: query, paginated-query, mutation, or action. |
--tenant | — | demo | Tenant id to invoke. |
--app | — | current directory | App directory used for generated function-kind inference. |
--config | — | unset | Path to nimbus.yaml / nimbus.json for function-scaling admission. |
--policy | — | unset | Path to nimbus.policy.yaml for operator quota admission. |
nimbus run exec -- <argv...> is parsed as reserved vocabulary, but raw command
execution is not shipped yet. It resolves the target and then exits with an
actionable error instead of bypassing the service/sandbox/node workload-control
path.
nimbus target
Section titled “nimbus target”nimbus target <subcommand>Manages the named-target registry at ~/.config/nimbus/targets — the named
endpoints that deploy, run, sandbox, and list resolve instead of a
raw URL. Run nimbus target --help for the add, list, and remove
subcommands.
nimbus explain
Section titled “nimbus explain”nimbus explain [flags]Explains the effective Nimbus configuration and runtime admission decisions
for a target — how flags, environment, and config-file values resolve. Run
nimbus explain --help for its options.
nimbus validate
Section titled “nimbus validate”nimbus validate [flags]Validates a Nimbus project’s configuration or an operator policy file before
you apply it, reporting problems without starting a server. Run
nimbus validate --help for what it checks.
nimbus list
Section titled “nimbus list”nimbus list <resource>Lists Nimbus resources on a target, such as sandboxes and services. Run
nimbus list --help for the resource kinds it enumerates.
nimbus sandbox
Section titled “nimbus sandbox”nimbus sandbox create [TARGET] --template NAMEnimbus sandbox list [TARGET]Reserves the top-level sandbox resource namespace and target-resolution contract.
TARGET is one optional positional — a URL or a configured target name; omitted
resolves the running local server — exactly like nimbus run. The commands
parse and resolve targets through the same TargetContext seam as nimbus run,
then fail actionably until sandbox lifecycle execution is owned by the
service/sandbox/node workload-control path.
nimbus codegen
Section titled “nimbus codegen”nimbus codegen [--app <path>]Generates _generated/* files and the runtime bundle from a nimbus/ or
convex/ source root. Codegen is embedded in the binary — there is no
separate npm codegen step. See Developers for the authoring
workflow.
| Flag | Env var | Default | What it does |
|---|---|---|---|
--app | — | . | App directory containing a nimbus/ or convex/ source root. |
--debug-node-apis | — | false | Diagnose Node.js builtin imports that should move behind "use node". |
nimbus init
Section titled “nimbus init”nimbus init <adapter> [directory] [flags]Scaffolds a new Nimbus project. The adapter argument is required and selects the project template; existing files are never overwritten.
| Argument / flag | Env var | Default | What it does |
|---|---|---|---|
<adapter> | — | required | Adapter to scaffold: convex or cloud-functions. |
[directory] | — | . | Target directory, created if it does not exist. |
--source-root | — | convex | Source root directory name (convex adapter only). |
--install | — | false | Install adapter dependencies after scaffolding. |
nimbus kv
Section titled “nimbus kv”nimbus kv [flags]Runs a loopback RESP (Redis) listener speaking RESP2 and RESP3 on
127.0.0.1:6380. Authentication is mandatory and the listener serves one
tenant per credential; if no password is given (--password or
NIMBUS_KV_PASSWORD), a dev credential is generated and printed at startup.
The command surface and flags are documented in
KV (Redis) compatibility.
nimbus object-storage
Section titled “nimbus object-storage”nimbus object-storage <subcommand>Administers the object byte plane — the store the S3 adapter reads and writes
through. Subcommands cover placement policy (set-placement), the encryption
master key (bootstrap-master-key), garbage-collection and erasure health
(gc-status, erasure-status, erasure-heal), offline byte-plane backup and
restore (backup-object-store, restore-object-store), and destructive
per-tenant removal (tenant rm). The maintenance verbs are offline and fail
closed while a server is running. See
Object storage for the operator runbook.
nimbus token
Section titled “nimbus token”Local admin token management.
nimbus token rotate
Section titled “nimbus token rotate”nimbus token rotateRotates the local admin token used for localhost server access. When a live server is discoverable, rotation goes through the running server; otherwise it rotates the on-disk token file offline. Takes no flags.
nimbus backup
Section titled “nimbus backup”nimbus backup create --data-dir ./data --out <file>nimbus backup restore --in <file> --data-dir ./dataOffline whole-deployment backup and restore for the embedded providers
(--provider sqlite|redb): one point-in-time archive per tenant in a
single file, fingerprint-verified on restore. Run with the server
stopped; restore requires a fresh data directory. See
Backup & restore for procedures, encrypted
deployments, and external backends.
nimbus auth
Section titled “nimbus auth”Sign-in URLs for the local console and credentials for remote deploys.
nimbus auth url
Section titled “nimbus auth url”nimbus auth url [--copy] [--open]Mints a single-use launch URL for the local operator console. Requires a
running server (nimbus start or nimbus dev).
| Flag | Env var | Default | What it does |
|---|---|---|---|
--copy | — | false | Copy the launch URL to the OS clipboard in addition to printing it. |
--open | — | false | Open the launch URL in the default browser in addition to printing it. |
nimbus auth token
Section titled “nimbus auth token”nimbus auth token [--copy]Prints the local admin token from the on-disk token file.
| Flag | Env var | Default | What it does |
|---|---|---|---|
--copy | — | false | Copy the token to the OS clipboard in addition to printing it. |
nimbus auth login
Section titled “nimbus auth login”nimbus auth login --url <daemon-url> [--bearer <token>]Stores a deploy bearer token for a remote Nimbus daemon in the local
credentials file. nimbus deploy falls back to this store when
NIMBUS_DEPLOY_TOKEN is unset.
| Flag | Env var | Default | What it does |
|---|---|---|---|
--url | — | required | Daemon URL to authenticate against (e.g. https://nimbus.example.com). |
--bearer | — | stdin | Deploy bearer token; if omitted, read from stdin. |
nimbus auth status
Section titled “nimbus auth status”nimbus auth statusLists configured deploy connections with masked bearers and metadata. Takes no flags.
nimbus auth logout
Section titled “nimbus auth logout”nimbus auth logout --url <daemon-url>Removes a stored deploy bearer.
| Flag | Env var | Default | What it does |
|---|---|---|---|
--url | — | required | Daemon URL whose stored bearer should be removed. |
nimbus auth rotate-admin
Section titled “nimbus auth rotate-admin”nimbus auth rotate-adminRotates the local admin token offline. Required before
nimbus start --allow-network when the token has gone stale. A running
daemon keeps its in-memory token until restart. Takes no flags.
nimbus ui
Section titled “nimbus ui”nimbus uiDiscovers the running local daemon and opens the operator console in a
browser. It does not spawn a daemon — start one with nimbus start or
nimbus dev first. Takes no flags.
nimbus machine
Section titled “nimbus machine”Manages local developer machines — the Linux guest VM that backs container
workloads on macOS. Most subcommands take an optional machine [name]
positional that defaults to default.
nimbus machine init
Section titled “nimbus machine init”nimbus machine init [flags] [name]Initializes a new machine: writes its config and state records and records the guest resource contract.
| Flag | Env var | Default | What it does |
|---|---|---|---|
-c, --cpus | — | 2 | Number of CPUs. |
-m, --memory | — | 2048 | Memory in MiB. |
-d, --disk-size | — | 20 | Disk size in GiB. |
--image | — | release-pinned image | Machine OS image source. |
--identity | — | auto-generated | Path to the SSH identity for guest access. |
--ignition-path | — | unset | Legacy Ignition config file for explicit non-bootc image overrides. |
--firmware | — | unset | Path to the EFI variable store. |
-v, --volume | — | none | HOST:GUEST volume mount; repeatable. |
--now | — | false | Start the machine after initializing it. |
nimbus machine start
Section titled “nimbus machine start”nimbus machine start [flags] [name]Starts a machine, creating it first when it does not exist. Accepts the same
creation flags as machine init (--cpus, --memory, --disk-size,
--image, --identity, --ignition-path, --firmware, --volume), which
apply only when start creates the machine, plus:
| Flag | Env var | Default | What it does |
|---|---|---|---|
-q, --quiet | — | false | Suppress machine starting status output. |
--no-info | — | false | Suppress informational tips. |
nimbus machine stop
Section titled “nimbus machine stop”nimbus machine stop [name]Stops a running machine and persists the stopped state. No flags beyond the optional name.
nimbus machine status
Section titled “nimbus machine status”nimbus machine status [flags] [name]Displays machine status.
| Flag | Env var | Default | What it does |
|---|---|---|---|
-f, --format | — | table | Output format: json, yaml, or table. |
-q, --quiet | — | false | Print the machine name only. |
-n, --noheading | — | false | Omit table headings from table output. |
nimbus machine list
Section titled “nimbus machine list”nimbus machine list [flags]Lists initialized machines (alias: nimbus machine ls). The default machine
is marked with * in table output.
| Flag | Env var | Default | What it does |
|---|---|---|---|
-f, --format | — | table | Output format: json or table. |
-q, --quiet | — | false | Print machine names only. |
-n, --noheading | — | false | Omit table headings from table output. |
nimbus machine info
Section titled “nimbus machine info”nimbus machine info [-f <format>]Displays machine host info: roots, cache locations, and the current machine release.
| Flag | Env var | Default | What it does |
|---|---|---|---|
-f, --format | — | yaml | Output format: json or yaml. |
nimbus machine inspect
Section titled “nimbus machine inspect”nimbus machine inspect [-f <format>] [name]Prints the persisted machine record (config plus refreshed state).
| Flag | Env var | Default | What it does |
|---|---|---|---|
-f, --format | — | json | Output format: json or yaml. |
nimbus machine set
Section titled “nimbus machine set”nimbus machine set [flags] [name]Updates a stopped machine’s recorded resources; the next machine start
applies them.
| Flag | Env var | Default | What it does |
|---|---|---|---|
-c, --cpus | — | unchanged | Number of CPUs. |
-m, --memory | — | unchanged | Memory in MiB. |
-d, --disk-size | — | unchanged | Disk size in GiB. |
nimbus machine cp
Section titled “nimbus machine cp”nimbus machine cp [-q] <src-path> <dest-path>Securely copies files between the host and a machine. Guest endpoints use
NAME:/path notation (e.g. default:/tmp/file).
| Flag | Env var | Default | What it does |
|---|---|---|---|
-q, --quiet | — | false | Suppress copy status output. |
nimbus machine ssh
Section titled “nimbus machine ssh”nimbus machine ssh [name] [command...]Logs in to a machine using SSH, optionally running a command. If the first argument names an initialized machine it is treated as the machine name; otherwise all arguments are passed through as the guest command on the default machine.
nimbus machine rm
Section titled “nimbus machine rm”nimbus machine rm [name]Removes an existing machine’s config, state, and runtime layout when it is not running. No flags beyond the optional name.
nimbus machine os
Section titled “nimbus machine os”Manages machine OS images.
nimbus machine os apply <image> [--restart]nimbus machine os upgrade [--dry-run] [--restart]nimbus machine os rollback [--restart]| Subcommand | Flag | Default | What it does |
|---|---|---|---|
apply <image> | — | required | OCI image reference or digest to use on the next boot. |
apply | --restart | false | Restart the machine immediately if it is running. |
upgrade | --dry-run | false | Check whether an upgrade is available without applying it. |
upgrade | --restart | false | Restart the machine immediately if an upgrade is applied. |
rollback | --restart | false | Restart the machine immediately after queuing rollback. |
upgrade switches to the supported machine OS image for the current nimbus
release; rollback queues the previous bootc deployment for the next boot.
nimbus node
Section titled “nimbus node”Manages Nimbus node service-manager installation artifacts (systemd units
and Podman Quadlet files) on Linux hosts. The artifact subcommands select a
target with --systemd (native unit) or --container (Quadlet), and a
scope with --user or --system (default: system). node install
requires an explicit target; the other artifact subcommands default to
--systemd. See
Run Nimbus as a service and
Deploy on Linux.
nimbus node install
Section titled “nimbus node install”nimbus node install --systemd|--container [flags]| Flag | Env var | Default | What it does |
|---|---|---|---|
--systemd | — | — | Install native systemd units for a host binary. |
--container | — | — | Install a Quadlet .container file for the Nimbus OCI image. |
--user / --system | — | system | Service-manager scope to install into. |
--binary | — | /usr/local/bin/nimbus | Trusted Nimbus binary path (native installs only). |
--image | — | required with --container | Nimbus OCI image reference (Quadlet installs only). |
--socket-activation | — | false | Render a matching nimbus.socket and start from systemd’s inherited TCP listener (native only). |
--enable | — | false | Enable the generated service after writing artifacts. |
--now | — | false | Start the generated service after writing artifacts. |
--overwrite | — | false | Replace existing generated artifacts. |
--dry-run | — | false | Print generated artifacts without writing files or calling systemctl. |
nimbus node status
Section titled “nimbus node status”nimbus node status [--systemd|--container] [--user|--system]Shows the Nimbus node service status through systemd. Target and scope flags only.
nimbus node logs
Section titled “nimbus node logs”nimbus node logs [--systemd|--container] [--user|--system] [--follow]Prints Nimbus node service logs through journalctl.
| Flag | Env var | Default | What it does |
|---|---|---|---|
--follow | — | false | Follow appended logs. |
nimbus node doctor
Section titled “nimbus node doctor”nimbus node doctor [--systemd|--container] [--user|--system]Diagnoses host support for the selected node service mode. Target and scope flags only.
nimbus node uninstall
Section titled “nimbus node uninstall”nimbus node uninstall [--systemd|--container] [--user|--system] [--dry-run]Removes Nimbus node service-manager artifacts.
| Flag | Env var | Default | What it does |
|---|---|---|---|
--dry-run | — | false | Print the files and commands without mutating the host. |
nimbus compose
Section titled “nimbus compose”Compose-backed local service lifecycle commands. All subcommands share one
discovery rule for --file: explicit repeated --file flags win; otherwise
the COMPOSE_FILE environment variable provides an ordered list (separator
overridable with COMPOSE_PATH_SEPARATOR); otherwise Nimbus discovers
Compose files from the current directory and parents. Lifecycle subcommands
default to a deterministic per-project tenant, overridable with --tenant.
nimbus compose config
Section titled “nimbus compose config”nimbus compose config [--file <path>]... [--services]Validates and prints the resolved service plan from a Compose file.
| Flag | Env var | Default | What it does |
|---|---|---|---|
--file | COMPOSE_FILE | discovered | Compose files to read in order; repeat to merge overlays. |
--services | — | false | Print only service names, one per line. |
nimbus compose up
Section titled “nimbus compose up”nimbus compose up [service] [--file <path>]... [--tenant <id>]Starts one or more declared services for the current Compose project. When the service name is omitted, starts all declared services.
| Flag | Env var | Default | What it does |
|---|---|---|---|
--file | COMPOSE_FILE | discovered | Compose files to read in order; repeat to merge overlays. |
--tenant | — | project tenant | Tenant override. |
nimbus compose down
Section titled “nimbus compose down”nimbus compose down [service] [--file <path>]... [--tenant <id>]Stops one or more persisted services for the current Compose project. When
the service name is omitted, stops all persisted services in the tenant.
Same flags as compose up.
nimbus compose ps
Section titled “nimbus compose ps”nimbus compose ps [-f <format>] [-n] [--file <path>]... [--all-tenants]Shows persisted sandbox state for the current Compose project.
| Flag | Env var | Default | What it does |
|---|---|---|---|
--file | COMPOSE_FILE | discovered | Compose files to read in order; repeat to merge overlays. |
-f, --format | — | table | Output format: json, yaml, or table. |
-n, --noheading | — | false | Omit table headings from table output. |
--all-tenants | — | false | Show all tenants under the project-scoped backend root. |
nimbus compose inspect
Section titled “nimbus compose inspect”nimbus compose inspect <service> [-f <format>] [--file <path>]... [--tenant <id>]Shows persisted sandbox details for one service.
| Flag | Env var | Default | What it does |
|---|---|---|---|
--file | COMPOSE_FILE | discovered | Compose files to read in order; repeat to merge overlays. |
--tenant | — | project tenant | Tenant override. |
-f, --format | — | json | Output format: json or yaml. |
nimbus compose logs
Section titled “nimbus compose logs”nimbus compose logs <service> [--file <path>]... [--tenant <id>] [--follow]Prints persisted service logs for one service.
| Flag | Env var | Default | What it does |
|---|---|---|---|
--file | COMPOSE_FILE | discovered | Compose files to read in order; repeat to merge overlays. |
--tenant | — | project tenant | Tenant override. |
--follow | — | false | Keep polling the persisted log file for appended output. |
nimbus compose top
Section titled “nimbus compose top”nimbus compose top <service> [-f <format>] [-n] [--file <path>]... [--tenant <id>]Shows the persisted PID snapshot for one service.
| Flag | Env var | Default | What it does |
|---|---|---|---|
--file | COMPOSE_FILE | discovered | Compose files to read in order; repeat to merge overlays. |
--tenant | — | project tenant | Tenant override. |
-f, --format | — | table | Output format: json, yaml, or table. |
-n, --noheading | — | false | Omit table headings from table output. |
nimbus compose export quadlet
Section titled “nimbus compose export quadlet”nimbus compose export quadlet [flags]Renders Podman Quadlet artifacts from an admitted Compose plan for operator review.
| Flag | Env var | Default | What it does |
|---|---|---|---|
--file | COMPOSE_FILE | discovered | Compose files to read in order; repeat to merge overlays. |
--service | — | all services | Export only the named service; repeatable. |
--mode | — | containers | Quadlet export shape: containers, pod, or kube. |
--podman-version | — | unset | Podman version the operator targets; recorded in provenance. |
--output-dir | — | stdout | Write artifacts to a directory instead of printing them. |
--overwrite | — | false | Replace existing artifact files under --output-dir. |
--strict | — | false | Treat every export warning as an error. |
nimbus policy
Section titled “nimbus policy”Validates and explains Nimbus operator policy files. See Manage tenants for the policy model.
nimbus policy validate --file nimbus.policy.yaml [-f text|json]nimbus policy explain --file nimbus.policy.yaml [-f text|json]nimbus policy prove --file nimbus.policy.yaml [-f text|json]nimbus policy diff --from before.yaml --to after.yaml [-f text|json]| Subcommand | What it does |
|---|---|
validate | Validate a Nimbus operator policy file. |
explain | Explain the tenant-isolation decisions produced by a policy file. |
prove | Prove policy advisories and accepted-risk status. |
diff | Show authority changes between two policy files. |
Flags for validate, explain, and prove:
| Flag | Env var | Default | What it does |
|---|---|---|---|
--file | — | required | Path to a nimbus.policy.yaml file. |
-f, --format | — | text | Output format: text or json. |
Flags for diff:
| Flag | Env var | Default | What it does |
|---|---|---|---|
--from | — | required | Previous policy file. |
--to | — | required | Next policy file. |
-f, --format | — | text | Output format: text or json. |
nimbus encryption
Section titled “nimbus encryption”Encryption admin commands for local at-rest encryption. These commands read
the active key provider and persistence settings from the same environment
variables and config file as nimbus start (NIMBUS_ENCRYPTION_KEY_PROVIDER
and friends; see Configuration). Operational
guidance lives in Encryption.
nimbus encryption status
Section titled “nimbus encryption status”nimbus encryption status [--format text|json]Inspects encryption coverage and status.
| Flag | Env var | Default | What it does |
|---|---|---|---|
--format | — | text | Output format: text or json. |
nimbus encryption migrate
Section titled “nimbus encryption migrate”nimbus encryption migrate --source <path> --provider <family> [flags]Migrates a plaintext database to encrypted.
| Flag | Env var | Default | What it does |
|---|---|---|---|
--source | — | required | Path to the plaintext database to migrate. |
--target | — | source + .encrypted | Path to the encrypted output database. |
--provider | — | required | Provider family: sqlite, redb, or libsql-cache. |
--tenant-id | — | unset | Tenant ID for tenant databases. |
--skip-validation | — | false | Skip validation after migration. |
--retire-source | — | false | Remove the source after successful migration. |
nimbus encryption export
Section titled “nimbus encryption export”nimbus encryption export --source <path> --target <path> --provider <family> [--tenant-id <id>]Exports an encrypted database to plaintext for recovery.
| Flag | Env var | Default | What it does |
|---|---|---|---|
--source | — | required | Path to the encrypted database to export. |
--target | — | required | Path to the plaintext output database. |
--provider | — | required | Provider family: sqlite, redb, or libsql-cache. |
--tenant-id | — | unset | Tenant ID for tenant databases. |
nimbus encryption rotate-kek
Section titled “nimbus encryption rotate-kek”nimbus encryption rotate-kek --path <path> [flags]Rotates key-encryption keys: rewraps manifests without rewriting data.
| Flag | Env var | Default | What it does |
|---|---|---|---|
--path | — | required | Path to the database or data directory. |
--provider | — | unset | Provider family: sqlite, redb, or libsql-cache. |
--new-key-provider | — | current provider | Replacement key provider: master-key-file, key-dir, or aws-kms. |
--new-master-key-file | — | unset | New master key file when rotating to master-key-file. |
--new-key-dir | — | unset | New key directory when rotating to key-dir. |
--new-aws-kms-key-id | — | unset | AWS KMS key ID or alias when rotating to aws-kms. |
--new-aws-region | — | unset | AWS region override when rotating to aws-kms. |
--new-aws-endpoint-url | — | unset | AWS endpoint override when rotating to aws-kms. |
--all | — | false | Rotate all manifests in the directory. |
nimbus encryption rotate-dek
Section titled “nimbus encryption rotate-dek”nimbus encryption rotate-dek --path <path> --provider <family> [flags]Rotates data-encryption keys; provider-specific and may rewrite data.
| Flag | Env var | Default | What it does |
|---|---|---|---|
--path | — | required | Path to the encrypted database. |
--provider | — | required | Provider family: sqlite, redb, or libsql-cache. |
--tenant-id | — | unset | Tenant ID for tenant databases. |
--skip-backup | — | false | Skip backup before rotation. |
nimbus packages
Section titled “nimbus packages”Provisions the embedded Nimbus JS packages into an app’s
.nimbus/packages/ directory so file: package specifiers resolve offline.
nimbus packages provision
Section titled “nimbus packages provision”nimbus packages provision [target] [--app-dir <path>]| Argument / flag | Env var | Default | What it does |
|---|---|---|---|
[target] | — | all | What to provision: all or an adapter (convex, firebase, mongodb, dynamodb, nimbus); dependencies are included automatically. |
--app-dir | — | . | App directory to provision into. |
nimbus packages verify
Section titled “nimbus packages verify”nimbus packages verify [--app-dir <path>]Verifies provisioned package bytes against the binary’s embedded checksums.
| Flag | Env var | Default | What it does |
|---|---|---|---|
--app-dir | — | . | App directory whose .nimbus/packages/ is verified. |