Generated, not hand-written
Hand-written docs decay the moment they're shipped. Generated docs decay too — but they also regenerate. The right architecture isn't "no docs to maintain"; it's "the maintenance is automatic."
Quill started as a tool a small team built for itself — engineers shipping fast and watching their help center drift further from their product every sprint. Now it's a system anyone can point at their codebase. The docs catch up automatically. The humans stay in charge of what publishes.
Hand-written docs decay the moment they're shipped. Generated docs decay too — but they also regenerate. The right architecture isn't "no docs to maintain"; it's "the maintenance is automatic."
We don't believe AI should publish without a human green light. Every Quill article moves through an operator review queue. The AI proposes; you publish. That's not a UX compromise — it's the only way docs stay trustworthy.
When the doc and the code disagree, the code wins. Quill is built around that posture. We read your routes, your types, your tests. We don't invent product behavior — we describe it.
Help center, dev reference, and changelog should come from the same understanding of the product. Quill's pipeline produces all three from one read of your repo, then keeps them in sync as you push.
Every commercial-software docs site was good once because someone who cared about docs sat down and made it good. We're building Quill so that someone can be your AI cofounder.
Quill is a small team currently in early access. We're being deliberate about who we bring on — every customer gets a real human paired with them for the first two weeks. We expect to stay small for a while.
Built by an engineer who'd watched the same docs decay cycle play out at three different companies. The first prototype ran against the team's own product before any external customer ever saw it.
Quill writes Quill's own docs. The help center, dev docs, and changelog you see at quilldocs.ai are themselves produced by the pipeline. We're our own canary.
Pages marked [ preview ] are positioning hedges for features in active design. We'd rather flag the gap than fake the feature.