Overview
The StrataGateway CLI is intended to provide a terminal-native interface over the StrataGateway API, enabling fast infrastructure workflows directly from the command line.
The StrataGateway CLI is currently planned and not yet publicly available. Command names, flags, configuration files, authentication workflows, output formats, and installation methods may change before release.
Planned installation
The CLI is not yet available for download. The examples below illustrate the planned installation approach.
Illustrative installation example
Install script (illustrative)
curl -fsSL https://example.invalid/install-strata.sh | shImportant: Do not use stratagateway.com as a real install URL unless such an installer actually exists.
Planned package-manager possibilities
The above are text-only descriptions of planned distribution methods. No working download links exist yet.
Authentication
The CLI is planned to authenticate using API tokens. You can log in interactively or set an environment variable.
Interactive login
strata auth loginAlternative: set the token via environment variable.
Environment variable (bash/zsh)
export STRATA_API_TOKEN="your_token_here"Environment variable (PowerShell)
$env:STRATA_API_TOKEN="your_token_here"Command syntax is illustrative and may change.
See Authentication for token management details.
Configuration
The CLI is planned to support a configuration file for default settings.
Planned config options
PlannedIllustrative configuration file at ~/.config/strata/config.yaml:
Illustrative configuration
organization: org_example
region: fra-1
output: tableThis file format is not finalized and may change.
Core commands
Planned top-level command structure:
Planned CLI command structure
Command groups
strata version
strata help
strata auth
strata config
strata instance
strata network
strata firewall
strata ssh-keyCompute commands
Illustrative examples for instance management:
List instances
List
strata instance listCreate instance
Create
strata instance create \
--name web-prod-01 \
--region fra-1 \
--plan compute-standard \
--image ubuntu-24.04-ltsInspect instance
Get
strata instance get inst_7a91c2Reboot instance
Reboot
strata instance reboot inst_7a91c2Delete instance
Delete
strata instance delete inst_7a91c2Every command above is preview syntax. The CLI does not currently exist.
Network commands
Illustrative network management examples:
List networks
List
strata network listCreate network
Create
strata network create \
--name production-private \
--region fra-1 \
--cidr 10.10.0.0/24Inspect network
Get
strata network get net_52a8f1Illustrative CLI syntax.
See Networking for the network resource model.
Firewall commands
Illustrative firewall management examples:
List firewalls
List
strata firewall listCreate firewall
Create
strata firewall create --name web-productionInspect firewall
Get
strata firewall get fw_82c9a1Rule management syntax is still under design.
See Firewalls for the firewall policy model.
SSH key commands
Illustrative SSH key management examples:
List SSH keys
List
strata ssh-key listAdd SSH key
Add
strata ssh-key add \
--name "Personal Laptop" \
--file ~/.ssh/id_ed25519.pubDelete SSH key
Delete
strata ssh-key delete key_8f3a9b1cThe CLI should only upload public SSH key material. Private keys must remain on the user's trusted device.
See SSH Keys for the key management model.
Output formats
The CLI is planned to support multiple output modes:
Table
Human-readable terminal output.
JSON
Machine-readable automation output.
Illustrative usage:
JSON output
strata instance list --output jsonIllustrative output
JSON response
{
"data": [
{
"id": "inst_7a91c2",
"name": "web-prod-01",
"status": "running"
}
]
}Illustrative output.
Scripting and automation
The CLI is intended for use in CI/CD pipelines, shell scripts, infrastructure automation, and developer workflows.
Illustrative automation workflow.
Capture instance ID in variable
INSTANCE_ID=$(strata instance create \
--name ci-worker \
--region fra-1 \
--output json)The actual output schema is not finalized. The above is illustrative only.
Exit codes
The CLI is planned to follow standard conventions:
Detailed exit code semantics will be documented before public release.
Planned
Shell completion
Planned support for shell completion:
Shell completion is not yet implemented.
Planned
CLI and REST API
The CLI is intended to act as a developer-friendly interface over the same core StrataGateway API used by SDKs and infrastructure tooling.
Conceptual flow
Developer
→ StrataGateway CLI
→ REST API
→ Control PlaneSee REST API for the underlying API resource model.
Next steps
Next
TypeScript SDKWas this page helpful?