
Company News
Free Business Plan Upgrades for Open Source Maintainers
Open source maintainers are under more pressure than ever. We're raising our open source program from the Team plan to the Business plan, free.
Command-line interface for the Treza platform - manage enclaves, KYC proofs, and more
Command-line interface for the Treza platform
Manage secure enclaves, verify KYC proofs, and interact with the Treza platform directly from your terminal.
npm install -g @treza/cli
Or with yarn:
yarn global add @treza/cli
# Configure the CLI with your wallet
treza config init
# List your enclaves
treza enclave list
# Create an enclave from a Docker image
treza enclave create \
--name "My Enclave" \
--source-type registry \
--image nginx:latest \
--region us-west-2
# Create an enclave from a GitHub repository
treza enclave create \
--name "My App Enclave" \
--source-type github \
--github-repo https://github.com/my-org/my-app \
--github-branch main \
--region us-west-2
# Interactive setup
treza config init
# Show current configuration
treza config show
# Set individual values
treza config set walletAddress 0x...
treza config set apiUrl https://app.trezalabs.com
# Clear all configuration
treza config clear
# List all enclaves
treza enclave list
treza enc ls # alias
# Get enclave details
treza enclave get <id>
Enclaves support three deployment sources:
From a public Docker / container registry image:
treza enclave create \
--name "My Enclave" \
--source-type registry \
--image nginx:latest \
--region us-west-2 \
--instance-type m6i.xlarge \
--cpu 2 \
--memory 1024
From a GitHub repository (Treza builds the image automatically):
treza enclave create \
--name "My App Enclave" \
--source-type github \
--github-repo https://github.com/my-org/my-app \
--github-branch main \
--github-token ghp_xxxxxxxxxxxx \
--region us-west-2
Your repository must contain a
Dockerfileat its root. The build status will progress throughPENDING_BUILD → BUILDING → PENDING_DEPLOY → DEPLOYING → DEPLOYED.
From a private container registry:
treza enclave create \
--name "My Private Enclave" \
--source-type private-registry \
--image registry.example.com/my-org/my-app:latest \
--registry-url registry.example.com \
--registry-username myuser \
--registry-password mypassword \
--region us-west-2
| Flag | Description | Default |
|---|---|---|
--provider <id> | Provider ID | aws-nitro |
--instance-type <type> | EC2 instance type | m6i.xlarge |
--cpu <count> | vCPU count for the enclave | 2 |
--memory <mib> | Memory in MiB for the enclave | 1024 |
--workload-type <type> | service or task | service |
treza enclave pause <id>
treza enclave resume <id>
treza enclave terminate <id>
treza enclave delete <id>
# Application logs (default)
treza enclave logs <id>
treza enclave logs <id> --type application --limit 100
# Build logs (for GitHub-sourced enclaves)
treza enclave logs <id> --type build
# System logs
treza enclave logs <id> --type system
# Verify a proof
treza kyc verify <proof-id>
# Get proof details
treza kyc get <proof-id>
# Quick status check
treza kyc status <proof-id>
Requires an API key with pii:* permissions (see platform API Keys). Optional: treza config set piiProcessorEnclaveId enc_... and treza config set complianceMode gdpr.
# Submit JSON: { "type": "SSN", "payload": "opaque-string", "consentGiven": true }
treza pii submit --file ./test-pii.json --enclave enc_12345
treza pii retrieve --pii-id pii_abc123 --purpose "credit_check"
treza pii delete --pii-id pii_abc123
treza pii consent grant --data-type SSN --recipient "0x..."
treza pii consent revoke --consent-id consent_xyz
treza pii audit --user-id 0xYourAddress --start-date 2026-01-01
# List all tasks
treza task list
treza task ls --enclave <enclave-id>
# Create a scheduled task
treza task create
treza task create --name "Daily Sync" --enclave <id> --schedule "0 0 * * *"
# Delete a task
treza task delete <id>
# Show cron examples
treza task cron
# List available providers
treza provider list
--json # Output as JSON (available on most commands)
--help, -h # Show help for any command
--version, -v # Show CLI version
The CLI stores configuration in a local config file:
| Setting | Description | Default |
|---|---|---|
walletAddress | Your Ethereum wallet address | Required |
apiUrl | Treza API endpoint | https://app.trezalabs.com |
apiKey | Optional API key for authenticated requests | — |
piiProcessorEnclaveId | Default PII_PROCESSOR enclave for PII CLI | — |
complianceMode | Label for tooling (gdpr, ccpa, hipaa, off) | off |
Configuration is stored at:
~/Library/Preferences/treza-cli-nodejs/config.json~/.config/treza-cli-nodejs/config.json%APPDATA%/treza-cli-nodejs/config.json# Configure CLI
treza config init
# Create an enclave that builds from your GitHub repo
treza enclave create \
--name "Demo App" \
--source-type github \
--github-repo https://github.com/my-org/my-app \
--github-branch main \
--github-token ghp_xxxxxxxxxxxx \
--region us-west-2
# Monitor build progress
treza enclave logs <id> --type build
# Once status is DEPLOYED, view application logs
treza enclave logs <id> --type application
treza enclave create \
--name "Nginx Enclave" \
--source-type registry \
--image nginx:latest \
--region us-west-2
# Check status
treza enclave get <id>
treza enclave create \
--name "Internal Service" \
--source-type private-registry \
--image registry.example.com/my-org/service:v1.0.0 \
--registry-url registry.example.com \
--registry-username myuser \
--registry-password mypassword \
--region us-west-2
# Quick verification
treza kyc status 550e8400-e29b-41d4-a716-446655440000
# Detailed verification with JSON output
treza kyc verify 550e8400-e29b-41d4-a716-446655440000 --json
# List enclaves as JSON for parsing
treza enclave list --json | jq '.[] | select(.status == "DEPLOYED")'
# Create enclave non-interactively
treza enclave create \
--name "Automated Enclave" \
--source-type registry \
--image my-org/my-service:latest \
--region us-west-2 \
--provider aws-nitro
| Status | Description |
|---|---|
PENDING_BUILD | Waiting to start building from GitHub source |
BUILDING | AWS CodeBuild is building the Docker image |
BUILD_FAILED | Build failed — check build logs |
PENDING_DEPLOY | Image ready, waiting to deploy |
DEPLOYING | EC2 Nitro instance is being provisioned |
DEPLOYED | Running and healthy |
PAUSED | Instance stopped |
TERMINATED | Instance terminated |
# Clone the repository
git clone https://github.com/treza-labs/treza-cli.git
cd treza-cli
# Install dependencies
npm install
# Build
npm run build
# Link for local development
npm link
# Now you can use 'treza' command globally
treza --help
MIT License - see LICENSE file for details.
Built by Treza Labs — Privacy infrastructure for the next era of finance.
FAQs
Command-line interface for the Treza platform - manage enclaves, KYC proofs, and more
We found that @treza/cli demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Company News
Open source maintainers are under more pressure than ever. We're raising our open source program from the Team plan to the Business plan, free.

Security News
The supply chain control that delays freshly published gems now covers lockfile generation and gem vendoring in Ruby projects.

Security News
During a UK cyber test, a Mythos 5 agent used sockpuppets, social engineering, and prompt injection to try to get a maintainer to merge malware.