# Docker Compose Apps

> Run your own Docker Compose app on a FlyWP server: create it from a compose file, a link, GitHub or a template, then manage its domains, deploys, settings and backups.

Source: https://flywp.com/docs/site/docker-compose-apps/

A Docker Compose App runs a set of containers from a Docker Compose file on your FlyWP server. Use it for anything that isn't WordPress, Node.js or a one-click app, like a database with a web frontend, or a stack you already run with Docker Compose.

FlyWP validates your Compose file, saves a managed copy, and deploys it to your server. Every app gets dedicated management pages for domains, deploys, settings, backups, and logs. Explore the guides below to learn how each part works.

![A running app's Overview page, with the app sidebar (Overview, Domains, Deploys, Configurations, Backups, Logs and Settings) and the Services card](https://flywp.com/wp-content/uploads/2026/11/compose-app-sidebar.png)

## In this section

- [Create an app](https://flywp.com/docs/site/docker-compose-apps/create-an-app.md): Create a Docker Compose App from a pasted file, link, GitHub repository, or template, configure domains and environment variables, and deploy it.
- [Deploys](https://flywp.com/docs/site/docker-compose-apps/deploys.md): Redeploy a Docker Compose App, roll back failed deploys, compare versions, automate deploys with Git push, and manage registry credentials.
- [Configure](https://flywp.com/docs/site/docker-compose-apps/configure.md): Update environment variables, edit the Compose file, and adjust CPU and memory limits for your Docker Compose App, then deploy your changes.
- [Backups](https://flywp.com/docs/site/docker-compose-apps/backups.md): Configure backup destinations and schedules for a Docker Compose App, run on-demand backups, inspect contents, and restore data.
- [Logs](https://flywp.com/docs/site/docker-compose-apps/logs.md): View real-time logs for a Docker Compose App, search log output, inspect deploy logs, and download log archives.
- [Compose file rules](https://flywp.com/docs/site/docker-compose-apps/compose-file-rules.md): Learn what FlyWP accepts, modifies, and blocks in Compose files, including size limits, reserved settings, and advanced mode exceptions.
- [Clone and transfer](https://flywp.com/docs/site/docker-compose-apps/clone-and-transfer.md): Clone a Docker Compose App with its data to another server in your team, or transfer the app entirely.
- [Advanced and delete](https://flywp.com/docs/site/docker-compose-apps/advanced.md): Enable advanced mode for a Docker Compose App, configure deploy timeouts, and safely delete an app.

## Before you begin

Make sure you have:

- A paid FlyWP plan (Docker Compose Apps aren't available on the Free plan).
- A server in your team that supports apps (trial servers can't run them).
- A server with at least 512 MB of memory. The creation flow displays each app's memory requirements, and templates that require more RAM than your server has free are flagged.
- A team owner or team admin role. Other roles can't create apps.

If any requirement isn't met, the **Create Site** dialog explains why on the Docker Compose App card and prevents you from continuing.

A server can be large enough and still have no room. If its other apps use all the memory it sets aside for apps, the card says: "No memory is free for Docker Compose Apps on this server: its other apps use it." Lower the limits of those apps on their **Resources** pages, or choose another server.

## What you can do with an app

- Start from a template, paste a Compose file, link to a remote file, or select a file from a GitHub repository.
- Connect one or more domains and let FlyWP automatically secure them with SSL. See [Domains and SSL](#domains-and-ssl).
- Update environment variables, edit the Compose file, adjust resource limits, and apply your changes with a new deploy.
- Roll back, redeploy, compare versions, and deploy automatically on each push to a branch.
- Schedule automatic backups, take manual snapshots on demand, and restore them.
- Stream live logs and download log files.
- Clone or transfer the app to another server in your team.

## Domains and SSL

The **Domains** page lists every domain of your app, the service and port each one goes to, its SSL state, and its status. The main domain has a **Main** badge. It is the address FlyWP shows for the app. To remove the main domain, make another domain main first.

For a domain that is waiting for DNS, two buttons appear in its row: **Check DNS again** and the lock button (**Certificate**). Add an A record that points the name to your server, remove any AAAA record for the name, then click **Check DNS again**. If a certificate fails, the lock button reads **Try SSL again**. Once the name points to your server, SSL starts on its own.

Use the lock button to add your own certificate or a Cloudflare Origin certificate instead.

:::note
FlyWP starts up to 12 certificates an hour for each app. The dashboard and the API share this limit. If you reach a limit, the page tells you how long to wait, for example "Too many requests. Try again in 5 minutes."
:::

## Read next

- [Create an app](https://flywp.com/docs/site/docker-compose-apps/create-an-app/) walks you through the four-step setup process.
- [Compose file rules](https://flywp.com/docs/site/docker-compose-apps/compose-file-rules/) covers what FlyWP allows, adjusts, or blocks in your Compose files.
