PEPenpot
Design interfaces, prototypes and shared design systems collaboratively in a browser.
About this project
Penpot is a graphical interface-design and prototyping product for designers and developers. The documented design core uses open web standards and supports vector design, reusable components and shared design systems.
Core functions include interactive prototypes, real-time collaboration, flex and grid layouts, design tokens and developer handoff. The repository describes optional plugin, API and MCP integration; deploying those integrations is a separate configuration decision.
The reviewed scope is the MPL-licensed design core. A self-hosted installation runs multiple container services and persistent data stores. Commercial administration, SSO and governance features are not assumed to be covered by the design-core license, and the recent 2.18 administration-service changes need version-specific review.
Why it is worth a look
- Vector interface design
- Interactive prototypes
Before you use it
- Review the chosen version and 2.18 administration-service changes
- Back up PostgreSQL and design assets together
- Configure HTTPS for public use
- Distinguish design-core features from paid governance options
Review the chosen version and 2.18 administration-service changes; Confirmed requirements: An always-on device or service; Some requirements have not been verified. Check the official setup instructions.
What it can do
- Vector interface design
- Interactive prototypes
- Real-time collaboration
- Components and design tokens
- Flex and grid layouts
- Developer handoff
- Optional plugin/API/MCP integrations
Who it fits
Designers and developers collaborating on interfaces; Teams with a container/server operator
You require a native offline desktop design application; You assume all paid administration features are MPL-covered
Getting started
- Prepare Docker and Compose and review the official deployment configuration for the selected Penpot version.
- Set the public URL, secret and persistent database/asset volumes; review 2.18 admin-console additions and keep excluded enterprise capabilities separate.
- Start the official Compose deployment, using its documented default port 9001 for an initial local check.
- Configure HTTPS for public access, initialize accounts and verify a sample design/prototype; test database and asset restoration before upgrades.