Engineering docs,
connected to code.
Meldoc is a docs as code platform for engineering teams. Keep technical knowledge connected to your code, spot outdated documentation during code review, and share project context with developers and AI tools.
Start free. Upgrade to Pro for unlimited team members, with no per-seat pricing.
$ curl -fsSL https://meldoc.io/install.sh | bash How docs as code works.
-
browser · .meldoc.md in repoWrite in Meldoc or alongside your code.
Create and edit documentation in the browser, or keep
.meldoc.mdfiles in your repository. Both workflows stay connected. -
GitHub · GitLab · sync both waysConnect Git once.
The GitHub App or the GitLab connection keeps the repository and Meldoc in step, both ways. No CI job to maintain. Bitbucket: the CLI.
-
portal for people · MCP for AIEveryone reads. AI reads too.
Enable documentation checks in pull requests. Your team reads through the web portal, while AI tools access the same knowledge through MCP.
Code review is where documentation should catch up.
When a pull request changes how your system works, the documentation needs attention too. Meldoc brings that review into the same workflow, so your team can spot outdated information before the change is merged.
Meldoc sync: <project>Sync checkWill the sync go through cleanly?
Meldoc review: <project>Documentation reviewDid this change make a sentence in the docs untrue?
Off by default, per project. Never blocks a merge.
Why docs should pass code review →Try it — drag the blue number. The docs get checked.
Session rotation
Sessions rotate every 24 hours, with a
24-hour grace period. The rotation hook lives in auth/service.go.
updated · just now
docs/auth/sessions.meldoc.md:14“Sessions rotate every 24 hours, with a 24-hour grace period.”
The meaning check runs on your own AI key (Pro). Without one, the review still reports dead references.
Meldoc stores documentation, never code. The review reads a pull request’s changes only on projects where you turn it on.
one source · every team
Engineers write it. Every team builds on it.
Engineering docs live in Git, next to the code, and get checked in pull requests. Product, support and QA keep their own projects on top — specs, help articles, test plans — and link to the engineering page instead of retelling it. When the engineering page is updated, those links lead to the latest version. Linked specs, articles and test plans may still need their own updates.
product
Specs start from how the system works today. A brief links the current API and UI pages instead of copying them.
support
Help articles and reply snippets link to the engineering documentation, so support can check the behaviour behind an answer.
qa
Test scenarios sit beside the intent and the implementation they verify, one link away from both.
ai agents
Each project tells assistants what it owns. Through MCP, an answer comes from the page that owns the fact.
Documentation platform features.
Free covers the core for one person. Pro adds unlimited members, your own AI key and webhooks.
- MCP server
- Your AI tools read and edit your docs directly, on every plan. Claude Code, Cursor and Claude Desktop connect once and stay in context.
- Git sync, both ways
- Changes in the repository land in Meldoc. Edits made in the browser go back as a pull request.
- Documentation checks in pull requests
- One predicts what the sync will do. The other quotes the sentence your code change made untrue, judged by your own AI key (Pro); without one, it still reports dead references.
- Knowledge graph
- Every link and backlink between pages, so you see what else a change touches before you make it.
- Audit suite
- Finds duplicate pages, broken links, old names still in use, and searches that found nothing.
- Templates and custom fields
- Give a page a type and it gets the fields that type needs. Filter and sort by any of them.
- History and contributors
- Every version with a diff and a restore button, kept for 365 days on Pro. Every author credited, straight from Git.
Plus the basics: an audit log, sign-in with an email code, GitHub or Bitbucket, Markdown export, three-way merge, a full CLI, and renames that keep old links working. On Pro: roles per project and Teams, webhooks, and public publishing with llms.txt.
Pricing without per-seat fees.
| Feature | Free €0 Solo, internal docs Start for free | Pro €79/mo per workspace €66/mo billed yearly For engineering teams Start with Pro |
|---|---|---|
| Members | 1 | Unlimited |
| Projects | 3 private | Unlimited |
| Documents | 200 | Unlimited |
| Version history | Not included | 365 days |
| CLI + CI/CD | Included | Included |
| Documentation review | Dead references | + meaning check, on your key |
| AI writing | Not included | 200/day |
| Bring your own AI key | Not included | Included |
| MCP server | Read and write | Read and write |
| Webhooks | Not included | Included |
See detailed plans → Need something else? Contact us
Docs as code FAQ.
What is MCP?
Do I need Git?
.meldoc.md files, the GitHub App or GitLab connection, the CLI — is there for teams that want docs next to code. Both paths lead to the same docs.Do I need a CI job?
Can docs still go out of date?
Whose AI key is used?
SAML SSO?
*.meldoc.md never blocks a merge product · support · qa · ai Start free. Upgrade when you outgrow the limits.
$ curl -fsSL https://meldoc.io/install.sh | bash