How to choose self-hosted Penpot: Docker, collaboration, and developer handoff for an open-source design tool

Mon, 22 Jun 2026 08:05:45 +0800

penpot/penpot is an open-source design tool. Its positioning is close to Figma, but it emphasizes open source, self-hosting, and collaboration between design and code. It fits teams that want to keep design assets, components, and handoff workflows under their own control.

Project repository:

https://github.com/penpot/penpot

Official site:

https://penpot.app

Who Penpot Is For

Penpot fits these scenarios:

The team wants to use an open-source design tool.
The company does not want all design files to live entirely in a third-party SaaS.
Designers and frontend developers need Inspect Mode, design systems, and component handoff.
The team wants to build long-term design standards around design tokens, components, and variants.

If you only need to draw something quickly as an individual, the online version is easier. Self-hosting is better for long-term team use.

Self-hosting Entry Point

The README does not paste a full Docker Compose file on the homepage. Instead, it points to the official self-host documentation:

`1`	`https://penpot.app/self-host`

For real deployment, follow the official Docker or Kubernetes documentation instead of copying an old compose file from the web. Collaboration tools like Penpot usually involve more than one container. You may also need a database, object storage, background workers, and email service.

A safer self-hosting flow is:

# 1. Read the official self-host documentation first
# 2. Prepare a domain, HTTPS, persistent directories, and a database
# 3. Start it using the official Docker / Kubernetes method
# 4. Create the administrator account
# 5. Import or create team workspaces

Developer Handoff

For developers, one of Penpot’s useful parts is Inspect Mode. After a designer finishes a screen, developers can inspect:

Sizes and spacing.
Colors and fonts.
Component structure.
Design tokens.
Reusable components and variants.

This is more stable than annotated screenshots and fits multi-person collaboration better.

Suggested Team Workflow

You can roll it out like this:

Designers build a design system in Penpot.
Component names stay as close as possible to the frontend component library.
Colors, font sizes, and spacing are managed through tokens.
Developers inspect styles through Inspect Mode instead of relying on verbal descriptions.
Export or back up design files before major version changes.

Notes