QuiverAI helped shape Blume from the start.
QuiverAI, the frontier AI lab for graphic design, wanted the freedom of a custom docs site without building one. It helped shape Blume from the start, then moved its docs over in less than a day.
- From Mintlify to production
- < 1 day
- Docs sites on Blume, public and internal
- 2
QuiverAI is a frontier AI lab building models for graphic design. Its flagship, Arrow, is a model for SVG generation: it turns a prompt into vector artwork, vectorizes images, and edits and animates existing SVGs. QuiverAI serves Arrow in the QuiverAI App and over the QuiverAI API, the main gateway for its business customers, used by companies like Paper, Flora, Vercel, and ComfyUI.
Its docs cover all of it: the App, the API platform, the API reference, and the MCP server and plugins that bring Arrow to Codex and Cursor.
How the docs started
QuiverAI's docs started on Mintlify, and Mintlify worked very well for the team. But as QuiverAI wanted more control over how its docs looked, it needed more room than Mintlify gave it.
The choice seemed to be Mintlify or a custom site. QuiverAI wanted both: the freedom of building its own, with the professional feel and the support for integrations that Mintlify had.
Building Blume together
Earlier in 2026, Nicklas Scharpff shared those concerns with Hayden Bleasel, just as Hayden was starting on Blume. Hayden brought QuiverAI into many of Blume's technical decisions, both to make sure Blume fit what QuiverAI needed and as a stand-in for other companies at a similar scale.
That meant QuiverAI's workflows and existing docs worked from day one. The migration was barely more than one CLI command, blume migrate mintlify, plus a prompt or two to refine the result, and the docs were in production in less than a day.
Docs that look like QuiverAI
What changed most was control over the design. Blume's design tokens carry QuiverAI's visual identity into every page, and component overrides let the team replace any built-in component with its own.
“The freedom to override any UI component, and how flexibly Blume adapts design tokens, made adapting our vision for the docs very straightforward.”
Nicklas ScharpffCo-founder, QuiverAIThe same flexibility took Blume past the public docs. It's now also the backbone of QuiverAI's internal design system documentation.
Ready for agents
QuiverAI's product reaches agents through its MCP server and plugins, and its docs reach them too, with no extra work. Every page has a Markdown version, the site publishes llms.txt and llms-full.txt, and an AI catalog lists its agent-facing resources.
The API reference builds from QuiverAI's OpenAPI spec with openapi(): every endpoint, from text to SVG to SVG animation, gets a page with its schemas, code samples, and a Try it panel.
The results
QuiverAI went from Mintlify to production in less than a day, and Blume now runs two of its docs sites: the public docs and the internal design system.
| What | Number |
|---|---|
| Public docs pages | 35 |
| API endpoint pages | 8, from an OpenAPI spec |
| Time to production | Less than a day |
| Docs sites on Blume | 2, public and internal |
For teams weighing the same move, Nicklas keeps it short.
“Just try it out. It's so simple, and you get to an MVP super fast.”
Nicklas ScharpffCo-founder, QuiverAIThe new docs are live at docs.quiver.ai. To make the same move, follow the Mintlify migration guide.
