The random histories never changed the structure of the shapes a main holds. The shape structure programs add a structure edit on a shape a main holds, and its next sibling: group, mask, unmask, combine into a bool of each type, or convert to a path, through the changes of app.common.logic.groups and app.common.logic.bool the workspace events commit, and the frontend's path conversion without the WASM renderer. Ungrouping, and grouping that takes every child out of a group, stay out until copies follow the removal of a shape their main holds. The oracle and the model learn the shapes these edits make: - bools and paths keep their bounds in their selrect only, which the geometry checks read when a shape has no box of its own; - path segments compare within the geometry tolerance, and the design snapshot leaves out a bool's segments, which it computes from its children in an order that depends on how it was computed; - children of groups and bools measure from, and anchor authored places to, the board around them, as a group's bounds come from its children; - differing flip flags count only when the ordered corners differ too; - undo and redo compare geometry within 1e-10, and bool and path geometry within 1e-4, as a group computes its geometry again from its children and a path stores its segments in single precision. Transforms of copy shapes inside groups and bools stay out until the oracle places them. Test: random-shape-structure-compositions. Focused only; the full common suite runs at the end of this series. Harness only; the benchmark is not run. Also in this commit: - Count differing flip flags unless they decompose the same corners. The shape structure gates ignored differing flip flags whenever the ordered corners matched, so a shape whose flags disagree with its own transform passed as well (both-flags-and-a-half-turn-equal-neither). Flags count now unless the corners match and the shape's flags and rotation decompose its transform, so they store the same transform otherwise. - Resize the groups around a shape the harness transforms. The frontend's transform resizes the groups around the shapes it changes (reg-objects, pcb/resize-parents); the harness transform did not, so a main's group kept the bounds of a child it moved while sync gave its copies' groups bounds from their children, and the oracle found them apart. The harness transform resizes the parents too. - Reflow layouts only after the structure edits whose events do. The structure node reflowed the layouts of the parents after every edit, but the workspace events update layouts only after grouping, masking and ungrouping; unmasking, creating a bool and converting to a path do not. The extra reflow left an undo that did not give back the place of the children of a mask unmasked in a flex main. The node reflows as the events do. - Compare the corners of a bool in any order. A bool computes its points from its segments, so their order follows the path, not the transform: a flipped main gave its copies' bools the same corners in another order, which the geometry check and the design snapshot read as another place. Both compare a bool's corners in a sorted order. - Check only the first corner of a place whose size a layout gives. The model checks an authored place by the corners of the shape placed in its parent, but leaves out the dimensions a layout gives it. A moved copy whose main came to hug its grid took the hugged width from its layout and kept its first corner, yet the corner check compared all four corners with the authored width. With a size the layout gives, only the first corner is checked, which a layout resize keeps. - Sort the corners of a bool by their rounded position. Sorting a bool's corners by their raw coordinates swapped two corners whose x differed only by noise, so two equal bools compared apart. The corners sort by position rounded to the hundredth of a pixel. - The harness changes that check the next commit, "Keep the layout's place and sizes out of a detach's kept geometry". AI-assisted-by: claude-opus-5-5
Website • User Guide • Learning Center • Community
Youtube • Peertube • Linkedin • Instagram • Mastodon • Bluesky • X
Penpot is the open-source design platform for teams that build digital products at scale.
Penpot’s key strength lies in giving you full ownership of your design infrastructure. Built on open source and designed for self-hosting, it puts teams in complete control of their design environment supporting strict compliance and governance requirements. Whether used in the browser or deployed on your own servers, Penpot works with open standards like SVG, CSS, HTML, and JSON.
Real-time collaboration strengthens this foundation, helping teams scale and bring design closer to the product through top-tier capabilities. Additionally, developers feel at home using Penpot, because design is expressed as code, enabling a direct translation and shipping products faster.
Best-in-class native Design Tokens provide a single source of truth between design and development. They ensure consistency, improve collaboration, and make it easier to manage complex design systems.
The MCP server takes it further by enabling multi-directional workflows between design and code. A powerful open API and plugin system makes the workspace programmable, enabling automation, AI-driven workflows, and integrations with the tools and systems you already use.
With CSS Grid and Flex Layout, teams can design responsive interfaces that behave like real code from the start.
Combined, these features turn Penpot into a full-stack design platform for building scalable design systems and fully integrated product development processes.
If your organization is scaling and needs extra support, we’re here to help. Talk to us
Table of contents
Why Penpot
Penpot connects design, code, and AI workflows through a code-based approach, making designs readable by developers and AI via the MCP server. This approach helps teams ship what’s actually designed and manage design systems at scale with powerful design tokens. As a self-hosted, open-source and real-time collaboration platform, Penpot offers full flexibility, security, and ownership without vendor lock-in. Learn more about why Penpot is the platform for your team.
Plugin system
Penpot plugins let you expand the platform's capabilities, give you the flexibility to integrate it with other apps, and design custom solutions.
Designed for developers
Penpot was built to serve both designers and developers and create a fluid design-code process. You have the choice to enjoy real-time collaboration or play "solo".
Inspect mode
Work with ready-to-use code and make your workflow easy and fast. The inspect tab gives instant access to SVG, CSS and HTML code.
Integrations
Penpot offers integration into the development toolchain, thanks to its support for webhooks and an API accessible through access tokens.
Building Design Systems: design tokens, components and variants
Penpot brings design systems to code-minded teams: a single source of truth with native Design Tokens, Components, and Variants for scalable, reusable, and consistent UI across projects and platforms.
Getting started
Penpot is the only design & prototype platform that is deployment agnostic. You can use it in our SAAS or deploy it anywhere.
Learn how to install it with Docker, Kubernetes, Elestio or other options on our website.
Penpot Enterprise
Penpot Enterprise is our paid plan for organizations that need to scale their design work across multiple teams with advanced governance, security, and administration. Manage teams and access from a centralized Admin Console, configure advanced permissions, and connect your identity provider through SSO. Available for cloud and self-hosted environments, it combines enterprise controls with Penpot’s open-source foundation and open standards.
Community
We love the Open Source software community. Contributing is our passion and if it’s yours too, participate and improve Penpot. All your designs, code and ideas are welcome!
Want to go a step further? Become a Penpot Ambassador and help grow the Penpot community in your region while contributing to a global, open design ecosystem.
If you need help or have any questions; if you’d like to share your experience using Penpot or get inspired; if you’d rather meet our community of developers and designers, join our Community!
Categories include:
- Ask the Community
- Troubleshooting
- Help us Improve Penpot
- Events and Announcements
- Penpot in your language
- Education
Code of Conduct
Anyone who contributes to Penpot, whether through code, in the community, or at an event, must adhere to the code of conduct and foster a positive and safe environment.
Contributing
Any contribution will make a difference to improve Penpot. How can you get involved?
Choose your way:
- Create and share Libraries & Templates that will be helpful for the community.
- Invite your team to join.
- Give this repo a star and follow us on Social Media: Mastodon, Youtube, Instagram, Linkedin, Peertube, X and BlueSky.
- Participate in the Community space by asking and answering questions; reacting to others’ articles; opening your own conversations and following along on decisions affecting the project.
- Report bugs with our easy guide for bugs hunting or GitHub issues.
- Become a translator.
- Give feedback: Email us.
- Contribute to Penpot's code: Watch this video by Alejandro Alonso, CIO and developer at Penpot, where he gives us a hands-on demo of how to use Penpot’s repository and make changes in both front and back end.
To find (almost) everything you need to know on how to contribute to Penpot, refer to the contributing guide.
Resources
You can ask and answer questions, have open-ended conversations, and follow along on decisions affecting the project.
✏️ Tutorials
🏘️ Architecture
🧑🏫 UI Design Course
License
This Source Code Form is subject to the terms of the Mozilla Public
License, v. 2.0. If a copy of the MPL was not distributed with this
file, You can obtain one at http://mozilla.org/MPL/2.0/.
Copyright (c) KALEIDOS SUBSIDIARY SL
Penpot is a Kaleidos’ open source project