Penpot Free Cloud vs Self-Host: Choosing a Path for an Indie Team

The cost is operational. The official Docker guide requires Docker and Docker Compose, basic DNS management, and proxy configuration. You also need a domain, TLS, backup policy, monitoring, and an administrator rotation. A free installation route does not make the underlying infrastructure free or maintenance-free.

Installation and upgrades are ongoing work

The official guide provides a Docker Compose example, startup commands, and a version variable. After the first install, decide whether to pin PENPOT_VERSION, when to pull new images, and how to move through small version increments. The guide recommends small updates rather than jumping between distant releases. Restore a backup in an isolated environment before each upgrade, then verify login, files, collaboration, and export.

Network exposure needs a visible acceptance result. The default service listens on a local port; a team-facing deployment needs a reverse proxy and domain configuration. Put these checks in the deployment runbook so “the container started” is not confused with “the team can use the service safely.”

Ask about storage, history, and governance

The cloud pricing page lists storage, autosaved versions, file recovery, team size, and governance by tier. Professional shows unlimited teams and files within storage capacity, while higher tiers add space, history, SSO, or IP allowlisting. Self-hosting does not automatically grant a cloud tier’s operational service. Your team chooses disk capacity, snapshots, and recovery drills.

For a two- or three-person project, validating the workflow in Cloud is often easier than operating a server immediately. If you already have container, backup, and access-control standards, self-hosting becomes more manageable. The key question is whether someone can handle an upgrade or incident before a release, not whether a machine exists.

Make the choice from team conditions

Choose Cloud when the project needs a quick start, the team is small, hosting is acceptable, and no one wants to maintain Docker services. Choose self-hosting when data must stay on your network, independent access controls are required, or the team already operates containers, backups, and monitoring. In either case, validate invitations, file recovery, and export with a small project.

Write a responsibility page after deciding. For Cloud, record the admin, billing owner, and sharing policy. For self-hosting, record the server owner, version, backup location, recovery target, and upgrade window. That turns a “free” decision into something another teammate can operate.

Is Penpot Cloud Professional really free

The current pricing page shows Professional at $0 per user per month and calls it free and fully featured. Cloud use still follows account, storage, and service rules.

What skills does self-hosted Penpot require

The Docker guide lists Docker, Docker Compose, basic DNS, and proxy configuration. Your team also owns backups, updates, and incident response.

Does self-hosting automatically reduce total cost

No conclusion follows from the software install path alone. Servers, storage, networking, and maintenance time belong in the total cost.

Should an indie team start in Cloud or self-host

Start in Cloud when you need fast collaboration and lack operations capacity. Consider self-hosting when you already operate containers and backups or must keep data on your own network.