This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 2.0.4 instead.
Reason given by maintainers: Superseded by 2.0.2, please upgrade
voltagegpu-cli
Deploy and manage VoltageGPU machines from your terminal or from Python:
- Confidential VMs: Intel TDX trust domains with an NVIDIA GPU, only your SSH keys on the machine, and an attestation you generate and verify yourself.
- Standard pods: whole GPU machines without an enclave, for workloads that are not sensitive.
Billing is per second. The first hour is charged when you deploy; when you stop a standard pod, the unused part of that hour goes back to your balance.
pip install voltagegpu-cli
Python 3.10 or newer. The package installs the voltagegpu command (volt is
an alias kept from earlier releases).
1. Log in
Create an API key at https://voltagegpu.com/api-keys (it is shown once), then:
voltagegpu login # prompts for the key, hidden, checks it, saves it to ~/.volt/config.ini (mode 0600)
# or, for CI and scripts:
export VOLT_API_KEY=volt_...
Add the SSH key you will connect with (defaults to ~/.ssh/id_ed25519.pub):
voltagegpu ssh-keys add
voltagegpu ssh-keys list
2. Pick a machine
voltagegpu machines # Confidential VM tiers, then standard machines, cheapest first
voltagegpu machines --standard --gpu A6000 # filter by GPU model
voltagegpu machines --standard --max-price 1 --json
voltagegpu machines --confidential
voltagegpu templates # images for standard pods (PyTorch by default)
3a. Deploy a standard pod
voltagegpu deploy standard --machine <machine_id>
voltagegpu deploy standard --cheapest --gpu 4090 --wait # cheapest matching machine, wait for SSH
The CLI shows the price and asks before charging. In scripts, add --yes.
If your account has several SSH keys, choose one with --ssh-key <key_id>.
Other options: --template <template_id>, --jupyter, --ports 3,
--auto-terminate 8 (hours), --name my-pod.
3b. Deploy a Confidential VM
voltagegpu deploy confidential --tier rtx6000b-small --wait
voltagegpu deploy confidential --tier h100-small --hardstop 4 --port 8000 --port 8443/tcp
Every SSH key on your account is bound to the VM when it is created; a VM cannot be given a key afterwards, so add yours first. The sudo password is printed once and is not kept anywhere. The command also prints how to generate the attestation inside the VM.
4. Connect, inspect, stop
voltagegpu pods list
voltagegpu pods wait <pod_id> # until SSH answers
voltagegpu ssh <pod_id> # interactive shell
voltagegpu ssh <pod_id> -- nvidia-smi -L # run one command
voltagegpu ssh <pod_id> --print # just print the ssh command
voltagegpu pods show <pod_id>
voltagegpu pods stop <pod_id> # releases it: billing stops, the disk is deleted
voltagegpu balance
Fresh pods present a new host key. In non-interactive scripts you can accept it
on first use with -o StrictHostKeyChecking=accept-new.
5. Verify a Confidential VM
Inside the VM you produce an evidence bundle (the deploy output prints the exact commands). On your own machine:
pip install "voltagegpu-cli[verify]" # installs voltage-verify
voltagegpu verify bundle.json --offline
voltagegpu verify bundle.json --challenge <hex-you-issued> --gpus 1
voltagegpu verify runs voltage-verify,
which checks the Intel TDX quote up to Intel's root and the NVIDIA GPU
attestation tokens, without trusting VoltageGPU.
Scripting
Every list command takes --json; deploys and stops take --yes.
# Deploy the cheapest standard machine, wait for SSH, run a job, release it.
POD=$(voltagegpu deploy standard --cheapest --yes --json | jq -r .deploy.pod_id)
voltagegpu pods wait "$POD"
voltagegpu ssh "$POD" -o StrictHostKeyChecking=accept-new -- nvidia-smi
voltagegpu pods stop "$POD" --yes
Exit codes: 0 success, 1 API or runtime error, 2 usage error or missing
confirmation.
Python SDK
from volt.sdk import VoltageGPUClient
with VoltageGPUClient() as client: # VOLT_API_KEY or ~/.volt/config.ini
machine = client.list_machines("standard")[0] # cheapest first
result = client.deploy_standard(machine.id, name="my-pod")
pod = client.wait_until_reachable(result.pod_id)
print(pod.ssh_command)
print(client.release_pod(result.pod_id).prepaid_refund)
A complete example is in examples/deploy_standard_pod.py.
REST API
The CLI is a thin client of the public API, documented at https://docs.voltagegpu.com/api-reference. The same deploy with curl:
curl -X POST https://api.voltagegpu.com/api/volt/pods \
-H "X-API-Key: $VOLT_API_KEY" -H "Content-Type: application/json" \
-d '{"provider":"standard","name":"my-pod","machine_id":"<machine_id>"}'
curl https://api.voltagegpu.com/api/volt/pods -H "X-API-Key: $VOLT_API_KEY"
Configuration
| Setting | Where |
|---|---|
| API key | --api-key of login, VOLT_API_KEY (or VOLTAGEGPU_API_KEY), then ~/.volt/config.ini |
| API base URL | VOLT_BASE_URL (https only; default https://api.voltagegpu.com/api) |
| Debug | VOLT_DEBUG=1 shows tracebacks |
voltagegpu config shows where the key comes from, masked.
Security
- The key is sent only over HTTPS, in the
X-API-Keyheader; redirects are never followed and certificates are always verified. - The key is never printed.
~/.volt/config.iniis created readable by you only, andvoltagegpu configwarns if its permissions are too open. - The SSH command returned by the API is parsed into user, host and port and ssh is started without a shell, so a tampered answer cannot run a command on your machine.
ssh-keys addrefuses private keys.
Report a vulnerability to contact@voltagegpu.com.
Upgrading from 1.2
volt cc inventory/volt cc deploy: Confidential containers were retired on 2026-10-01. Usevoltagegpu machines --confidentialandvoltagegpu deploy confidential --tier <tier>.volt pods stopnow releases the pod and reports the refund.volt account balanceis nowvoltagegpu balance.
Links
- Docs: https://docs.voltagegpu.com/cli
- API reference: https://docs.voltagegpu.com/api-reference
- API keys: https://voltagegpu.com/api-keys
- Changelog: CHANGELOG.md
MIT License.
Metadata
Release files for voltagegpu-cli 1.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| voltagegpu_cli-1.3.0.tar.gz | 40.2 kB | Without provenance | Details for voltagegpu_cli-1.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| voltagegpu_cli-1.3.0-py3-none-any.whl | Python 3 | none | any | Details for voltagegpu_cli-1.3.0-py3-none-any.whl |
Total release size: 75.3 kB
Release files / voltagegpu_cli-1.3.0.tar.gz
| Download URL | voltagegpu_cli-1.3.0.tar.gz |
|---|---|
| Size | 40.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2d7d8f4ee04ecff4419b7f97f888076503353896110456af7949053131bd5348
|
|
BLAKE2b-256 checksum How to use checksums |
29199442250607c5f3378d46ec7a74c19e2c83ffab00dcb94684c8e5a2b8042e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.4
|
Release files / voltagegpu_cli-1.3.0-py3-none-any.whl
| Download URL | voltagegpu_cli-1.3.0-py3-none-any.whl |
|---|---|
| Size | 35.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e80b4221285de195a298919c577f85718918f7895f8a0c6612552864efafca5c
|
|
BLAKE2b-256 checksum How to use checksums |
462b0745804551a2829ad0888923056ce34ebf4b1da4ae17cfb14c97149aafbe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.4
|
Security for voltagegpu-cli 1.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.