Git-native revisions
Every save is a commit. Browse, diff, and restore any past version, no separate revision database to maintain.
Self-hosted · Git-native
No database.
No database.
Just your docs, as Markdown in Git.
DocuCommit stores every page as a plain Markdown file in your own Git repo. No database to run, no vendor to trust, no lock-in — and every page is already readable by any LLM or agent.
14 days free. No credit card.
- Java 25 · Spring Boot
- flexmark · JGit · Lucene
- No database · self-hosted
auth.md on branch main · 3 revisions
---
title: Authentication
tags: [security, jwt]
updated: 2026-05-31
---
# How tokens are signed
We use **HS256** with a rotating secret pulled from
[Vault](/infra/vault). See `AuthService.java` for the
signing flow.
```java
String token = Jwts.builder()
.subject(user.id())
.signWith(secret)
.compact();
``` See it in motion · the 20-second tour From Markdown to merged,
From Markdown to merged,
in one unbroken flow.
The trouble with most docs platforms Your knowledge
Your knowledge
shouldn't be hostage
to a vendor.
-
Lock-in by design
SaaS tools store your content in a proprietary database. Switching tools means exporting to a lossy JSON dump and starting over.
-
Revision history that vanishes
Most plans cap history at 30 days. Older changes are gone, and the change graph is hidden inside a black-box service.
-
Exports that don't survive
"Export to Markdown" usually means a brittle dump full of platform-specific blocks that won't render anywhere else.
01 · Architecture
Two surfaces, one Git repo.
02 · Features
What you get out of the box.
Comments & @mentions
Discuss any block of text. Comments live in a sidecar JSON so your Markdown stays clean and reviewable.
Diagrams: draw.io + Mermaid
Bundled draw.io for pixel-precise boards, plus fenced Mermaid for diagrams that diff cleanly in Git. Both render on the editor and the server.
Conflict-free collaboration
Get updates and Publish without a terminal. When two people edit the same page, a guided three-pane merge keeps the best of both.
03 · Comparison
How it stacks up.
| DocuCommit | The traditional docs stack | |
|---|---|---|
| Content storage | Markdown files in your own Git repo | Locked in a proprietary database |
| Data ownership | Your repo, your infrastructure — nothing leaves your perimeter | Held in the vendor's cloud or database |
| Revision history | Full native Git history, in your repo, forever | Retention-capped and trapped inside the service |
| Leaving / export | Nothing to export — the files were always yours | Lossy export; links and formatting break on the way out |
| AI / agent-readable | Every page is plain Markdown, readable by any LLM or agent | Content must be pulled through an API or export first |
| Self-hosting | Desktop editor app + a read-only Docker server on your infra | Usually cloud-only, or a heavy database stack to run |
| Diagrams | Bundled draw.io + fenced Mermaid, fully offline | Paid add-ons or limited built-ins |
| Content telemetry | None — a license heartbeat that reads no content | Cloud usage analytics over your content |
"The traditional docs stack" means the usual database-backed wikis and SaaS documentation tools as a category — not any single product.
Free for 14 days
Own your docs from day one.
Start a 14-day trial, no card required. Pick Pro, Team, or Enterprise when you're ready. Everything you write stays plain Markdown in Git, on your own infrastructure, yours to keep whether you stay or not.