Specific migrated to Blume in an afternoon.

Specific (YC F25) is the cloud platform built for coding agents. Your agent already writes your code; Specific lets it build the infrastructure to run it too. The agent defines the resources an app needs in a config file, spins up the whole stack locally with one command, tests against isolated production data in preview environments, and ships with a single command or through GitHub. When something breaks, it queries logs and metrics, finds the root cause, and ships the fix.

The team runs as much as it can on Specific: the landing page, the dashboard, the docs, and Hermes, its internal agent. That way it hits the same problems its customers do, first.

The challenge

Specific wanted two things from its docs: a beautiful site out of the box, and preview environments, so the team could check what its agents changed before shipping. The docs site isn't Specific's primary surface, since agents mostly read the docs that ship inside its CLI, so anything beyond that was a bonus.

And since the team runs everything it can on Specific, it wanted the docs running there too.

The move

When Blume came out, the choice was easy: open source and self-hostable meant Specific could run it on Specific. Iman handed the migration to Claude, and a couple of hours later, on July 14, 2026, the switch was made.

The whole deployment is one specific.hcl of about 30 lines: a build step, a service running the Node server Blume builds, a public endpoint with a health check, and one secret for the assistant. Every branch gets a preview environment out of the box, which covered the other half of what the team wanted.

The assistant, out of the box

Since agents mostly read the docs in Specific's CLI, what the team values in Blume isn't any single AI feature but how cheap they are to turn on. The MCP server at /mcp is on because it was one line of config.

The assistant is the one that paid off. Blume ships an assistant endpoint grounded in the docs, so any page can call it. After seeing Gustavo's "infinite FAQ" demo on X, Iman built one for specific.dev the same day: the FAQ on Specific's landing page ends with an empty row where a visitor types their own question and gets an answer from the docs, two to five sentences long, citing at most two pages.

It needed two small options Blume didn't have yet: CORS, for a caller on another origin, and a reasoning level. Iman sent two pull requests, and both were merged and released the same day. Iman calls that turnaround the real feature.

The results

On the first Blume deploy, on July 14, 2026, and before any tuning, Lighthouse performance scored 100, and every score was 96 or above.

The migration took a couple of hours of agent time, the docs run on a couple dollars of compute, and they're live at docs.specific.dev.

To move your own docs, read Migrate to Blume, and see what running Blume costs on your own host.