Evergreen Documentation

Your docs are outdated. Right now.

InkLoom monitors your codebase and automatically updates documentation with every commit. Set up once, never fall behind again.

Documentation debt is real

Every team faces the same problem — docs fall behind code the moment you ship.

Documentation lags behind code

Every merge creates drift. Within weeks, your docs mislead users and erode developer trust.

Manual updates don't scale

As your codebase grows, no one has time to audit docs for accuracy after every release.

Stale docs erode trust

Developers stop reading your docs when they learn they can't rely on them. Support tickets spike.

How It Works

Five steps to evergreen docs

Set it up once and your documentation stays accurate forever — automatically.

Push code
Commit to main or open a PR
CI scans changes
GitHub Action detects what changed
AI generates updates
InkLoom creates or updates affected pages
Review in PR
Preview doc changes alongside your code review
Auto deploy
Merge the PR, docs go live on the edge
.github/workflows/inkloom.yml
name: Update Documentation
on: push
jobs:
docs:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: inkloom/docs-action@v1
with:
api-key: ${{ secrets.INKLOOM_API_KEY }}
project-id: ${{ secrets.INKLOOM_PROJECT_ID }}

Why InkLoom is different

Not another docs tool — a docs engine that's native to your development workflow.

Git-native, not a separate workflow

Documentation updates are proposed as pull requests. Review them with the same tools and processes you already use for code.

AI that reads your code, not just your prompts

InkLoom indexes your actual codebase to generate accurate, contextual documentation — not generic content from a prompt.

One-click rollback

Full version history for every page. If an automated update isn't right, restore the previous version instantly.

Stop chasing your docs. Let them chase your code.

Set up once, stay in sync forever. Free to start, no credit card required.

Frequently asked questions

How does the automation actually work?

InkLoom provides a GitHub Action that runs in your CI pipeline. On every push or pull request, it analyzes code changes, identifies which documentation pages are affected, and uses AI to generate or update those pages. The updates are proposed as a pull request so you can review them before they go live.

Are updates auto-published or do they go through review?

By default, all documentation updates are proposed as pull requests. Your team reviews the changes alongside the code review, and docs only go live when the PR is merged. You can optionally configure auto-merge for trusted updates.

Is GitHub required?

GitHub is the primary integration today, with full support for GitHub Actions, PR-based workflows, and repository syncing. Support for GitLab and Bitbucket is planned.

Can I self-host InkLoom?

Yes. InkLoom is open source under the Apache 2.0 license. You can self-host the entire platform on your own infrastructure. See docs.inkloom.io for the self-hosting guide.