Published 19 July 2026 · Source dated 1 January 2025
The Penpot-vs-Figma debate is really about who controls your design system's tokens and infrastructure. Self-hosting is now a real option, not just a theory.
Beyond the UI comparisons, the sharper argument for design-system leads is architecture: Penpot is built on open web standards (SVG/CSS/HTML), can be self-hosted, and hands you the tokens without vendor lock-in. For a junior, this matters less for day-to-day file-pushing and more for understanding why senior design-system owners debate tool choice — governance, long-term scalability, and who owns the source of truth when a company outgrows its subscription. It's not dethroning Figma-based systems (Figma still has the plugin depth and community), but 'open-source design system infra' is a real, growing conversation worth knowing the vocabulary for, even if you never touch a self-hosted instance yourself.
Coach
Read up on design tokens basics, then check whether a design system you admire documents publicly where its tokens live.
Design tokens are still the backbone of Material Design
Google's Material Design continues to push token-based theming as the default way to build flexible, on-brand components — it's the clearest real-world example of tokens done at scale. For juniors, understanding tokens beats memorising any one system's components.
material.io ·
Established
Material 3 Expressive: systems that flex, not just scale
Google's Material 3 Expressive update layers more personality — motion, colour, shape — onto Material's existing token structure without a rebuild. It's a solid case study in how mature design systems evolve.
design.google ·
Established
Penpot puts native design tokens in its free tier
Penpot now bundles native design tokens and shared component libraries into its open-source platform at no cost — a feature set that's often gated behind paid tiers elsewhere. Design tokens themselves are a well-established practice, just newly accessible without a licence fee.