Short answer: An overview of Penpot in Aamu.app for open-source design work, collaboration, project-connected workflows, and current API availability.
Aamu Designs opens your team’s Penpot workspace for UI mockups, wireframes, visual assets and prototypes.
The integration is intentionally simple: Aamu gives the team a Designs entrypoint and handles the Penpot team/profile authentication flow. The actual design work happens in Penpot.
What Penpot is
Penpot is a browser-based design tool built around open web standards such as SVG. It is often compared with tools like Figma, but it is open source and designed to work well for both designers and developers.
You can use Penpot for:
UI mockups,
wireframes,
prototypes,
design systems,
icons and visual assets,
layout exploration, and
developer-friendly design handoff.
How Aamu integrates it
In Aamu, open the Designs section. From there, Aamu provides a button to open the team's Penpot dashboard.
Behind the scenes, Aamu handles the connection between the Aamu company and the Penpot team. When a user opens Designs, Aamu can create or verify the Penpot profile, join the user to the company Penpot team, and set the authentication token so the user can continue into Penpot.
Your team can open the design workspace from Aamu’s navigation without a separate sign-in.
What belongs in Designs
Use Designs for visual work that benefits from a real design canvas:
new product screens,
landing page layouts,
customer-facing UI flows,
admin interface plans,
mobile app concepts,
brand or icon exploration, and
visual explanations that are easier to draw than describe.
Use Aamu Docs for written specifications and decisions. Use Tasks for implementation work. Use Penpot when the question is visual: layout, hierarchy, components, flow, affordances, and design detail.
Designs and the rest of Aamu
The best workflow is not to put every product decision into the design file. Keep each kind of work in the right place:
Docs hold product requirements, copy, decisions, and design rationale.
Tasks hold implementation and review work.
Meetings hold design reviews and customer calls.
Helpdesk shows customer feedback that can inspire design changes.
Penpot holds the visual exploration and prototype.
For developers
Penpot is useful for developers because it exposes design information in a web-friendly way. Developers can inspect structure, spacing, colors, typography, and assets without needing a proprietary desktop workflow.
For non-designers
You do not need a dedicated designer to get value from Designs. Penpot is also useful for rough diagrams, quick wireframes, and "this is what I mean" sketches.
What Aamu does not replace
Aamu does not try to reimplement all of Penpot inside the normal Aamu UI. The Designs section is the bridge into Penpot, while Penpot remains the design tool.
A practical workflow
Create a Doc for the product idea or feature brief.
Open Designs and create the related Penpot design.
Use Penpot for wireframes, screens, or prototypes.
Review the design in a Meeting or in project discussion.
Create Tasks for implementation and follow-up.
Update the Doc when decisions change.
API availability
Aamu does not currently expose a public Designs or Penpot CRUD API in its OpenAPI document. Team API keys therefore do not have a separate Designs or Penpot scope, and integrations cannot list or edit embedded Penpot files through Aamu’s API.
API-driven workflows can still coordinate the work around a design. Use the Tasks API for design review and implementation work, the Docs API for briefs and decisions, and the Files API for reference exports or assets that should be available in Aamu editor content. The Penpot file itself remains managed through the embedded Penpot experience and Penpot’s own capabilities.
If a direct Designs API is added later, it should appear in Aamu’s OpenAPI document at /.well-known/openapi.json before integrations depend on it.