Kittl
Kittl hands the design decisions to an agent, then opens the editor to outside tools and licensed type.
A side-by-side editorial comparison of Aseprite and Penpot — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Aseprite | Penpot |
|---|---|---|
| Sector | Design | Design |
| Velocity score | 5.0 | 2.5 |
| Sparks · 30d | 0 | 0 |
| Top themes | pixel art, lua api, extensibility, maintenance train | open source, design tools, figma alternative, self-hosting |
| Last editorial update | 21h ago | 1mo ago |
| Website | Visit → | — |
Steady 1.3 maintenance, with the Lua API quietly becoming Aseprite's extension point.
Aseprite is deep into a long 1.3.x maintenance line: v1.3.18 landed in July after three betas stretching back to February, followed within the hour by a 1.3.18.1 crash-fix patch and, two weeks later, a one-line 1.3.18.2. The substantive work in 1.3.18 splits three ways — performance (undo/redo now keeps doc::Objects in memory), discoverability (Preferences search, configurable tooltip delay, clearer layer groups in the timeline), and Lua API growth (custom file formats for load and save, eyedropper in app.useTool). By volume, bug fixes dominate: tilemap selection, zoom distortion, crash paths.
Penpot chases Figma parity while betting on self-host and AI-agent access
Penpot is the open-source, deployment-agnostic design and prototyping tool, and its releases run on two tracks: steady Figma feature parity (background blur, design tokens, export formats) and infrastructure that sets it apart — self-hosting, an MCP server for AI assistants, and a WebGL rendering path. Development is fast and community-heavy, with each numbered release carrying dozens of enhancements and fixes.
Aseprite is deep into a long 1.3.x maintenance line: v1.3.18 landed in July after three betas stretching back to February, followed within the hour by a 1.3.18.1 crash-fix patch and, two weeks later, a one-line 1.3.18.2. The substantive work in 1.3.18 splits three ways — performance (undo/redo now keeps doc::Objects in memory), discoverability (Preferences search, configurable tooltip delay, clearer layer groups in the timeline), and Lua API growth (custom file formats for load and save, eyedropper in app.useTool). By volume, bug fixes dominate: tilemap selection, zoom distortion, crash paths.
The cadence is beta → final → patch, with identical fixes backported across the 1.3.17.x and 1.3.18.x branches — several entries here are branch twins carrying the same two or three fixes. The one directional thread is extensibility: the Lua API version moved 39 → 40 and now lets third-party code register sprite load/save formats the core used to own exclusively. Separately, "refactors needed for new layer types" appears across two releases as internal groundwork with no user-visible effect yet.
Expect the 1.3.18.x patch train to keep absorbing crash reports at this pace, with the next feature release cashing in the new-layer-type refactors that have been landing quietly.
Penpot is the open-source, deployment-agnostic design and prototyping tool, and its releases run on two tracks: steady Figma feature parity (background blur, design tokens, export formats) and infrastructure that sets it apart — self-hosting, an MCP server for AI assistants, and a WebGL rendering path. Development is fast and community-heavy, with each numbered release carrying dozens of enhancements and fixes.
Two bets run in parallel. One is closing the remaining gap with Figma feature-by-feature; the other leans into what a hosted competitor can't easily copy — private or on-prem deployment and agent-readable design files via MCP. The token-system depth and WebGL work suggest Penpot wants to be both a credible daily design tool and the default for teams that need control over where their design data lives.
Expect the parity grind to continue release-over-release, with the WebGL renderer maturing out of beta and the MCP and self-host story pushed harder as the differentiator against hosted rivals.
Other Design products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Aseprite or Penpot.
Kittl hands the design decisions to an agent, then opens the editor to outside tools and licensed type.
shadcn/ui is turning a component registry into infrastructure for AI app UIs.
Two release trains, zero new features — Astra has been in pure maintenance mode since spring.
The editor now prints to a CVS counter, and that is the second business bolted on this summer.
Webflow is building for the answer engines, not just the search results page.
The 10.6 alphas are an Angular tooling rebuild wearing a version number.
See all Aseprite alternatives → · See all Penpot alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Aseprite is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Aseprite is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Design products to evaluate alongside.
Top Aseprite alternatives in Design are ranked by recent ship velocity. Browse the "Aseprite alternatives" section above for the current picks, or visit /alternatives/aseprite for the full list with editorial commentary on each.
Top Penpot alternatives in Design are ranked by recent ship velocity. Browse the "Penpot alternatives" section above for the current picks, or visit /alternatives/penpot for the full list with editorial commentary on each.