From 10bc4525de8288281b9f20e95072b7c93409a767 Mon Sep 17 00:00:00 2001 From: bean1352 Date: Mon, 28 Sep 2026 14:33:59 +0200 Subject: [PATCH 1/5] Warn that the Coolify guide is not for large deployments --- maintenance-ops/self-hosting/coolify.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/maintenance-ops/self-hosting/coolify.mdx b/maintenance-ops/self-hosting/coolify.mdx index 9cd9f21f1..0c34eaf5e 100644 --- a/maintenance-ops/self-hosting/coolify.mdx +++ b/maintenance-ops/self-hosting/coolify.mdx @@ -7,6 +7,10 @@ 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. + + This guide is suited to development and small deployments. It runs a single PowerSync Service container, with the API and replication in one process, on one Coolify server. The PowerSyncService scales by adding API containers behind a load balancer, about one per 100 concurrent connections, and Coolify deploys a Compose resource to a single server. For large production workloads, follow the [Deployment Architecture](/maintenance-ops/self-hosting/deployment-architecture#production) guide on a platform that runs multiple containers, such as [AWS ECS](/maintenance-ops/self-hosting/aws-ecs) or [AWS EKS](/maintenance-ops/self-hosting/aws-eks). + + Before following this guide, you should: - Read through the [Service Configuration](/configuration/powersync-service/self-hosted-instances) From a93895ab8b79eaf127cf1098247016780938121f Mon Sep 17 00:00:00 2001 From: bean1352 Date: Mon, 28 Sep 2026 14:39:06 +0200 Subject: [PATCH 2/5] Fix wording and typo --- maintenance-ops/self-hosting/coolify.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/maintenance-ops/self-hosting/coolify.mdx b/maintenance-ops/self-hosting/coolify.mdx index 0c34eaf5e..b295bddeb 100644 --- a/maintenance-ops/self-hosting/coolify.mdx +++ b/maintenance-ops/self-hosting/coolify.mdx @@ -8,7 +8,7 @@ description: "Deploy the self-hosted PowerSync Service on Coolify with Docker Co Think of it as a self-hosted alternative to platforms like Heroku or Netlify. - This guide is suited to development and small deployments. It runs a single PowerSync Service container, with the API and replication in one process, on one Coolify server. The PowerSyncService scales by adding API containers behind a load balancer, about one per 100 concurrent connections, and Coolify deploys a Compose resource to a single server. For large production workloads, follow the [Deployment Architecture](/maintenance-ops/self-hosting/deployment-architecture#production) guide on a platform that runs multiple containers, such as [AWS ECS](/maintenance-ops/self-hosting/aws-ecs) or [AWS EKS](/maintenance-ops/self-hosting/aws-eks). + This guide is for development and small deployments. It runs the PowerSync Service as a single container on one server, and Coolify cannot spread it across servers. For large production workloads, use a platform that runs multiple containers behind a load balancer, such as [AWS ECS](/maintenance-ops/self-hosting/aws-ecs) or [AWS EKS](/maintenance-ops/self-hosting/aws-eks). See [Deployment Architecture](/maintenance-ops/self-hosting/deployment-architecture#production) for the production setup and [Performance and Limits](/resources/performance-and-limits) for the scale the Service can reach. From 34c75d336ae96d8e580ad73027edc6965842daa4 Mon Sep 17 00:00:00 2001 From: bean1352 Date: Mon, 28 Sep 2026 14:41:20 +0200 Subject: [PATCH 3/5] Move Coolify prerequisites out of a second warning callout --- maintenance-ops/self-hosting/coolify.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/maintenance-ops/self-hosting/coolify.mdx b/maintenance-ops/self-hosting/coolify.mdx index b295bddeb..37c8fa696 100644 --- a/maintenance-ops/self-hosting/coolify.mdx +++ b/maintenance-ops/self-hosting/coolify.mdx @@ -11,12 +11,12 @@ Think of it as a self-hosted alternative to platforms like Heroku or Netlify. This guide is for development and small deployments. It runs the PowerSync Service as a single container on one server, and Coolify cannot spread it across servers. For large production workloads, use a platform that runs multiple containers behind a load balancer, such as [AWS ECS](/maintenance-ops/self-hosting/aws-ecs) or [AWS EKS](/maintenance-ops/self-hosting/aws-eks). See [Deployment Architecture](/maintenance-ops/self-hosting/deployment-architecture#production) for the production setup and [Performance and Limits](/resources/performance-and-limits) for the scale the Service can reach. - - Before following this guide, you should: - - 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. - +## Prerequisites + +Before following this guide: + +- Read the [Service Configuration](/configuration/powersync-service/self-hosted-instances) guide to understand the requirements and configuration options. This guide assumes you have done so and only covers the Coolify-specific setup. +- Have Coolify installed and running. ## Background From 1af0d75ce8e18413773451affb1f06acaeb09c7b Mon Sep 17 00:00:00 2001 From: bean1352 Date: Mon, 28 Sep 2026 14:44:51 +0200 Subject: [PATCH 4/5] Clarify the Coolify single-server limitation --- maintenance-ops/self-hosting/coolify.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/maintenance-ops/self-hosting/coolify.mdx b/maintenance-ops/self-hosting/coolify.mdx index 37c8fa696..697b44db7 100644 --- a/maintenance-ops/self-hosting/coolify.mdx +++ b/maintenance-ops/self-hosting/coolify.mdx @@ -8,7 +8,7 @@ description: "Deploy the self-hosted PowerSync Service on Coolify with Docker Co Think of it as a self-hosted alternative to platforms like Heroku or Netlify. - This guide is for development and small deployments. It runs the PowerSync Service as a single container on one server, and Coolify cannot spread it across servers. For large production workloads, use a platform that runs multiple containers behind a load balancer, such as [AWS ECS](/maintenance-ops/self-hosting/aws-ecs) or [AWS EKS](/maintenance-ops/self-hosting/aws-eks). See [Deployment Architecture](/maintenance-ops/self-hosting/deployment-architecture#production) for the production setup and [Performance and Limits](/resources/performance-and-limits) for the scale the Service can reach. + This guide is for development and small deployments. Coolify runs this Compose deployment as a single PowerSync Service container on one server. Coolify can manage several servers, but each resource runs on one [destination](https://coolify.io/docs/knowledge-base/destinations), and Coolify does not load balance a resource across servers. For large production workloads, use a platform that runs multiple containers behind a load balancer, such as [AWS ECS](/maintenance-ops/self-hosting/aws-ecs) or [AWS EKS](/maintenance-ops/self-hosting/aws-eks). See [Deployment Architecture](/maintenance-ops/self-hosting/deployment-architecture#production) for the production setup and [Performance and Limits](/resources/performance-and-limits) for the scale the Service can reach. ## Prerequisites From 9d115132ff9edacd1d8ffe91a902fa7888758f83 Mon Sep 17 00:00:00 2001 From: bean1352 Date: Mon, 12 Oct 2026 09:49:22 +0200 Subject: [PATCH 5/5] Define small deployments and cite Coolify's Compose limitation --- maintenance-ops/self-hosting/coolify.mdx | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/maintenance-ops/self-hosting/coolify.mdx b/maintenance-ops/self-hosting/coolify.mdx index ff82acd6b..de8e4d406 100644 --- a/maintenance-ops/self-hosting/coolify.mdx +++ b/maintenance-ops/self-hosting/coolify.mdx @@ -7,17 +7,15 @@ 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. - This guide is for development and small deployments: workloads that one PowerSync Service container can serve. For the connection limit of one container, see [API Containers](/maintenance-ops/self-hosting/deployment-architecture#api-containers). + 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. - Coolify runs this Compose deployment as a single container on one server. Coolify can manage several servers, but each resource runs on one [destination](https://coolify.io/docs/core/networking/destinations/overview), and Coolify does not load balance a resource across servers. For larger production workloads, use a platform that runs multiple containers behind a load balancer, such as [AWS ECS](/maintenance-ops/self-hosting/aws-ecs) or [AWS EKS](/maintenance-ops/self-hosting/aws-eks). See [Deployment Architecture](/maintenance-ops/self-hosting/deployment-architecture#production) for the production setup and [Performance and Limits](/resources/performance-and-limits) for the scale the Service can reach. + 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). ## Prerequisites -Before following this guide: - -- Read the [Service Configuration](/configuration/powersync-service/self-hosted-instances) guide to understand the requirements and configuration options. This guide assumes you have done so and only covers the Coolify-specific setup. -- Have Coolify installed and running. +- 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