1
Install the CLI
Choose your preferred installation method:
- npm
- Homebrew
- Binary
Install via npm if you have Node.js version 16 or later installed.For detailed instructions, see Installation.
Requires Node.js version 16+.
2
Verify the installation
Confirm the CLI is installed and accessible:You should see the CLI version number.
3
Authenticate
Log in to Control Plane using your browser:This opens your browser for authentication and creates a default profile.
If you can’t use a browser, see the browser-less login guide.
Using WSL2? Browser login requires extra setup
Using WSL2? Browser login requires extra setup
When you run After installation, Chrome appears in your Windows Start menu under the distro name (e.g., Ubuntu → Google Chrome). Run
cpln login in WSL2, the localhost URL won’t work in your Windows browser because it points to the WSL2 instance, not Windows.Solution: Install a browser in WSL2 (requires WSLg):cpln login, copy the localhost URL from the terminal, and paste it into your WSL2 Chrome.Alternative: Use browser-less login with a service account token.4
Explore available commands
Use the built-in help to discover commands:Start with read-only commands like
cpln gvc get or cpln workload get.Try your first commands
Once authenticated, try these safe, read-only commands:Deploy your first app
Build and deploy a local application to Control Plane:1
Create a GVC
Create a Global Virtual Cloud to host your workload:
2
Build and push your image
From your project directory, build and push to your org’s private registry:
3
Create a workload
Deploy your image as a workload:
Replace
8080 with the port your application listens on. Use --public to make it accessible from the internet.4
Check your deployment
View your workload status:Once ready, access your app at the endpoint shown in the output.
For more image operations, see the Images guide.