Coolify 4.4's traffic analytics page for a server: the collection settings, the KPI strip, and the requests chart.
Traffic analytics in Coolify 4.4: collection settings, the KPI strip and the requests chart for a local test server. Screenshot: Coolify project, from the official v4.4.0 release notes.

Coolify 4.4.0 landed on October 6, and the release is generous: built-in traffic analytics, a new database option, single sign-on, secret managers, and DNS management, plus the usual fix list. The patch line is already busy, with 4.4.1 and 4.4.2 on October 7 and 4.4.3 today, so take the newest of the line rather than the headline version.

Analytics, done carefully

The flagship is traffic analytics for Traefik and Caddy, powered by a new Rust service called Sentinel. It ingests the proxies’ JSON access logs and stores aggregated rollups only; the raw access logs stay on your server and rotate on schedule. It is off by default with a per-server toggle, MaxMind is optional for GeoIP, and the dashboards cover requests, bandwidth, unique visitors and p95 latency, with breakdowns by status code, country, device, path, host, referrer and browser. If you are used to bolting a third-party analytics service onto a self-hosted stack and wondering what it keeps, the answer here is designed to be “counts, and only counts.” Two practical notes: Caddy applications need a redeploy when the toggle changes so their logging labels update, and Nginx is out of scope.

The rest of the additions

SQLite arrives as a standalone database option based on a custom image, connectable to an application in one click, with its data volume protected and backups supported, scheduled ones included. Generated container names can take a readable prefix while keeping rolling updates working. You also get OpenID Connect sign-in, and third-party secret managers (Doppler, Infisical and HashiCorp Vault) that resolve {{vault.KEY}} references at deploy time, never store the values in Coolify’s database, and redact them from deployment logs, Cloudflare DNS management, GitHub Actions runners on build servers, Docker registry logins, and a team audit log that captures UI, API, MCP and webhook activity with before-and-after values, encrypted at rest and pruned after ninety days. Team admins can also read the events through the API. The interface gets split action buttons and autofocus on auth forms, and the fix list runs long behind all of it.

My read

The analytics design is the thing to commend: rollups only, opt-in per server, raw logs never leaving the box. That is how a self-hosted platform should ship a feature this intimate, and it sets a bar its competitors will be measured against. The SQLite service covers the long tail of small apps that do not need Postgres, and identity plus secrets are the enterprise-shaped pieces arriving without an enterprise licence key. If you run Coolify, update to 4.4.3 and read the release notes for the one redeploy Caddy users need; if you have been meaning to try it, the 4.4 line is a fine entry point.

Source: the v4.4.0 release.