Upsun vs CapRover in 2026: what you give up running your own PaaS

CapRover is a self-hosted PaaS that turns any Linux server into a Heroku-style deployment target. Built on Docker, Nginx, and Let's Encrypt, it gives developers a web dashboard for managing applications, a one-click marketplace of pre-built services, and Docker Swarm clustering for multi-node setups. You install it on any Linux VPS with a single shell command and manage everything through a browser.

Upsun is a managed multi-cloud PaaS that runs application infrastructure across AWS, Google Cloud, Azure, OVHcloud, and IBM Cloud. Teams compare the two because both promise an easier path to deployment than configuring cloud infrastructure directly. The difference is what you give up to get there.

Key takeaways

• CapRover is a self-hosted PaaS that runs on a single Linux server, with optional Docker Swarm clustering for multi-node setups. Upsun is a managed multi-cloud PaaS that runs application infrastructure for you across five cloud providers.
• CapRover is cheaper by monthly invoice and ships with a one-click marketplace that makes spinning up databases and developer tools nearly effortless. Upsun is cheaper by total cost once compliance, autoscaling, and operational hours enter the picture.
• Compliance is non-negotiable. CapRover holds no certifications and changed to a modified Apache license in 2023 that restricts modification of paid features and redistribution. Upsun holds ISO 27001, SOC 2, PCI DSS, HIPAA, and GDPR.
• CapRover fits indie developers, side projects, and teams that want a click-through UI on a small server. Upsun fits autoscaling, multi-cloud deployment, regulated production environments, and teams that want to ship application code instead of managing infrastructure.

In short: CapRover if you want a clickable PaaS on a VPS, Upsun if you want a managed platform that handles scale and compliance for you.

What do Upsun and CapRover have in common?

Both platforms run on the Heroku-style workflow that has shaped modern PaaS. Each supports Git-push deployment, automatic SSL through Let's Encrypt, and a range of languages including Node.js, Python, PHP, Ruby, and Go. Both run applications in isolated Docker containers, and both let you provision databases through the platform rather than configuring them manually.

If your only criterion is "Git push to deploy a containerized app behind a managed reverse proxy," either platform will do the job.

What are the differences between Upsun and Caprover?

Detailed comparison

How do Upsun and Caprover handle hosting and infrastructure?

Upsun runs your application on infrastructure managed across five major cloud providers. You choose where to deploy, and the platform handles provisioning, networking, OS-level updates, and security patching. The same YAML configuration deploys identically across AWS, GCP, Azure, OVHcloud, or IBM Cloud.

CapRover runs on a Linux server you provision yourself. A single shell command installs CapRover, Docker Swarm, Nginx, and Let's Encrypt in roughly 10 minutes on any VPS with a public IP. Once installed, you manage applications through a web dashboard at your captain subdomain. The kernel, OS updates, security patches, firewall, and backups remain yours to manage. CapRover supports multi-node setups by joining additional servers to its Docker Swarm cluster, but Docker has slowed development of Swarm in favor of Kubernetes-based solutions and lists SwarmKit among its retired and deprecated products.

The trade-off is direct: CapRover gives you control of the server and a polished UI on top of it. Upsun removes the server entirely.

How do their deployment workflows compare?

Both platforms deploy from a Git push, but the configuration models differ. Upsun uses a single .upsun/config.yaml file in your repository that defines services, routes, environment variables, and infrastructure for every branch. The config travels with the code, which makes environments reproducible through pull requests.

CapRover applications are configured through the web dashboard, optionally backed by a captain-definition file in your repository that points to a Dockerfile or template. Deployments can come from a Git connection, a CLI command (caprover deploy), a tarball upload, or the one-click app marketplace. The marketplace is one of CapRover's most distinctive features: dozens of common applications, including WordPress, GitLab, Mattermost, MySQL, and MongoDB, deploy with a few clicks and a handful of configuration values.

Teams that want infrastructure-as-code in a single YAML file will prefer Upsun. Teams that want a clickable interface and pre-built one-click installs will prefer CapRover.

Which platform scales better?

Upsun supports automatic horizontal and vertical scaling. Application containers scale based on traffic and resource utilization, and database read replicas can scale independently. Production environments can be cloned in under a minute, with live data, for testing or feature work.

CapRover does not autoscale. You set an instance count manually per application, and Nginx load balances requests across those instances. For multi-node setups, you add servers to CapRover's Docker Swarm cluster and assign workloads to specific nodes through dashboard labels. This works, but Docker Swarm itself has been in maintenance mode at Docker Inc., and most modern container orchestration has moved to Kubernetes. For steady single-server workloads, CapRover scales adequately. For unpredictable traffic, multi-region deployment, or production workloads that need autoscaling, the manual model becomes a bottleneck.

A related limitation worth flagging: CapRover does not deploy Docker Compose stacks natively. If your application uses multiple services (web app, database, cache, background worker), each must deploy as a separate CapRover app, with networking handled through CapRover's internal subdomain routing rather than Compose's shared networks.

What managed services and observability does each platform offer?

Upsun provides a managed services catalog including PostgreSQL, MySQL, MariaDB, Redis, Elasticsearch, OpenSearch, RabbitMQ, and Kafka. Services are provisioned through the YAML config and inherit the platform's backup, scaling, and security policies. Observability comes built in: infrastructure metrics, logs, and continuous profiling are part of the platform.

CapRover's one-click marketplace handles service deployment elegantly. PostgreSQL, MySQL, MongoDB, Redis, and other common services install with a few clicks and run as Docker containers on your CapRover server. The catch is that you operate them. Backups, version upgrades, and security patches for each service are your responsibility. Observability is limited to NetData, which CapRover bundles for system metrics. Application-level metrics, error tracking, and log aggregation require external tools that you assemble yourself.

CapRover wins on installation convenience. Upsun wins on operational simplicity and integrated observability.

How does pricing compare between Upsun and Caprover?

CapRover is free to install and use. A capable VPS from Hetzner, DigitalOcean, or Linode costs $5 to $25 per month, and there are no per-user fees or feature paywalls. In July 2023, CapRover moved from a standard Apache 2.0 license to a modified version that restricts modification of paid features and redistribution of paid versions, though the core platform remains free for self-hosted use.

Upsun uses a Flex pricing model that bills at the resource level for CPU, RAM, and storage. Costs scale linearly with actual usage. For a single small project, Upsun is meaningfully more expensive than self-hosted CapRover. For a team needing observability tooling, compliance certifications, automated backups, and multi-region failover, the comparison shifts once you account for the engineering hours and third-party tooling required to match those capabilities on CapRover.

The honest version: CapRover is cheaper if your time is free and your workload fits on a single server. Upsun is cheaper once either of those stops being true.

Which platform is better for compliance and security?

This is where the comparison ends decisively. Upsun holds ISO 27001, SOC 2, PCI DSS, HIPAA, and GDPR certifications. These are platform-level guarantees that customers inherit when deploying. Security patches, vulnerability management, and infrastructure-level compliance controls are managed by the platform.

CapRover holds no certifications. When you self-host CapRover, you inherit responsibility for your own compliance posture, including OS patching, vulnerability management, audit logging, and access controls. For regulated industries such as healthcare, financial services, or government, CapRover is not a viable production platform without significant additional engineering work. CapRover was built as a developer-friendly self-hosted PaaS for indie developers and small teams, not as a compliance-ready enterprise platform.

When to choose CapRover

CapRover is the right tool when convenience, cost, and a clickable interface matter more than scale and compliance. Pick CapRover if:

• You want a click-through dashboard with a one-click app marketplace for spinning up WordPress, GitLab, MySQL, and similar services.
• You are an indie developer or small team running side projects, internal tools, or a handful of production apps on a small VPS.
• You have basic Linux and Docker familiarity and prefer a no-Kubernetes orchestration model.
• Your applications can deploy as independent services without requiring native Docker Compose support.
• Your workload fits on a single server or a small Docker Swarm cluster.

CapRover has been a stable, popular self-hosted PaaS for nearly a decade. For the right team, it is a better fit than any managed PaaS.

When to choose Upsun

Upsun is the right tool when self-hosted convenience stops being worth the operational and compliance trade-offs. Pick Upsun if:

• Your application carries compliance obligations, including HIPAA, PCI DSS, or SOC 2.
• You need automatic scaling for unpredictable traffic, such as e-commerce flash sales or product launches.
• You operate multi-cloud or need data residency across AWS, GCP, Azure, OVHcloud, or IBM Cloud.
• Your application uses multiple coordinated services that benefit from Docker Compose-style native multi-container support.
• Your team should be writing application code, not patching kernels, managing TLS rotations, or operating Docker Swarm clusters.

The line between "CapRover is enough" and "CapRover is holding us back" usually crosses somewhere between hobby project and serious production workload, or the moment compliance enters the picture. That crossover is when Upsun becomes the cheaper option, even when its monthly invoice is larger.

How do you migrate from CapRover to Upsun?

A CapRover-to-Upsun migration moves your applications, services, and data onto a managed platform. The process involves six main steps:

1. Translate configuration. Move from CapRover's dashboard and captain-definition files to a single .upsun/config.yaml file in your repository. Applications, services, routes, and environment variables are defined in YAML and travel with the code.
2. Map runtimes and build steps. CapRover applications built from Dockerfiles can often run on Upsun with minimal modification, since Upsun supports both buildpack runtimes and custom container builds for major languages.
3. Map managed services. PostgreSQL, MySQL, Redis, and MongoDB are supported by both platforms. Each one-click app from CapRover's marketplace maps to an equivalent Upsun managed service defined in the YAML config.
4. Consolidate multi-service applications. Applications split across multiple CapRover apps (because CapRover does not support Docker Compose natively) can often be combined into a single Upsun project with multiple services defined in one YAML file.
5. Migrate data. Export databases from your CapRover server and import them into Upsun's managed services using standard dump and restore workflows such as pg_dump and mysqldump.
6. Update connection logic. Application code typically needs minor updates to reference Upsun's environment variables and service relationships.

A production migration typically takes 6 to 9 weeks, with the longest phases being infrastructure documentation, MVP testing, and data validation. For CapRover setups with extensive marketplace apps, custom Nginx configuration, or complex Swarm clustering, expect additional time to translate those into Upsun's equivalent constructs.

Frequently Asked Questions (FAQs)

Is CapRover free and open source?

CapRover is free to install and use for self-hosted deployments. Its license status is more nuanced. In July 2023, CapRover moved from a standard Apache 2.0 license to a modified version that restricts modification of paid features and prohibits redistribution of paid versions without a written agreement. The core platform remains free, but the modified license means CapRover is technically source-available rather than fully open source under the strict Open Source Initiative definition.

Can CapRover deploy Docker Compose applications?

Not natively. CapRover deploys each service as a separate application, which means a multi-service stack (app, database, cache, worker) must be split into individual CapRover apps with networking handled through internal subdomain routing. This is one of CapRover's most significant limitations for teams running complex multi-container applications. Platforms like Upsun, Coolify, and Dokploy support multi-service configurations more natively.

Can CapRover scale to multiple servers?

Yes. CapRover supports multi-node clusters through Docker Swarm. You add additional servers to the cluster from the dashboard and assign workloads using node labels. The trade-off is that Docker Swarm itself has been in maintenance mode at Docker Inc. for several years. For teams that need autoscaling, advanced orchestration, or multi-region deployment, a managed PaaS like Upsun is a better fit.

Does CapRover support SOC 2 or HIPAA compliance?

No. CapRover does not hold SOC 2, HIPAA, PCI DSS, or ISO 27001 certifications. When you self-host CapRover, you inherit responsibility for compliance, including OS patching, audit logging, access controls, and vulnerability management. Teams in regulated industries typically need a managed platform with platform-level certifications, such as Upsun.

Does Upsun support multi-cloud deployment?

Yes. Upsun deploys across AWS, Google Cloud Platform, Microsoft Azure, OVHcloud, and IBM Cloud through identical workflows defined in a single .upsun/config.yaml file. Teams can meet data residency, compliance, and latency requirements without rewriting deployment pipelines for each provider. CapRover, by contrast, runs on individual servers you provision yourself and does not abstract multi-cloud deployment.

What is Upsun pricing model?

Upsun uses resource-based pricing, where you only pay for the resources you provision: CPU, RAM, and storage. There are no fixed tiers or surprise bandwidth charges. This is structurally different from CapRover, which is free software billed only through the VPS you run it on. Upsun is more expensive on a monthly invoice but typically cheaper in total cost when engineering hours, observability, and compliance are included.

Is CapRover cheaper than Upsun?

On monthly invoice, yes. A self-hosted CapRover instance on a $10 VPS is significantly cheaper than an equivalent Upsun project. On the total cost of ownership, the comparison narrows once engineering hours, observability tools, backup management, and compliance work enter the calculation. For single-server workloads and indie projects, CapRover is almost always cheaper. For production workloads with operational and compliance requirements, Upsun is often cheaper overall.