Penpot: Self-Hosted Design Infrastructure

Indie Hacker News2026-06-15go watch the original →

the gist

Penpot is an open-source, self-hostable design tool that treats design files as code, featuring native design tokens, an MCP server for AI agents, and a high-performance Rust/Wasm rendering engine.

Design as Code and Infrastructure

Penpot differentiates itself from cloud-native incumbents by treating design files as open-standard code rather than proprietary blobs. The platform utilizes native design tokens, ensuring that color and spacing values exist in a single source of truth. Because the tool is built on CSS grid and flexbox, frames behave like responsive code, allowing developers to pull SVG, CSS, and HTML directly from the canvas via inspect mode. This architecture allows teams to own their entire design stack, eliminating per-seat licensing and vendor lock-in.

AI Integration and Engineering

Penpot recently shipped an MCP (Model Context Protocol) server, which allows AI agents to read and edit design files as structured data rather than relying on visual screenshots. The platform is built using Clojure and ClojureScript, with a significant transition underway to replace the browser renderer with a new engine written in Rust and WebAssembly. This new engine utilizes tiling and viewport culling to maintain performance on massive files. The entire stack runs on a PostgreSQL database, enabling deployment via a single Docker command.

Recent Technical Updates

Version 2.15 introduced a fully supported MCP server integration for AI-driven design manipulation.
A new chunked upload API removed previous file size limitations for binary and media assets.
Security headers were added to Docker images to harden self-hosted instances.
An experimental WebGL renderer is available in beta for users requiring higher performance on complex files.

Trade-offs

Self-hosting requires the user to manage database maintenance, patching, and infrastructure uptime, tasks that are abstracted away by commercial SaaS alternatives. Additionally, the community-driven ecosystem is smaller than that of established players, resulting in fewer pre-made design libraries and templates. The new rendering engine remains in beta, meaning users may encounter stability or performance issues with exceptionally heavy files compared to polished commercial tools.