GitHub Repos intermediate 4 min read Jun 22, 2026 · Updated Jun 23, 2026
Public Preview Sign in free for the full digest →

Penpot: The Open-Source Figma Alternative You Can Self-Host

“Your Figma designs live on Adobe's servers. Penpot stores them as real SVG on yours — and 11 years in, it just replaced the rendering engine that was crashing production deploys.”

Penpot: The Open-Source Figma Alternative You Can Self-Host
1 Views
0 Likes
0 Bookmarks
Source · github.com

“"Simply navigating between pages (even on the example documents) was causing parts of the document to change in bizarre ways." — supermatt (https://news.ycombinator.com/item?id=46064757)”

You know that feeling when a designer sends you a Figma link, you open the inspect panel, and the CSS values look almost but not quite like what your codebase actually uses — requiring a manual translation pass before any code gets written? Or when your legal team flags that all your design IP lives on Adobe's servers under terms you did not write, and one pricing change or acquisition rewrites the equation? Most design tools lock files in proprietary formats that require export steps between design and code, and they store everything on servers you do not control. You cannot self-host Figma, you cannot read a .fig file without Figma, and the entire workflow depends on a vendor relationship you cannot renegotiate.

open-sourcedesign-toolsself-hostedfigma-alternativeclojureuxcollaboration

Think of Penpot as a Figma-shaped wrapper around an SVG document. When you draw a shape or set a color, Penpot writes those values as SVG markup and CSS properties in PostgreSQL — not as proprietary bytes. Your browser runs a ClojureScript and React frontend that sends edits to a Clojure backend running on the JVM; a separate exporter service handles PNG and PDF output. When you open the inspect panel, you see real CSS that maps directly to what a developer would write, because the design representation and the CSS representation are the same thing. To self-host: you run three Docker containers — the app, the exporter, and PostgreSQL — and you own every file. Version 2.16.0 added an opt-in WebGL rendering path that bypasses the DOM entirely for canvas operations, targeting the memory and stability issues that plagued the DOM-based renderer on complex documents.

01
SVG and CSS native file storage — your inspect panel outputs actual HTML and CSS, not a screenshot or an approximation, because the design representation and the code representation are the same underlying format; no separate handoff expor...
02
WebGL rendering engine (opt-in beta in 2.16.0) — replaces the DOM renderer that caused a reported 20GB RAM crash on a 64GB server with 5-6 pages; enables GPU-accelerated canvas operations for large or complex files
03
Design tokens with direct numeric field selection — a single source of truth for color, spacing, and typography values shared between your design file and your codebase; token values appear directly in the design tab without a separate map...
04
MCP server integration — connects your Penpot design files to AI agents and LLM workflows, enabling AI-native design-to-code pipelines from June 2026
05
Self-hosted on Docker, Kubernetes, Elestio, Rancher, OpenShift, or TrueNAS — your files never leave your infrastructure; free tier supports up to 8 users with no per-seat cloud fees beyond your own hosting cost
06
Plugin and webhook API — extend the workspace with custom scripts and connect Penpot to GitHub Actions, GitLab CI/CD, and Slack via webhooks, as covered in the official May 2026 integration guide
07
Real-time multiplayer editing — multiple designers and developers edit the same file simultaneously; free tier supports up to 8 team members with no paid upgrade required
Who it’s for

If you run a team in a regulated industry — healthcare, finance, defense — where sending design files to a cloud vendor is a compliance issue, Penpot is the only viable self-hosted design tool in this category. If you are a developer on a team still doing a manual design-to-code translation pass, Penpot's inspect mode outputs real CSS to copy directly. Not the right fit if you need Sketch file import (confirmed missing per HN community), a true offline desktop app, or a single-binary lightweight self-hosted install — the multi-service Docker stack requires meaningful ops overhead.

Worth exploring

The 10-year track record with 52,429 stars and active company backing from Kaleidos makes Penpot more credible than most open-source design tools, and the data sovereignty use case is genuine and underserved. The WebGL renderer shipping in 2.16.0 addresses the most-cited production failure mode, but it is still opt-in beta — you would be an early adopter of the new rendering path. If self-hosting is a hard requirement, this is the only serious option in the space; if it is merely a preference, the DOM stability issues documented in the community make it worth waiting for the WebGL renderer to become the default before committing.

Developer playbook
Tech stack, code snippet, sentiment, alternatives.
PM playbook
Adoption angles, user fit, positioning.
CEO playbook
Traction signals, ROI, build vs buy.
Deep-dive insight
Full long-form analysis, no fluff.
Easy mode
Core idea, fast — when you need the gist.
Pro mode
Technical nuance, edge cases, tradeoffs.
Read the full digest
Go beyond the preview

Deep-dive insight, Easy and Pro modes, plus action playbooks — the full breakdown is one tap away.

Underrated tools. Unfiltered takes.

Read the full digest in the Snaplyze app for deep-dive insight, Easy and Pro modes, and the playbooks you can actually use.

Install Snaplyze →