About
Documentation that tells the truth about your code
Inkwell Forge was built on a simple observation: the documentation that matters most is almost always the documentation that doesn't exist yet.
The problem
Documentation is a solved problem that nobody solves
Every team knows documentation matters. Security auditors need it. New hires need it. M&A due diligence teams need it. Training departments need it. And yet, for the vast majority of codebases, it either doesn't exist or it was written once, three years ago, and is now quietly misleading everyone who reads it.
Writing documentation by hand is slow, expensive, and immediately starts falling behind the code. Most teams rationalize skipping it until the cost becomes impossible to ignore — a failed audit, a botched handoff, a new engineer who takes six months to become productive.
Our mission
Professional documentation for every team
Inkwell Forge exists to make professional-grade documentation accessible to engineering teams of every size — not just the ones who can afford a dedicated technical writing department.
We connect to your repository, analyze your code, and generate the documentation your team actually needs: training manuals, security audits, API references, onboarding guides, compliance checklists, and 30 more types — all built from what your code actually does, not what someone remembered to write down.
Our approach
Standards-based, transparent, code-driven
Generic automated documentation is a liability. When a document looks authoritative but contains fabricated details, it's worse than no documentation at all. We built Inkwell Forge with that risk at the center of every design decision.
Every one of our 36 deliverable types is validated against named professional standards — IEEE 829 for test plans, OWASP ASVS for security audits, ISO/IEC 42010 for architecture documents, and so on. Our analysis engine is explicitly constrained in what it can and cannot assert, what it must mark as inferred, and what it must flag as unknown.
The result is documentation that is honest about its own boundaries — more useful to the people who actually have to act on it.
What we build
36 deliverable types across 8 lifecycle categories
From end-user training manuals to security audit reports to tech debt burndown plans, Inkwell Forge covers the full lifecycle of engineering documentation. Connect your GitHub or GitLab repository, select the screens you want documented, choose your deliverables, and receive professional output in Word, PDF, HTML, Markdown, or Excel — ready to hand to a client, auditor, or new hire.
Principles
How we think about documentation quality
Accuracy over completeness
An incomplete document that is accurate is more valuable than a complete document that contains fiction. We never fabricate. Gaps are labeled as gaps.
Standards as a foundation
Every deliverable type is built against named professional standards. Not because auditors require it, but because standards encode decades of hard-won expertise about what good documentation actually contains.
Code is the source of truth
We read your repository, not your wiki. The code tells us what the system actually does. Documentation that drifts from the code is noise; documentation derived from the code stays current.
Transparency at every layer
Every document states what was analyzed, what was inferred, and what couldn't be determined from the available code. Readers always know where the document's authority ends.
Price predictability
You see the exact cost before you generate — calculated from your actual file sizes, applied to your plan's multiplier. No metered surprises after the fact.
Output formats that fit your workflow
Not everyone lives in Markdown. Engineers want .md files in their repos. Legal wants PDFs. Clients want Word documents they can edit. We produce all of them from a single analysis pass.
Get started
See what your codebase has to say
Sign up free and generate your first screen documentation and deliverable — no credit card required. Takes less than five minutes.