Skip to content

Warn that the Coolify guide is not for large deployments #666

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bean1352 merged 8 commits into from
Oct 13, 2026
Merged

Warn that the Coolify guide is not for large deployments #666

Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
10bc452
Warn that the Coolify guide is not for large deployments
bean1352 Sep 28, 2026
a93895a
Fix wording and typo
bean1352 Sep 28, 2026
34c75d3
Move Coolify prerequisites out of a second warning callout
bean1352 Sep 28, 2026
1af0d75
Clarify the Coolify single-server limitation
bean1352 Sep 28, 2026
1a938f8
Merge branch 'main' into docs/coolify-scaling-note
bean1352 Sep 30, 2026
5b584a4
Merge remote-tracking branch 'origin/main' into docs/coolify-scaling-…
bean1352 Oct 12, 2026
9d11513
Define small deployments and cite Coolify's Compose limitation
bean1352 Oct 12, 2026
09342a0
Merge branch 'main' into docs/coolify-scaling-note
bean1352 Oct 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions maintenance-ops/self-hosting/coolify.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,12 +7,16 @@ description: "Deploy the self-hosted PowerSync Service on Coolify with Docker Co
[Coolify](https://coolify.io/) is an open-source, self-hosted platform that simplifies the deployment and management of applications, databases, and services on your own infrastructure. Think of it as a self-hosted alternative to platforms like Heroku or Netlify.

<Warning>
Before following this guide, you should:
Use this guide for development or a small deployment, meaning one that a single PowerSync Service container can handle. The [API Containers](/maintenance-ops/self-hosting/deployment-architecture#api-containers) section of Deployment Architecture gives the current connection limit per container.

- Read through the [Service Configuration](/configuration/powersync-service/self-hosted-instances) guide to understand the requirements and configuration options. This guide assumes you have already done so, and will only cover the Coolify specific setup.
- Have Coolify installed and running.
The Compose file in this guide runs the PowerSync Service and its MongoDB storage together on one Coolify server. Coolify's [multi-server deployments](https://coolify.io/docs/core/infrastructure/scaling/multi-server-deployments) do not support Docker Compose applications, so you cannot spread this setup across servers. When you outgrow one container, move to a platform that runs several behind a load balancer, such as [AWS ECS](/maintenance-ops/self-hosting/aws-ecs) or [AWS EKS](/maintenance-ops/self-hosting/aws-eks), and follow the [production deployment architecture](/maintenance-ops/self-hosting/deployment-architecture#production).
</Warning>

## Prerequisites

- Read the [Service Configuration](/configuration/powersync-service/self-hosted-instances) guide first. This page covers only the Coolify side and assumes you know the Service's configuration options.
- Install Coolify and make sure it's running.

## Background

For the PowerSync Service to function correctly, you will need:
Expand Down
Loading