Contents
nexctl began as a small tool for starting and stopping servers. Over the past year it picked up separate command sets for Serverless and for clusters, each with its own habits and flag names. Version 2.0 puts all of it under one grammar.
One grammar for everything
Every command now reads nexctl <resource> <verb>, and a flag means the same thing wherever it appears. --family, --region and --name behave identically for servers, endpoints and clusters.
nexctl servers create --family b300 --region eu-ams-1nexctl endpoints create --family h100 --region eu-fra-1 --image chat-13b:1.4nexctl clusters create --family h200 --region eu-ams-1 --nodes 4JSON on every command
Add -o json to any command and you get a stable, documented shape back. Scripts no longer parse tables, and the shape is versioned together with the API.
{ "name": "llm-train-01", "family": "B300", "gpus": 8, "region": "eu-ams-1", "status": "running", "billing": "per_second", "rate_per_hour_eur": 48.00}Follow a deploy to ready
--watch follows a create or update until the resource is ready, prints each step as it happens, and exits with a non-zero code when something fails. It is made for CI jobs that have to wait for a server before they run tests on it.
Upgrading from 1.x
- Run
nexctl self-update, or download the new binary from the docs. - Run
nexctl config migrateonce. It rewrites your profile in the new format and keeps a backup. - Old 1.x command names keep working until March 2027 and print the new form as a hint.
Tell us what is missing
nexctl feedback opens a short form with your version and operating system filled in. The Developer Experience team reads every entry and answers the ones that leave an email.