Penpot
Self-hosted collaborative interface design and prototyping platform.
4 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Application platform deployment
Runs in
Documented customer environment
Penpot frontend, backend, exporter, PostgreSQL, cache and object storage.
- Vultr: Customer cloud account
- Railway: Customer platform workspace
- Railway
- Vultr
Servers / containers
Operated by
Your team
Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Deployment boundaries by provider
- Vultr: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Vultr Docs ↗ · Source checked 2026-11-19
- Railway: Customer platform workspace · Customer-operated
Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Railway ↗ · Source checked 2026-11-19
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Application platform deployment |
|---|---|
| Infrastructure | Servers / containers Penpot frontend, backend, exporter, PostgreSQL, cache and object storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure. |
| Licensing model | Open Source / Open Core Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
| License | Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
5 of 12 fields researched (42%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
The self-hosted configuration guide documents generic OIDC and named OAuth providers. Configure the backend credentials, enabled-login flags and callback URL; LDAP and the application admin surface are separate considerations.
Penpot self-hosted application-user identity configuration · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The official self-hosting guide supplies a Compose file with frontend, backend, exporter, PostgreSQL and persistent assets. Replace the example master secret/database credentials and pin compatible images. A single PostgreSQL container is not database HA.
Upstream Penpot Compose deployment; verify compatibility with the selected provider package · Source ↗ · Deployment artifact ↗ (develop (moving branch)) · Reviewed 2026-11-20
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The upstream settings guide describes 4 CPUs/16 GB RAM as a reference and recommends an elastic 50–100 GB database starting point for up to ten editors, with growth driven by files and usage. These are vendor guidelines, not a validated 100-user/1-TB HA configuration; add database/asset backups and replicas separately.
Upstream reference settings and elastic database guidance; not a guaranteed capacity benchmark · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Penpot; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
Reviewed upstream 2.19.3 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence.
Penpot upstream application; verify compatibility with the selected package · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
Show all fields (7 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
Design data, object storage, exports and database must be backed up together; externally configured integrations remain outside the server.
Community & maintenance
The reviewed upstream contributor history includes niwinz, Alotor, superalex, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.
Category fit
- Collaboration
- Self-hosted collaborative interface design and prototyping platform.
Compare within Collaboration
- 3CX Self-HostedCommercial business communications and PBX platform installed into the customer's public-cloud account.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Apache AnswerSelf-hosted community questions, answers and knowledge content.
- AWS
- DigitalOcean
- Railway
- Linode
- Vultr
- Hostinger
- LumaDock
- BigBlueButtonSelf-hosted conferencing and virtual classroom platform.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Hetzner
- Scaleway
- BookStack Self-HostedSelf-hosted wiki and documentation organized into books, chapters and pages.
- AWS
- DigitalOcean
- Linode
- Vultr
- Hostinger
- LumaDock
- Campfire (ONCE)Self-hosted group chat and team conversation application.
- DigitalOcean
- Collabora Online (CODE)Community office editing server for integration with a document platform.
- AWS
- DigitalOcean
- Hetzner
- Linode
- Vultr
- Hostinger
- LumaDock
- Confluence Data CenterCommercial self-managed Confluence edition for enterprise collaboration and knowledge management. New Data Center subscriptions are restricted to eligible existing Atlassian customers.
- AWS
- Azure
- Google Cloud
- DiscourseSelf-hosted discussion and community platform for workplace collaboration and customer support communities.
- AWS
- Google Cloud
- DigitalOcean
- Hetzner
- Linode
- Vultr
Showing 8 of 25 other listings in Collaboration. These products address related workflows; read their category-fit notes before comparing scope. See all of Collaboration →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Vultr Docs ↗docs.vultr.com
- Railway ↗railway.com
- MPL-2.0 LICENSE ↗github.com
- Releases v2.19.3 ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Vultr Docs ↗ · Vultr
Provider guide · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Penpot frontend, backend, exporter, PostgreSQL, cache and object storage. Design data, object storage, exports and database must be backed up together; externally configured integrations remain outside the server.
- Railway ↗ · Railway
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Penpot frontend, backend, exporter, PostgreSQL, cache and object storage. Design data, object storage, exports and database must be backed up together; externally configured integrations remain outside the server.
- Vultr Docs ↗ · Vultr
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Community, governance or adoption evidence ↗github.com
- Upstream project ↗github.com