Make every client point at the same workspace
Account → plan → developer key → node handshake → workspace sync → verified CLI, SDK and AI call. The UI, vxcli and SDKs use one contract.
In the dashboard (UI)
Use the dashboard for the first setup. Keep the browser open while you verify the same state from the CLI or an SDK so a stale session cannot hide a billing or node mismatch.
Create or select the workspace
Sign in to vxcloud.io, select the organization/workspace in the profile menu, and confirm the workspace name before creating credentials. A developer key and node are scoped to this workspace.
- Use a separate workspace for production, staging and demos.
- Do not paste provider secrets into a prompt or a source repository.
Choose a plan and finish billing
Open Billing, read the available plans and current subscription, then choose Upgrade/Checkout or activate a free plan. Complete hosted payment when required and return to Billing to confirm the active plan, period, seats and allowances.
- Read entitlements after every plan change; an active plan and an enabled capability are different checks.
- Use the billing portal for cards, receipts, renewal and cancellation.
Create a developer API key
Open Developer → API keys, create a named key and copy it once. Use one key per environment or CI job and rotate by creating the replacement before revoking the old key.
Register and sync the tenant node
Open Nodes, select the target node, choose Sync With Workspace, and wait for the health/version checks to finish. For self-hosted workloads the control plane verifies the node identity over HTTPS before binding it to the workspace.
- The sync refreshes existing Vault/AppRole credentials; it cannot bootstrap a missing node identity.
- Use the node selector to set a default, but keep the node hostname visible when a task targets a different node.
Configure AI providers
In AI Settings add or select the workspace provider (Anthropic, OpenAI, Ollama or another enabled provider), choose a model, and save. A read-only test should succeed before an agent is allowed to deploy, send, or mutate data.
Verify the end-to-end state
Check the node card for Active, run the built-in health/version check, then run a read-only AI prompt such as “report node status and do not change anything”. Confirm the response names the intended workspace and node.
Stuck halfway through? Email [email protected] — most replies land within an hour during weekdays.
All guidesWas this page helpful?