Skip to content
vops

Getting started

The first useful vops session needs no provider account and makes no infrastructure changes. Install the CLI, inspect the supported providers and open the local dashboard before deciding whether to add credentials.

Prerequisites

vops requires Node.js 20 or newer. Install the published package globally:

Terminal window
npm install -g @flui-cloud/vops
vops --version

Every topic and command has built-in help:

Terminal window
vops --help
vops providers --help
vops providers plans --help

Research without credentials

Start with the provider model:

Terminal window
vops providers list
vops providers capabilities ovh
vops compare --provider ovh

The OVH public catalog can answer without an account token. Other provider queries may require credentials because their APIs do not expose equivalent public data.

No command above provisions a server.

Open the local dashboard

Terminal window
vops ui

vops starts a local service on 127.0.0.1, creates a one-time browser session and opens the dashboard. Pass --no-open when you want to start the service without launching a browser.

The dashboard and CLI share the same provider, inventory and application services. Using one does not create a second configuration store.

Add credentials only when needed

Credentials are required when you want to query a private provider account, compare across providers or create resources.

Terminal window
export VOPS_TOKEN=...
vops config set hetzner
unset VOPS_TOKEN
vops config list

config set currently stores Hetzner and Scaleway credentials; the other provider integrations use their documented environment variables. Avoid putting tokens directly in shell history. See Configuration and credentials for the local vault and keyring model.

Choose your next path