Loading content
Penpot is an open-source design and prototyping platform for cross-functional product teams. It supports collaborative vector editing, interactive prototypes and design systems with a web-based, self-hosted or cloud option. It aims to bridge design and engineering by producing developer-friendly assets and exports.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Usable application software: supports people in a task.
Concrete cog in the system that works inside larger relationships.
An open-source platform for collaborative UI design, prototyping, and design systems with bridges to engineering.
Penpot was developed by Kaleidos as an open-source design tool and publicly introduced in 2021. It responded to the dependence of collaborative design work on proprietary SaaS tools, expanding vector design, prototyping, design systems, and self-hosting.
Teams edit vectors and components together in a browser, connect screens into interactive prototypes, and share design systems. Engineers can use CSS, SVG, and other inspection or export information. Open formats and self-hosting increase control, but teams still need rules for versioning, accessibility, and handoff.
Vector-based interfaces and components are created and maintained collaboratively.
Linked screens make interactions and flows testable early.
Inspection and exports help translate design into implementation.
Penpot matters to teams connecting design and engineering collaboratively while requiring data control or self-hosting. Hosting, permissions, component maintenance, and handoff quality deserve review.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.