Coolify CLI

Why it's ranked here

The command surface is unusually broad for daily Coolify operations. Multiple contexts, machine-readable output, shell completion, log following, and generated agent documentation make it useful beyond occasional manual tasks. The experimental Coolify v5 mesh setup is clearly marked and gated, but its network changes require caution.

What's good

Automation receives compact or pretty JSON, while people get tables. Application creation supports public repositories, private GitHub integrations, SSH deploy keys, Dockerfiles, and registry images. Operators can manage lifecycle actions, logs, routing, tags, storage, and environment variables without repeatedly returning to the dashboard.

Tradeoffs

Saved contexts place API tokens in a local JSON configuration file. Recommended installers pipe downloaded scripts directly into a shell or PowerShell. The Coolify v5 initialization feature remains experimental, requires privileged remote changes, modifies WireGuard, firewall, Podman, and agent configuration, and explicitly warns against production-first testing.

How to use it well

It best serves Coolify operators who want repeatable terminal workflows across production and staging instances. Use JSON output for scripts, named contexts for environment separation, connection verification before changes, and confirmation safeguards around deletion. It does not replace a general infrastructure system outside the Coolify API and its supported providers.

Observed

Primary language

Go

Interface

Command-line application built with Cobra; the root command also registers an MCP command

Installation surfaces

Linux and macOS shell installer, Windows PowerShell installer, Homebrew, and Go install

Platform support

Linux, macOS, and Windows installation instructions are provided

Output formats

Table, compact JSON, and pretty JSON

Shell completion

Bash, zsh, fish, and PowerShell

Configuration model

Local JSON configuration supports multiple named Coolify contexts