Early Access to Black Friday DealsFlyWP Lifetime Deal → Pay Once, Fly Forever

Grab Early Bird Deal

Containerized app management

Deploy & Manage Docker Compose Apps with FlyWP

Deploy Docker Compose apps beyond WordPress—all from your FlyWP dashboard. Launch ready-made templates or bring your own Compose files, then manage configurations, deployments, backups, and logs in one place.

Get Started with FlyWPExplore Docker Compose Apps

Your applications. Your containers. One management platform.

Docker Compose app management alongside your WordPress sites, on the same Docker-based FlyWP servers.

Get Started with FlyWP

  • Bring your Compose-based stacks

    Run applications beyond WordPress, Node.js, and one-click apps using Compose configurations that follow FlyWP’s Compose file rules.

  • Start with ready-made templates

    Launch popular self-hosted applications from built-in templates instead of configuring every service from scratch.

  • Simplify application management

    Manage deployments, environment variables, resource limits, backups, and logs without relying entirely on the command line.

  • Keep applications organized

    Each application gets dedicated pages for domains, configuration, deployments, backups, and logs.

Start with a template or bring your own Compose file

Deploy Docker Compose apps from four supported sources. FlyWP validates your Compose configuration before deployment and keeps a managed copy for your application.

  • Built-in templates

    Select a ready-made application template and fill in the required environment values.

    Directus, Ghost, n8n and more

  • Paste a Compose file

    Add your Docker Compose YAML directly in FlyWP.

    docker-compose.yml

  • GitHub repository

    Import your Compose file from a connected repository and branch.

    flydemo/api · main

  • Remote Compose URL

    Fetch a Compose file from a public HTTPS link.

    https://…/compose.yml

Ready-made templates for popular self-hosted apps

Self-hosted app hosting without the setup work. Start with a preconfigured application stack and provide the required environment values before deployment.

  • Directus
  • Ghost
  • Mautic
  • Metabase
  • n8n
  • Nextcloud
  • Open WebUI
  • Plausible CE
  • Umami
  • Vaultwarden

From Compose file to running application

A complete Docker application deployment workflow, right inside your server’s Create New Site flow.

  1. 1

    Create your application

    Choose Docker Compose App in Create New Site, then pick a template or your own Compose configuration.

  2. 2

    Configure your domain

    Use a FlyWP test domain or your own. FlyWP can create the DNS record through Cloudflare.

  3. 3

    Set environment variables

    Add the variables your app needs, import a .env file, and mark sensitive values as secrets.

  4. 4

    Review and deploy

    Name your application, review its services and resource requirements, and start deployment.

  5. 5

    Manage your application

    Follow deployment progress, then manage the running app from its own dashboard.

Before you start

Paid FlyWP planNot available on trial serversServer with at least 512 MB memoryTeam owners and team admins create appsCompose files must follow FlyWP’s rules

Every deploy. Every change. Under your control.

Deployment control without the complexity.

  • One-click redeployment. Redeploy with the current Compose configuration, environment variables, and resource settings.
  • Automatic rollback. Set a health-check window from 1 to 30 minutes; if a deployment fails its check, FlyWP can roll back to the previous version.
  • Manual rollback. Return to an earlier deployment whenever you need to.
  • Version comparison. Compare Compose files, environment variables, images, and resource limits between versions. Secret values stay hidden.
  • Push-to-deploy. Trigger a deployment whenever you push to the configured GitHub branch.

Flexible configuration. Clear resource controls.

  • Environment variable management. Add, edit, remove, and import variables. Mark secrets and review missing or unused variables.
  • Compose file editor. Edit your Compose configuration in FlyWP and validate it before you deploy.
  • CPU and memory limits. Set CPU, memory, and process limits for individual services.
  • Private registry support. Manage team registry credentials and choose the login to use for private images.
  • Centralized configuration. Keep the Compose file, variables, and resource settings together on the app’s dashboard.

Manage more than just deployment

Backups, restores, and logs for every containerized application.

Backups and restore

  • Scheduled backups. Hourly or daily, with your choice of storage destination and retention period. Availability depends on your plan.
  • Manual backups. Take a snapshot whenever you want an extra restore point.
  • Safety backups. Taken automatically before deployments, rollbacks, and restores.
  • Restore. Bring application data and configuration back to an earlier backup.

Live and deployment logs

  • Live application logs. Stream logs in your dashboard and download log files for troubleshooting.
  • Deployment logs. Review deployment results and investigate failed deployments.

Move and duplicate applications with more control

  • Clone applications. Copy a deployed app to another eligible server in your team for testing or an extra instance.
  • Transfer applications. Move an app and its data to another supported server in your team, including servers on other cloud providers.
  • Advanced settings. Use advanced mode and deployment time-limit settings when you need them.
  • Delete applications. Remove apps you no longer need, after reviewing what data is affected.

Built for more than WordPress

One FlyWP platform. More applications to run.

A Docker Compose management platform that sits next to your WordPress and Node.js deployments.

  • For developers

    Deploy custom Compose stacks and manage configuration without handling every routine task over SSH.

  • For agencies

    Manage client applications alongside WordPress projects on one infrastructure platform.

  • For SaaS teams

    Run supported self-hosted tools, databases, and application stacks on your FlyWP servers.

  • For hosting providers

    Go beyond WordPress hosting by managing additional containerized applications.

Everything you need to manage Docker Compose apps

  • Ready-to-deploy application templates
  • Docker Compose YAML support
  • GitHub repository integration
  • Remote Compose file import
  • Compose file validation
  • Custom domain and SSL management
  • Environment variable and secret management
  • CPU, memory, and process limits
  • GitHub Push-to-deploy
  • Deployment history and version comparison
  • Automatic and manual rollback
  • Scheduled and manual backups
  • Backup restoration
  • Live application logs
  • Private registry credentials
  • Application cloning and transfer
  • Advanced application settings

Try FlyWP Before You Deploy

Explore FlyWP for 48 hours before committing to a new Managed Server. Get familiar with the dashboard and see how FlyWP fits your workflow.

Start Your 48-Hour Trial

Docker Compose Apps need a paid FlyWP plan and aren’t available on trial servers. Use the trial to explore FlyWP, then add Compose apps after you upgrade.

Docker Compose Apps FAQs

What are Docker Compose Apps in FlyWP?

Docker Compose Apps let you deploy and manage containerized applications using Docker Compose configurations directly on your FlyWP servers.

Can I deploy applications other than WordPress?

Yes. Docker Compose Apps are built for applications beyond WordPress. You can run a ready-made template or your own Compose stack on the same FlyWP server as your WordPress sites.

Does FlyWP provide ready-made Docker Compose templates?

Yes. FlyWP includes built-in templates for popular self-hosted apps such as Directus, Ghost, Mautic, Metabase, n8n, Nextcloud, Open WebUI, Plausible Community Edition, Umami, and Vaultwarden. Pick one and provide the required environment values before deployment.

Can I use my own Docker Compose file?

Yes. You can paste your Compose YAML, import it from a connected GitHub repository and branch, or fetch it from a public HTTPS link. FlyWP validates the configuration before deployment, and your Compose file must follow FlyWP’s Compose file rules.

Can I automatically deploy Docker Compose applications from GitHub?

Yes. With Push-to-deploy, FlyWP triggers a deployment whenever you push to the GitHub branch you configured for the application.

Can I manage environment variables in FlyWP?

Yes. You can add, edit, remove, and import variables from a .env file, mark sensitive values as secrets, and review missing or unused variables. Secret values stay hidden when you compare versions.

Can I configure CPU and memory limits?

Yes. You can set CPU, memory, and process limits for individual services in your application.

Does FlyWP support Docker Compose application backups?

Yes. You can schedule hourly or daily backups with your choice of storage destination and retention period, take manual snapshots, and restore an earlier backup. FlyWP also takes safety backups automatically before deployments, rollbacks, and restores. Backup availability depends on your plan.

Can I roll back a failed deployment?

Yes. Set a health-check window from 1 to 30 minutes and FlyWP can roll back to the previous version if a deployment fails its check. You can also return to an earlier deployment manually at any time.

Can I clone or transfer a Docker Compose App?

Yes. You can clone an application to another eligible server in your team, or transfer the app and its data to another supported server in your team, including servers on other cloud providers.

Are Docker Compose Apps available on the FlyWP Free plan?

No. Docker Compose Apps need a paid FlyWP plan and aren’t available on trial servers. You can use the 48-hour trial to explore FlyWP, then add Compose apps after you upgrade.

What are the server requirements for Docker Compose Apps?

Your server needs at least 512 MB of memory, and your Compose file must follow FlyWP’s rules. Only team owners and team admins can create applications. Some templates need more memory, which each template card shows before you deploy.

Does FlyWP support every Docker Compose configuration?

No. Compose files must follow FlyWP’s Compose file rules. FlyWP validates your configuration before deployment and keeps a managed copy for your application.

Your Docker Compose workflows. Now easier to manage.

Bring your containerized applications to FlyWP. Deploy, configure, monitor, and maintain your applications through one centralized platform.

Get Started with FlyWPRead the Documentation

Wait!

Are You Really Leaving?

White Label Included

FlyWP Lifetime Deal
Pay Once, Fly Forever

Black Friday Special 🔥
Secure Your Lifetime Deal