# Top self-hosted open-source apps to deploy on Coolify (and how to wire them for production)

> A curated architecture guide to the best self-hosted applications in Coolify’s 300+ service catalog—Supabase, n8n, Directus, Plausible, LiteLLM/Open WebUI, PostGIS, Keycloak, and Uptime Kuma—plus production hardening tips.

For AI agents: curated site map at [https://www.devolute.org/llms.txt](https://www.devolute.org/llms.txt). Canonical HTML (preferred for search engines): [https://www.devolute.org/en/insights/open-source/best-self-hosted-apps-to-deploy-on-coolify](https://www.devolute.org/en/insights/open-source/best-self-hosted-apps-to-deploy-on-coolify).

- Language: en
- Published: 2026-10-27
- Markdown URL: https://www.devolute.org/en/insights/open-source/best-self-hosted-apps-to-deploy-on-coolify.md

## Best self-hosted open-source apps to deploy on Coolify

Which templates from Coolify’s 300+ catalog deliver the highest business value—and what to harden before going live.

One of the main reasons engineering teams adopt **[Coolify](/en/agency/coolify-self-hosted-paas-consulting-deployment)** is its catalog of **more than 300 one-click Docker Compose service templates**. Instead of spending two days writing boilerplate reverse-proxy rules, generating secrets, and wiring container networks, you can spin up a complete open-source tool in minutes.

Crucially, Coolify copies the template's Docker Compose definition into your service at creation time—meaning later upstream catalog changes will not unexpectedly overwrite your running deployment.

Still, not all 300 templates belong in a business stack, and default one-click settings often need a few production tweaks. Below are the **top-ranking open-source apps to deploy on Coolify**, grouped by architectural layer, along with how we wire and harden them in client projects.

## Overview: Top Coolify service templates for engineering & product teams

| Category | Top Coolify Templates | SaaS Replaced | Key Production Hardening Step |
|---|---|---|---|
| **Automation & Workflows** | **n8n** (with Postgres + worker), **Activepieces**, **Hatchet** | Zapier, Make, Workato | Use the Postgres + Redis queue worker variant; set `N8N_ENCRYPTION_KEY` and external S3 backups |
| **Backend & Databases** | **Supabase**, **PocketBase**, **Appwrite**, **PostgreSQL + pgvector / PostGIS** | Firebase, Auth0 + managed DBaaS | Place stateful databases on a dedicated server node separate from build workloads |
| **Headless CMS & Internal Apps** | **Directus** (with PostgreSQL), **Strapi**, **Ghost**, **Appsmith**, **Budibase**, **NocoBase** | Contentful, Webflow, Retool | Mount persistent uploads to S3/MinIO rather than local container volumes |
| **Privacy-First Analytics** | **Plausible Analytics**, **Umami**, **PostHog**, **Matomo** | Google Analytics 4, Mixpanel | Bound ClickHouse/Postgres memory limits so analytics spikes cannot OOM-kill web apps |
| **AI, LLMs & Vector Search** | **Open WebUI**, **LiteLLM**, **Dify**, **AnythingLLM**, **Qdrant**, **Chroma** | ChatGPT Team, proprietary AI gateways | Put behind SSO/OAuth and connect to dedicated GPU inference or EU API gateways |
| **Identity, Docs & Ops** | **Keycloak**, **Authentik**, **Docmost**, **Outline**, **Documenso / DocuSeal**, **Uptime Kuma**, **Grafana**, **Beszel**, **MinIO** | Okta, Notion, DocuSign, Datadog | Isolate Uptime Kuma / monitoring on a separate node from the workloads it monitors |

## 1. Workflow automation: n8n & Activepieces

 **[n8n](/en/agency/n8n-automation-agency)** is consistently the #1 business service deployed on Coolify.

- **Which template variant to pick:** Coolify ships three n8n variants (`default`, `with postgresql`, and `with postgres and worker`). Skip the SQLite default for anything beyond personal testing. Choose **n8n with PostgreSQL and Worker** (Redis + queue mode) so webhook bursts and long-running AI agent steps do not block the main UI process.
- **Integration idea:** Connect n8n over Coolify's internal Docker network directly to your **PostgreSQL**, **Directus**, or **[Nextcloud](/en/agency/nextcloud-enterprise-consulting-integration-hosting)** containers without traversing the public internet.

## 2. Backend-as-a-Service & spatial databases: Supabase, Appwrite, PocketBase & PostGIS

- **Supabase:** Coolify's one-click Supabase stack spins up PostgreSQL, GoTrue (Auth), PostgREST, Realtime, Storage, Kong API Gateway, and Supabase Studio. Because the full stack runs ~10 containers, deploy it on a dedicated VPS (minimum 4 vCPUs / 8 GB RAM) and immediately configure automated S3 backups for the Postgres database and Storage buckets.
- **PocketBase & TrailBase:** When you want an ultra-fast, single-binary backend with embedded SQLite, real-time subscriptions, and auth that consumes less than 100 MB of RAM, PocketBase on Coolify is unbeatable for MVPs and internal tools.
- **PostgreSQL + pgvector + PostGIS + Martin:** For data-intensive products, we combine **[PostgreSQL AI backends](/en/agency/postgresql-ai-backend)** and **[PostGIS geospatial platforms](/en/agency/postgis-geospatial-platform)** with Coolify's **Martin** template (a blazing-fast Rust PostGIS vector tile server) to feed **[deck.gl](/en/agency/deck-gl-data-visualization)** maps.

## 3. Headless CMS, customer portals & low-code: Directus, Appsmith, Docuseal

- **Directus (with PostgreSQL):** Introspects any SQL schema and instantly provides a clean REST/GraphQL API plus a customizable data studio for operations teams. Configure Directus on Coolify to use **MinIO** or external S3 for asset storage so container redeploys remain stateless.
- **Appsmith / Budibase / NocoBase:** Ideal for building internal admin panels over your PostgreSQL databases in hours instead of weeks.
- **Documenso & DocuSeal (with Postgres):** Self-hosted open-source alternatives to DocuSign for legally binding PDF contract signing workflows, easily triggered via webhook from n8n or your CRM.

## 4. GDPR-friendly web & product analytics: Plausible & Umami

European teams frequently use Coolify to replace Google Analytics with cookie-free, GDPR-compliant analytics:

- **Plausible Analytics (Community Edition):** Powered by PostgreSQL and ClickHouse. Because ClickHouse is memory-hungry, always set explicit Docker memory limits (`deploy.resources.limits.memory`) in the Coolify Compose editor so background merges do not starve co-located services.
- **Umami:** A lighter-weight PostgreSQL-backed alternative when you want clean traffic and event metrics on a smaller server footprint.

## 5. Self-hosted AI & RAG orchestration: LiteLLM, Open WebUI, Dify & Qdrant

Coolify makes standing up the control plane of a **[self-hosted AI stack](/en/agency/open-source-ai-infrastructure)** remarkably fast:

- **LiteLLM Proxy:** Deploy LiteLLM on Coolify as a unified OpenAI-compatible gateway that manages API keys, per-team token budgets, fallbacks, and routing across OpenAI, Anthropic, Mistral, and your own vLLM/Ollama GPU nodes.
- **Dify & AnythingLLM:** Visual RAG and agent workflow builders that connect to **Qdrant** or **Chroma** vector databases (also available as one-click Coolify templates) and **Browserless** (headless Chrome for web scraping) or **Gotenberg** (stateless PDF generation API).

## 6. Identity, knowledge wikis & observability: Keycloak, Docmost, Uptime Kuma & Beszel

- **Keycloak or Authentik:** Anchor your entire Coolify estate in single sign-on. Put **[Keycloak](/en/agency/keycloak-sso-implementation)** in front of Directus, Grafana, Outline/Docmost, and internal dashboards.
- **Docmost & Outline:** Fast, modern open-source alternatives to Notion and Confluence for engineering and company documentation.
- **Beszel, Uptime Kuma, Dozzle & GlitchTip:**
  - **Beszel** (and its lightweight agent) gives you clean CPU, RAM, disk, and Docker container metrics across all your Coolify servers.
  - **Dozzle** provides real-time container log search.
  - **GlitchTip** or **Bugsink** gives you self-hosted, Sentry-compatible error tracking without per-event overage fees.

## 4 production rules before relying on Coolify templates

1. **Pin image tags:** Change `:latest` in template Compose files to explicit semantic versions (e.g., `n8nio/n8n:1.85.2`) so a routine restart never triggers an unplanned major upgrade.
2. **Separate build servers from database servers:** Connect at least two servers in Coolify—run builds and preview deployments on a dedicated build VPS, and keep stateful production databases on an isolated node.
3. **Verify S3 backup restores:** Connect Coolify's built-in database backup scheduler to Hetzner Object Storage, AWS S3, or Backblaze B2—and test restoring a dump into a staging container monthly.
4. **Lock down the control plane:** Never leave port `8000` exposed to the public internet without MFA, IP allowlisting, or a Cloudflare Access / WireGuard tunnel.