Private Vantage Installation
Install v8x
Install v8x with uv:
uv venv
source .venv/bin/activate
uvx v8x
For the general installation workflow, see the CLI quickstart.
Connect to a private Vantage deployment
The v8x comes preconfigured to work with https://vantagecompute.ai by default.
If you are connecting to a privately hosted Vantage instance you will need to set up your profile accordingly.
Create a profile:
uvx v8x profile create --help
The most important options are the profile name, --vantage-url, and --activate if you want the new profile to become current immediately.
Key options:
--vantage-urlsets the base URL for the private Vantage deployment--activatemakes the new profile current immediately
uvx v8x profile create vantage-example-com \
--vantage-url=https://vantage.example.vantagecompute.ai \
--activate
╭───────────────────────────── Profile Created ───────────────────────────╮
│ ✅ Profile 'vantage-example-com' created successfully! │
│ 🎯 Set as active profile! │
╰─────────────────────────────────────────────────────────────────────────╯
Profile Details: vantage-example-com
┏━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Property ┃ Value ┃
┡━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
│ Profile Name │ vantage-example-com │
│ Vantage URL │ https://vantage.example.vantagecompute.ai │
│ OIDC Client ID │ default │
│ OIDC Max Poll Time │ 300 seconds │
│ Supported Clouds │ maas, localhost, aws, gcp, azure, on-premises, k8s │
└────────────────────┴────────────────────────────────────────────────────┘
After this command completes, the CLI stores the endpoint configuration in a named profile and, with --activate, uses it as the default target for later commands.
Success looks like this: the profile is created, the configured base URL is echoed back in the summary, and the active profile switches to the private deployment when requested.
Inspect Identity
If you want to inspect identity-related options first, run:
uvx v8x whoami --help
uvx v8x whoami
Key options:
- Use the default table output for a quick human-readable check
- Use
--jsonwhen you want to pipe identity details into another tool
Current User Information
┏━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Property ┃ Value ┃
┡━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
│ Email │ james@vantagecompute.ai │
│ Client ID │ default │
│ Profile │ vantage-example-com │
│ Name │ James Beedy │
│ User ID │ 028da929-d0cf-4984-8bbe-9bc83f49f797 │
│ Token Issued │ 2025-09-12T22:25:06 │
│ Token Expires │ 2025-09-12T23:25:06 (✅ Valid) │
│ Status │ ✅ Logged in │
└───────────────┴──────────────────────────────────────┘
uvx v8x whoami --json | jq '{email: .email, client_id: .client_id}'
{
"email": "james@vantagecompute.ai",
"client_id": "default"
}
Use uvx v8x whoami to confirm that your active profile points to the expected private deployment and that your login is valid.
Success looks like this: the output shows the expected profile, identity, and token validity state for the private environment you just configured.
See also: Commands | Troubleshooting