Penpot

Open-source design and prototyping, honestly reviewed. No marketing fluff, just what you get when you self-host it.

TL;DR

• What it is: Open-source (MPL-2.0) design and prototyping platform — think Figma, but your data lives on your server and Figma can’t raise your bill or lock your files [5].
• Who it’s for: Design teams and product founders who want Figma-level collaboration but can’t stomach $15–$45/editor/month, plus developers who hate the “handoff” step because Penpot outputs real CSS and SVG instead of static specs [3][5].
• Cost savings: Figma’s Professional plan runs $15/editor/month (annual) or $20 billed monthly. A 5-person design team pays $75–$100/month before they’ve opened a single file. Penpot self-hosted runs on a $6–10 VPS, free for all users [5].
• Key strength: It speaks developer natively. Penpot expresses layouts as CSS Flexbox and Grid, not a proprietary abstraction. The inspect tab gives you copy-paste CSS, SVG, and HTML — not a “specs panel” that a developer has to interpret [3][homepage].
• Key weakness: Still rougher around the edges than Figma. A frank AlternativeTo reviewer calls it “raw as a butchered chicken” and lists real friction points: freezes when working with images, unintuitive path editing, unpredictable undo/redo [2]. Not production-ready for every team, and the self-host setup is non-trivial if you’ve never touched Docker.

---

What is Penpot

Penpot is a browser-based design, prototyping, and developer-handoff platform. You build UI screens, create component libraries, define design tokens, wire up interactive prototypes, and hand off to developers — all in one tool. The key pitch is that it’s the first major open-source design tool built on open web standards: SVG, CSS, HTML, and JSON [README].

That last point matters more than it sounds. Figma stores your designs in a proprietary binary format. Move to another tool and you export whatever Figma decides you can export. Penpot’s files are SVG-native, which means the design layer and the code layer aren’t two separate things that have to be synchronized — they’re the same thing represented differently [3][homepage].

The project is developed by Kaleidos, a Spanish open-source company, and has been running since 2019. As of this review it sits at 44,888 GitHub stars. The website claims 600,000 teams are using it [homepage]. Version 2.0 was a major milestone: it shipped CSS Grid Layout natively, a complete UI redesign, a new component and variants system, and native design tokens [README].

---

Why people choose it over Figma, Sketch, and Adobe XD

The third-party articles and community reviews converge on a few recurring themes: cost, data ownership, and developer workflow. The complaints about Figma keep appearing: it’s cloud-only, files disappear if you stop paying, and the inspect panel generates specs that developers still have to translate.

Versus Figma. This is the fight Penpot picks. The XDA Developers article [5] frames it cleanly: “Figma has become the industry standard for UX/UI design, offering a powerful cloud-based platform where teams can collaborate on digital projects. However, its reliance on proprietary cloud storage, subscription costs, and data privacy concerns have led some designers to look for self-hosted alternatives.”

For a 5-person team, Figma Professional at $15/editor/month is $900/year. Figma Organization is $45/editor/month — $2,700/year. When Adobe tried to acquire Figma for $20 billion and regulators blocked it, the event reminded many teams exactly how much vendor leverage they’d handed over [5]. Penpot self-hosted costs the VPS you’d probably already be running.

The developer handoff angle is the other real differentiator. An AlternativeTo commenter [2] sums up the designer perspective: “The controls felt very intuitive to me — they map nicely to the mental models of actual CSS. I LOVE the wrapping options as well. I also really appreciate how developer-friendly this is, so handoff becomes simple.” The key insight: Penpot’s auto-layout behaves like CSS Flexbox. When a developer opens the inspect panel, the output is already CSS they can use, not a pixel specification they have to re-implement.

Versus Figma on design systems. Penpot has native design tokens — a single source of truth for colors, typography, spacing, and shadows that syncs across components [README]. It also has variants, which let you group component states (button/default, button/hover, button/disabled) in the same way Figma’s component variants work. For teams building and maintaining a design system, this is table stakes, and Penpot has it [2].

On data sovereignty. The self-hosting argument isn’t hypothetical. SaaS design tools see your unreleased product designs. For a startup working on something pre-launch, that’s real IP flowing through servers you don’t control. Penpot self-hosted keeps every pixel in your infrastructure [5].

Where it genuinely struggles. The negative reviews are worth reading because they’re specific. One AlternativeTo reviewer [2] writes: “Unfortunately it’s raw as a butchered chicken at the moment; the functionality may be good but the user experience is just awful. Freezes when working with images, editing paths is unintuitive, undo/redo changes random stuff, shapes jump and twist when moving/transforming them.” Another flags missing mobile support and a tricky Podman setup that required GitHub issue research to resolve [2]. This isn’t cherry-picked — the same reviewer gives the product credit for good features. These are real friction points in real use.

---

Features: what it actually does

Core design:

• Vector editing, frames, boolean operations [README]
• Auto-layout with Flexbox and CSS Grid behavior natively — not a Figma-style abstraction [README][homepage]
• Component library with master components, overrides, and variants [README][2]
• Native design tokens for colors, typography, spacing, shadow, and more [README]
• Assets panel with team-shared libraries [README]
• Custom fonts, gradient fills, effects [2]

Prototyping:

• Interactive flows with click/hover/drag interactions [homepage]
• Transitions and animations between frames [homepage]
• Presentation mode for stakeholder review [homepage]

Developer handoff:

• Inspect tab with CSS, SVG, and HTML output — copy-paste ready [homepage][3]
• Spec view with measurements, colors, typography details [homepage]
• Open SVG export — designs are SVG-native, not exported-to-SVG [README]

Collaboration:

• Real-time multiplayer editing [2]
• Comments and feedback threads [homepage]
• Shared libraries and templates [README]
• Permissions and team management [homepage]

Extensibility:

• Plugin system — community-built plugins for accessibility checks, design linting, and more [4][README]
• Webhooks for integrating with your dev pipeline [README][homepage]
• REST API via access tokens [README][homepage]
• MCP server — Penpot now exposes an MCP server for AI tool integration, mentioned on the homepage alongside the open API [homepage]

Deployment:

• Docker and Docker Compose [3][5]
• Kubernetes via Helm chart (also SUSE Rancher, Red Hat OpenShift) [3]
• Managed hosting via Elestio partner platform [3][5]

---

Pricing: SaaS vs self-hosted math

Penpot Cloud (their SaaS):

• Free tier: unlimited files, real-time collaboration, full feature set — Penpot’s cloud is free with no file or seat limits disclosed as of this review [homepage]
• Enterprise: contact sales for SLA, SSO, priority support [homepage]

The notable thing is that Penpot’s cloud free tier is legitimately generous — they aren’t using the free plan as a funnel to a $15/seat/month paywall. Their monetization is enterprise contracts and self-hosted support, not seat-based SaaS pricing.

Self-hosted (Community Edition):

• Software license: $0 (MPL-2.0) [README]
• Infrastructure: $6–15/month VPS on Hetzner, Contabo, or DigitalOcean
• Minimum specs: dual-core CPU, 4GB RAM (8GB recommended), 10–50GB SSD [5]
• Your time to deploy and maintain

Figma for comparison:

• Free: limited to 3 Figma files and 3 FigJam files
• Professional: $15/editor/month (annual) — unlimited files, version history, team libraries
• Organization: $45/editor/month — design systems, SSO, advanced permissions
• Enterprise: $75/editor/month

Concrete math for a typical small product team:

A 3-designer startup on Figma Professional: 3 × $15 = $45/month, $540/year. Figma Organization: 3 × $45 = $135/month, $1,620/year. Penpot self-hosted: $8/month VPS, $96/year — and unlimited designers, because there’s no seat pricing.

Scale to 10 designers: Figma Professional = $1,800/year. Figma Organization = $5,400/year. Penpot self-hosted still = ~$96/year. The numbers stop being marginal pretty fast.

Caveat: these numbers assume your team has someone who can run a Docker deployment. If you need to hire someone to do it once, budget an extra $100–300 for the setup. That still breaks even in the first month versus Figma.

---

Deployment reality check

The XDA Developers article [5] walks through three deployment paths. The Penpot engineering blog [3] covers the same ground with more depth. Neither makes it sound easy for a non-technical founder — which is honest.

Three options ranked by difficulty:

1. Elestio (partner managed hosting) — described in [5] as “manages everything for you… skip the complicated configurations and have your server ready in no time.” Takes about 10 minutes. You’ll pay Elestio’s hosting fees on top of the platform (starts around $10–15/month). Best choice if you’ve never configured a reverse proxy.

2. Docker Compose — standard path for technical users. Requires a Linux VPS, Docker, a reverse proxy (Caddy or nginx), and a domain. The server architecture is client-heavy, meaning server specs can stay modest — processing happens in the browser, the server handles storage and coordination [3]. Realistic time for someone comfortable with Linux: 45–90 minutes.

3. Kubernetes via Helm — for teams deploying into existing k8s infrastructure or using Rancher/OpenShift. Not a weekend project if you haven’t done it before.

What can go sideways:

• One AlternativeTo reviewer [2] needed to dig through GitHub issues to get Podman working. Community support is active but not instant.
• Storage planning: Penpot’s team explicitly says to plan storage based on active designers, not total users — read-only stakeholders have minimal footprint, but a team of 10 active designers creating large files will grow the database faster than you expect [3].
• The server does NOT need to be powerful — but the client does. Penpot runs design rendering in the browser. They specifically recommend Chrome for best performance [3]. If your designers are on old laptops, the self-hosted instance won’t fix the lag.
• No Android or iOS app — mobile access requires a browser, and the mobile browser experience is limited [2].

For a non-technical founder: use Elestio or Penpot’s free cloud tier. For a technical founder or a team with a DevOps person: Docker Compose on a $8–12 Hetzner VPS is the right path.

---

Pros and Cons

Pros

• CSS-native design. Auto-layout actually uses Flexbox and Grid semantics, not a proprietary abstraction. Developer inspect output is real CSS you paste, not specs you translate [homepage][3][2].
• Open standards throughout. SVG, CSS, HTML, JSON — your files aren’t held hostage in a proprietary format. Export, migrate, parse programmatically [README][homepage].
• Native design tokens. First design tool with tokens built-in as a first-class feature, not a plugin or workaround [README][2].
• MPL-2.0 license. More permissive than GPL, allows embedding in commercial products. Source code you can actually read and modify [README].
• 44,888 GitHub stars — this is not a side project. Active development, regular releases (2.14 as of this review), large community [README][2].
• Free cloud tier that isn’t crippled. You can use Penpot’s SaaS for free with full features before committing to self-hosting [homepage].
• Plugin system with community-built extensions (accessibility checkers, design linters, custom workflows) [4][README].
• MCP server for AI tool integration [homepage].
• No seat-based pricing. Self-hosted means unlimited designers at fixed infrastructure cost.

Cons

• Real stability issues. The AlternativeTo negative review [2] is blunt and specific: image freezes, broken path editing, unreliable undo/redo, shapes jumping during transforms. These aren’t hypothetical concerns — they’re current user reports.
• Path editing is rough. Multiple reviewers flag this. For complex vector illustration work, you’ll feel the gap versus Figma or Illustrator [2].
• No mobile app. Reviewing designs on a phone requires a browser; creating designs on mobile is not a realistic workflow [2].
• Client-side performance depends on the browser. Complex files with many layers will lag on lower-end machines. This is architectural, not a bug to fix in an update [3].
• Setup is genuinely technical. Elestio abstracts most of it, but the “true” self-host path (Docker, domain, reverse proxy) isn’t beginner-friendly. The Podman path requires GitHub issue research [2][5].
• Smaller plugin ecosystem than Figma. The community plugin library exists and is growing [4], but Figma’s marketplace has years of head start and far more entries.
• Less mature for animation and micro-interactions. Penpot handles transitions between frames, but detailed animation workflows remain stronger in Figma or dedicated prototyping tools.

---

Who should use this / who shouldn’t

Use Penpot if:

• Your team is paying Figma $500–$5,000/year in seat licenses and the per-seat pricing keeps growing as the team does.
• You have a developer on the team who resents translating design specs — Penpot’s CSS output means they’re looking at the same language they write in.
• You need full data ownership: unreleased product designs, client data in designs, regulated industries where data residency matters.
• You’re building or maintaining a design system and want native design tokens without a plugin dependency.
• You’re comfortable with Docker or willing to use Elestio’s managed service.

Skip it (stay on Figma) if:

• Your team does heavy illustration or complex vector editing. Figma’s path tools are more polished, and Penpot’s stability reports on this workflow are concerning [2].
• You need a reliable iOS/Android design review experience for stakeholders on mobile.
• Your team is non-technical and nobody can manage a deployment. Penpot’s cloud is free, but you lose the self-hosting advantages.
• You’re dependent on a specific Figma plugin with no Penpot equivalent — check the plugin hub before switching.
• Performance predictability is critical: Figma’s cloud rendering is more consistent than browser-side rendering for complex files.

Consider Penpot’s free cloud before self-hosting if you haven’t used the tool before. The free tier is full-featured enough to validate whether it fits your workflow before you commit infrastructure hours.

---

Alternatives worth considering

• Figma — the incumbent. Best plugin ecosystem, most polished, most expensive at scale, cloud-only with proprietary file format. Industry standard for a reason.
• Sketch — macOS only, subscription-based ($10/editor/month), no native Linux or Windows. Still popular for solo designers on Mac.
• Adobe XD — Adobe has been de-emphasizing XD in favor of Figma-like features in other tools. Trajectory is not encouraging.
• Lunacy — free and offline-first design tool with Figma/Sketch import. Windows-focused but cross-platform. Not open source.
• Plasmic — more focused on design-to-code than design itself; better if you want to generate React components from designs.
• Inkscape — open-source vector illustration, not a UI design tool. Different category, frequently appears in the same conversations.
• Framer — strong for interactive prototyping and publishing; proprietary SaaS, pricing comparable to Figma.

For a non-technical founder escaping Figma seat costs, the real shortlist is Penpot vs staying on Figma’s free tier. Penpot’s free cloud removes the self-hosting variable entirely, making the decision about workflow fit rather than infrastructure tolerance.

---

Bottom line

Penpot is the most credible open-source challenger to Figma’s design-tool monopoly. It’s not trying to win on feature count — it’s trying to win on architectural correctness: designs that are natively CSS, files that aren’t locked in proprietary formats, and a developer inspect experience where the output is real code, not a spec to translate. For a product team paying $1,000–$5,000/year in Figma seats, the math for switching is obvious. The friction is also real: stability reports from actual users mention image freezes, path editing rough edges, and an undo/redo that occasionally does something surprising. These aren’t dealbreakers for all teams, but they matter for any team doing complex vector work or depending on airtight reliability. If your use case is primarily UI screen design with a developer who wants CSS-ready output, Penpot earns the switch. If you’re doing complex illustration, animation, or need every Figma plugin your team currently uses, give it another year.

If the self-hosting setup is the blocker, that’s exactly what unsubbed.co’s parent studio upready.dev deploys for clients. One-time fee, you own the infrastructure.

---

Sources

1. Product Hunt — Penpot Desktop Reviews (4.7/5, 3 reviews). https://www.producthunt.com/products/penpot-desktop/reviews
2. AlternativeTo — Penpot Reviews (4.7, 30 reviews, 243 likes). https://alternativeto.net/software/penpot/about/
3. Penpot Engineering Blog — “How to self-host Penpot: A technical implementation guide”. https://penpot.app/blog/how-to-self-host-penpot/
4. Penpot Hub — Plugins (Accessible Design Checklist example). https://penpot.app/penpothub/plugins/accessible-design-checklist
5. Nolen Jonker, XDA Developers — “How to build your own self-hosted Figma alternative with Penpot” (Feb 7, 2025). https://www.xda-developers.com/penpot-build-self-hosted-figma-alternative/

Primary sources:

• GitHub repository and README: https://github.com/penpot/penpot (44,888 stars, MPL-2.0 license)
• Official website: https://penpot.app
• Penpot documentation: https://help.penpot.app/user-guide/
• Figma pricing page: https://www.figma.com/pricing