/coolify-operator

name: coolify-operator
description: Master Coolify operator for self-hosted deployment platform. Use when the user mentions 'coolify', 'deploy on coolify', 'list/restart/redeploy applications', 'view coolify logs', 'coolify API/CLI', 'manage coolify servers/databases/apps', or 'coolify context'. Automates deployments and management via REST API or official CLI.
metadata:
  author: ft.ia.br
  version: "3.2"
  date: 2026-10-19
  license: MIT
  category: ci-cd-and-deployment
  coolify_cli_version: "1.10.0"
  coolify_version: "4.4.6"
  upstream_commit: "e1d60947fc66c194d256b1049fd69c1ddf819760"

Coolify Operator

Skill for operating Coolify instances through the **official CLI** or **REST API**. Coolify is a self-hosted open-source platform alternative to Heroku/Vercel/Netlify for deploying applications, databases, and services.

**Pinned upstream:** coolify-cli **v1.10.0** (`e1d60947fc66c194d256b1049fd69c1ddf819760`) — Coolify v4 surface. Prefer command forms from `llms.txt` / `llms-full.txt` on that tag.

**Coolify version tested:** v4.4.6 (October 2026)

CLI v1.10.0 Highlights

• **New:** `coolify database import start|upload|status` and `coolify service database import ...` — restore backups from a local file, a previous upload, S3, or a server path
• **New:** `coolify audit list` — team audit log (admins/owners)
• **New:** `coolify integration-token create` + `coolify app secret-manager set` — Doppler / Infisical / Vault secret managers
• **New:** `coolify app previews logs`, `coolify teams update --build-server-fallback`, `coolify project environments get`
• **New:** `sqlite` database type (`--sqlite-databases`)
• `coolify service application logs` accepts `-n, --lines`

CLI v1.9.0 Highlights

• **New:** `coolify app previews list|get|create|update` (preview deployments API, Coolify v4.4.0+)
• **New:** `coolify server registry list|login|check|logout` — Docker registry logins on servers
• **New:** `coolify server remove --force` / `--delete-from-provider`
• **New:** `--server-role deployment|build|both` on `server add` / `server update` (`--is-build-server` deprecated)
• **Changed:** `coolify server get <uuid> --resources` now calls `GET /servers/{uuid}/resources` and prints a flat list (`uuid`, `name`, `type`, `status`) instead of the server details
• GitHub App commands also accept the numeric app ID

CLI v1.8.0 Highlights

• **New:** Commands for instance-wide SMTP/Resend settings (`coolify settings email get/update`)
• **Security:** API tokens redacted by default in `context list` output (use `--show-sensitive` to reveal)
• **Fix:** `is_buildtime` field now correctly sent on app env create/update
• **Breaking:** `--retention-max-storage-locally` and `--retention-max-storage-s3` accept **numeric GB** (e.g., `1`, `10.5`), not unit-suffixed strings

When to use this skill

• Connect to Coolify instances (via CLI contexts or API)
• Create, list, and manage applications, services, databases, and servers
• Deploy, restart, or stop resources
• View logs and deployment status
• Manage environment variables, shared envs, and storage
• Configure backups for databases
• Operate multiple Coolify instances (contexts)
• Integrate with GitHub / GitLab Apps for private repositories
• Configure notifications and instance email (SMTP/Resend)
• Manage cloud-init scripts and provision servers (Hetzner, DigitalOcean, Vultr)
• Restore database backups (database import), read the team audit log, configure external secret managers, and manage Docker registry logins on servers

---

Recent Changes (v4.4.x)

v4.4.0 — Major feature release

Highlights relevant to CLI/API operators (see the [v4.4.0 release](https://github.com/coollabsio/coolify/releases/tag/v4.4.0)):

• **SQLite** as a standalone database type (experimental)
• **Third-party secret managers** (Doppler, Infisical, HashiCorp Vault). `{{vault.KEY}}` references are resolved at deployment/database start and never stored in Coolify
• **Team audit log** (`GET /audit-events`, admins/owners only; events pruned after 90 days)
• **Database import API** for standalone and service databases (upload, server path, or S3). Upload/start need `write`; a server-path import also needs `deploy`
• **Server roles** (`server_role`: deployment / build / both); `is_build_server` is deprecated. Team setting decides whether builds fall back to the deployment server
• **Docker registry logins** per server (`GET/POST /servers/{uuid}/registries`, `.../{registry}/check`, `DELETE .../{registry}`). Coolify runs `docker login` on the server and does not store the token
• **Preview deployments API** (`GET /applications/{uuid}/previews[/{pr_id}]`, `POST /applications/{uuid}/previews` needs `deploy`)
• Delete a server from its cloud provider: `DELETE /servers/{uuid}?delete_from_provider=true`
• Named volumes for new mounts (existing bind mounts keep their paths)

**Behavior changes to watch:**

• Single-database PostgreSQL restores no longer drop existing objects by default — pass `replace_existing` (`--replace-existing`) to get the old `--clean` behavior; owners/privileges are skipped unless `keep_owners` (`--keep-owners`)
• Env var names must match `[A-Za-z_][A-Za-z0-9_.]*` (invalid build-time names stop builds)
• Container labels use UUIDs (`coolify.applicationUuid`, `coolify.serviceUuid`, `coolify.databaseUuid`); generated container names use an ISO 8601 suffix
• Container log and scheduled-task output endpoints require `read:sensitive` in the API
• Multi-server applications: extra servers must use the same proxy and pull the primary server's image; persistent volumes and Docker Compose apps can no longer be combined with multiple servers

v4.4.1 – v4.4.6

• v4.4.1: volume backup notifications and missing-volume-backup alerts; Sentinel 1.0.2
• v4.4.2: GitHub Actions runners on deployment+build servers; per-server traffic analytics IP storage controls
• v4.4.3: static-site PR previews fixed; nested Base64 custom labels fixed in API updates
• v4.