The essentials · 30-second read
Penpot is an open-source design tool. Cloud: free Professional plan, Unlimited at $7 per editor a month (capped at $175), Enterprise $25 per member. Self-hosting is free.
- Open-source design and prototyping tool (MPL 2.0 licence) with CSS Grid and Flex layouts, components, design tokens, code inspection and an MCP server.
- Cloud prices in USD: Professional $0 (up to 8 team members), Unlimited $7 per editor a month capped at $175, Enterprise $25 per member, Private Server $50k a year.
- Self-hosting is free forever on the Professional plan (Docker, Kubernetes, Elestio); self-hosted Enterprise costs $25 per member a month.
- Our verdict: the serious open alternative to Figma when data control or open source matters; Figma still has the larger ecosystem.
Summarize this page with AI
Penpot is the design tool that most often comes up when a team asks "is there an open-source Figma?". It runs in the browser, works with components, prototypes and design tokens, and can be installed on your own servers. This review explains what Penpot does in 2026, what each plan costs, where your data lives, and when we would recommend it over Figma.
01What is Penpot?
Penpot calls itself "the open-source design platform for teams". It is a design and prototyping tool for interfaces, websites and apps, with one difference from most of its competitors: the code is open source under the Mozilla Public License 2.0, published on GitHub, and you can run it yourself.

The product is developed by Kaleidos, a company whose legal address is in Madrid. Its design choices follow web standards: layouts behave like CSS Flex and Grid, and the platform leans on "open standards like CSS, HTML, SVG and JSON" plus an open file format. That makes the gap between a design and its implementation smaller, which is the main promise to developers.
Penpot comes in two forms. The cloud version is hosted by Penpot, with four plans from free to Private Server. The self-hosted version runs on your infrastructure, free on the Professional edition. Penpot says tens of thousands of organisations of all sizes use it.
02How we look at Penpot at BeBranded
Our own design work happens in Figma: the mock-ups and the design system of our site live there. We do not run Penpot day to day. We discuss it with clients in a few specific situations:
- We recommend Penpot when an organisation must keep design files on its own servers (public sector, health, defence suppliers, strict internal security policies) or when an open-source project wants a tool that matches its values and costs nothing.
- We suggest testing it when a team is reconsidering its Figma budget and mostly needs screens, components and prototypes, not the full plugin ecosystem.
- We advise against a switch when a team depends heavily on Figma plugins, community files or tools that integrate with Figma only. Our UI and UX design and design system work starts from the tool the client's team will actually maintain.
03Key features
- Vector design: shapes, paths, boolean operations, text and images in a browser-based editor.
- CSS Grid and Flex layouts: responsive layouts that follow the same logic as CSS.
- Components and shared libraries: reusable elements across files and teams.
- Native design tokens: colours, typography and spacing values managed as tokens.
- Prototyping: interactions and flows between boards to test journeys.
- Code inspection: developers inspect and integrate code that matches the design.
- Plugins and PenpotHub: plugins, libraries and templates shared by the community.
- MCP server: an open MCP server, with the promise that "any agent can design in Penpot".
- Real-time collaboration: comments and multi-user editing, with unlimited viewers.
- Self-hosting: Docker, Kubernetes (Helm chart), Elestio or TrueNAS.
04Use cases
Design data that must stay in-house
Some organisations cannot store design files with a third-party SaaS: mock-ups reveal unreleased products, internal tools or sensitive data. Penpot self-hosted runs on a Linux server with Docker, so files never leave the company's infrastructure. Plan for someone to maintain the server and apply updates.
Open-source projects
Open-source communities need a design tool that contributors can use without licences. Penpot is free, open, and listed among many open-source projects on its own site. Penpot also offers discounts for open-source, non-profit and education organisations on paid plans.
Design systems close to code
Because layouts follow Flex and Grid and tokens are native, a design system in Penpot maps cleanly to CSS. It suits teams where developers and designers share the same vocabulary. Our design system guide covers how to structure one whatever the tool.
Teams with many viewers
Penpot's free plan counts editors, not viewers: up to 8 team members with unlimited viewers. The Unlimited plan bills per editor with a monthly cap of $175, which keeps the cost predictable for large organisations with few designers.
AI-assisted design
The open MCP server lets AI agents read and modify Penpot files. For teams experimenting with AI in their design process, an open format and an open API reduce the dependency on a single vendor's AI features.
05Penpot pricing in 2026
Prices checked on penpot.app/pricing on 17 November 2026. All prices are in US dollars, per month unless stated. The page does not say whether they are billed monthly or annually, nor whether tax is included.

| Plan (cloud) | ||||
|---|---|---|---|---|
| Professional | Price $0 per user | Team Up to 8 team members, unlimited viewers | Storage Up to 10 GB | Version history and file recovery 7 days |
| Unlimited | Price $7 per editor, capped at $175 a month | Team Unlimited team size | Storage Up to 25 GB | Version history and file recovery 30 days |
| Enterprise | Price $25 per member | Team Unlimited team size | Storage Unlimited | Version history and file recovery 90 days |
| Private Server | Price $50k a year | Team Unlimited team size | Storage Unlimited | Version history and file recovery 90 days |
Unlimited and Enterprise include a 14-day free trial. Enterprise targets organisations that need governance, centralised administration and team permissions; the comparison table lists SSO, a choice of hosting region and IP whitelisting among the governance features. Private Server adds dedicated infrastructure and enterprise-grade support. Non-profit, education and open-source discounts are available on request.
Self-hosting has its own price list (penpot.app/pricing/self-host): the Professional edition is "Free, forever" with unlimited users, teams and files and community support; self-hosted Enterprise costs $25 per member a month, "starting at $950 / month", with an admin console, multiple organisations, SSO and 180 days of history and file recovery.
Is Penpot free? Yes, twice over. The cloud Professional plan is free with all design features for up to 8 team members and 10 GB of storage, and the self-hosted Professional edition is free with no user limit. You pay for more storage, longer history, larger teams in the cloud, or governance features.
06Pros and cons
Advantages
- Open source (MPL 2.0): no lock-in, and you can run it yourself.
- A genuinely useful free plan, plus free self-hosting with no user limit.
- Layouts and tokens that follow CSS, which helps the handoff to developers.
- Predictable pricing: Unlimited is capped at $175 a month whatever the team size.
- Unlimited viewers on every plan.
- An open MCP server for AI agents.
Drawbacks
- A smaller ecosystem of plugins, templates and tutorials than Figma.
- Most clients, freelancers and agencies still send Figma files.
- Self-hosting requires Linux, Docker and someone to maintain the server.
- The cloud hosting country is not stated on the public pages.
- SSO and governance features require Enterprise.
07Our verdict
Who it's for
- Organisations that must keep design data on their own infrastructure.
- Open-source projects and communities.
- Product teams with designers and developers who think in CSS.
- Large organisations with many viewers and few editors.
Who it's not for
- Teams that depend on Figma plugins and community files.
- Agencies that exchange files with many Figma-based partners.
- Teams without anyone able to maintain a self-hosted server, if they need self-hosting.
- Designers who need advanced illustration or photo editing tools.
08Penpot alternatives
| Tool | |||
|---|---|---|---|
| Penpot | Best for Open design, data control | Open source Yes (MPL 2.0) | Self-hosting Yes |
| Figma | Best for Industry standard, ecosystem, collaboration | Open source No | Self-hosting No |
| Sketch | Best for Mac-native interface design | Open source No | Self-hosting No |
| Uizard | Best for Fast AI-generated mock-ups | Open source No | Self-hosting No |
| Whimsical | Best for Wireframes, flows and diagrams | Open source No | Self-hosting No |
Our rule: choose Penpot when open source or hosting control is a requirement, Figma when the team relies on its ecosystem and on exchanging files with partners, Sketch for a Mac-only team attached to a native app, and Whimsical for early wireframes. For a full design-to-site workflow, see our Figma to Webflow guide.
09Penpot vs Figma
Both tools cover interface design, components, prototyping and developer handoff in the browser. The differences sit elsewhere:
- Ownership: Penpot is open source and can run on your servers; Figma is a proprietary cloud service.
- Layout model: Penpot uses CSS Flex and Grid directly; Figma has its own Auto Layout, which developers translate into CSS.
- Ecosystem: Figma has far more plugins, community files, courses and integrations.
- Cost logic: Penpot's free plan has no feature restriction, Unlimited is capped at $175 a month, and self-hosting is free. Figma bills per seat with feature differences between plans.
- Market habits: most freelancers, agencies and design schools use Figma, which matters when you hire or share files.
In practice, Penpot wins when data control, open source or cost predictability matter more than ecosystem. Figma wins when your partners and your team's habits are already there.
10Getting started with Penpot
- Create a free cloud account and rebuild one real screen from your product, not a demo, to judge the layout model.
- Set up tokens and a small component library first: colours, typography, buttons, inputs.
- Ask a developer to inspect the result and compare it with how they would write the CSS.
- Decide on hosting: stay in the cloud, or plan a self-hosted install with Docker if data must stay in-house. Budget the maintenance time.
- Check your plugins: list the Figma plugins the team uses and look for equivalents on PenpotHub before committing.
- Migrate project by project. Keep existing work where it is and start new projects in Penpot. Our design team can help structure the library.
