Automatize
Products · 05 · Authoring & Publishing
← All products

GitWriter

Write once. Version everything. Publish everywhere.

Every book, manual or documentation set becomes a real Git repository — with branches, commits, diffs, blame, merges and conflict resolution — driven entirely from a browser by people who will never install a Git client. It is then published to PDF, EPUB, Word, HTML and a searchable static site from the same source.

Request a demo →Download brochure (PDF, EN) ↓
13Book types
7Git hosting targets
264REST endpoints
2708Automated tests
The problem

Docs-as-code works beautifully — for the people who can already use Git.

Engineering wants version control, branches and review. The technical writer, the compliance officer and the trainer want to open a page and type. So the documentation splits: the parts under version control that only engineers touch, and the parts in a wiki that nobody can diff, review or roll back. Both halves go stale, in different ways.

01
Two systems
The repository and the wiki disagree about what is current.
02
No review
Wiki pages change with no branch, no approval and no way to see what moved.
03
Publishing by hand
The customer PDF is exported, reformatted and emailed by one person.
04
Content leaves
Hosted authoring puts unreleased specifications and policies outside your control.
The solution

Give everyone the browser. Give the content real Git underneath.

01
Genuine version control
A real repository per book, with branches, annotated tags, merges, three-way conflict resolution, per-file history and blame — driven entirely from the interface.
02
Review before publish
Branch, comment on a line, suggest a replacement, request changes, approve, merge — the workflow engineering trusts, made usable by non-engineers.
03
On your own hardware
Eight of the fifteen supported AI model runtimes are local, and grammar checking runs inside the application — nothing has to leave the network.

Capabilities

01Write & version
  • Real, non-bare Git repository per book, scaffolded with a table of contents, sections and an asset folder.
  • Commit, revert a commit, paged history, per-file history and blame.
  • Branches typed as main, draft, review or archive, with protection and an undeletable default.
  • Annotated tags; merges with a dry-run check before you commit to one.
  • Book-wide find and replace with case, whole-word and regex options — replace-all lands as a commit.
  • Diff between any two references or a single commit, with formatted hunks and rename detection.
  • Rich, source and split editor modes with a draggable divider and debounced live preview.
02Collaboration & review
  • Live co-editing with per-user cursors and a presence bar showing who is in the book.
  • Comments anchored to the quoted text, not just the line number, so highlights survive edits above them.
  • Suggested edits — propose a replacement; accepting writes and commits it.
  • Review requests from branch to branch with approvals, change requests and threaded comments.
  • In-browser conflict resolution — theirs, ours and an editable merged pane per file, with the option to abort.
  • Mentions with autocomplete, and in-app notifications for mentions, comments, assignments and jobs.
  • Readability scoring, daily word goals, a streak counter and a thirty-day activity sparkline.
03Import & migrate
  • Import from Confluence, Notion, GitBook, Markdown, Word or rich text, with the format detected automatically.
  • GitBook imports follow the existing table of contents in order, then append anything unreferenced.
  • Existing pages are never overwritten — slugs deduplicate instead.
  • Unsupported files are skipped with a warning, rather than failing the whole import.
  • Bounded and safe: page and file ceilings, archive-entry limits, and traversal defences on every path.
04AI assistance
  • Fifteen model providers, eight of them local, so drafting, translation, search and review need no external call.
  • An agentic writer plans, drafts, reviews, refines and finalises on its own branch, committing each page as it goes.
  • Six path-validated tools for the agent: list, read, edit, create, update content, finish.
  • Selection actions streamed token by token: check, rewrite, improve with an instruction, shorten, lengthen.
  • Book-level AI work: cross-chapter continuity checking, style linting against your own guide, summaries and glossaries.
  • Eight insight tools including pacing, fact-check, link suggestion, alt text, tone and a character bible.
  • Semantic search with no vector database — embeddings stored inline, degrading to keyword scoring when unavailable.
05Publishing & platform
  • Five output formats from one source: PDF, EPUB, Word, HTML and a static site.
  • Export presets inherited across three levels: page size, margins, base size, fonts, contents depth and numbering.
  • A cover designer with image, colour, subtitle and author overrides, plus front and back matter.
  • The static site includes sidebar contents, a page outline, previous/next navigation, a light/dark toggle and full-text search.
  • White-label branding with field-level inheritance — name, logo, favicon, colours and typeface, shown to readers too.
  • Reader analytics: views, sessions, searches, helpfulness, per-page figures and drop-off pages.
  • Content health checks for broken internal links and orphan pages, recomputed on every build.
■Java 17 on Spring Boot 4, with an embedded Git engine — no Git binary or external service.
■PostgreSQL database, 30 tables, schema installed by the setup wizard.
■264 REST endpoints across 39 controllers; server-rendered vanilla ES6 front end, no build step.
■2,708 automated tests — roughly the size of the production codebase itself.
■Single sign-on via Google and Microsoft; bcrypt password hashing; refresh-token rotation.
■Self-hosted, single-node deployment; not yet available: outbound e-mail, MFA, SAML/directory login, encryption at rest for provider credentials.

What it does

  • 01Real Git — branches, merges, diffs and blame — used entirely from the browser.
  • 02Fifteen AI model providers, eight local, so drafting and review never have to leave your network.
  • 03One licence, unlimited authors — publish from one source to PDF, EPUB, Word, HTML and a static site.

At a glance

For whomEngineering docs · Compliance · Training · Agencies · Publishers
LicenceLicensed per installation, not per author, so one licence covers unlimited authors. The annual fee scales with your own turnover — marginal like income tax, with a €900 minimum and yearly increases capped at 25% — while hosting, AI usage and services are billed separately.

GitWriter in your organisation?

Start the conversation →