Why Doxxy

Documentation should be a build artifact, not a chore.

Your docs already live in the repo. Doxxy treats them like everything else you ship - versioned, reviewed, and deployed automatically to wherever your teams actually read them.

Docs live with the code

Update docs in the same pull request as the change that made them necessary - one review, no separate wiki to forget. The same CI you trust for code lints, spell-checks, and validates links before a doc ever ships.

One write, many homes

Some teams live in Confluence, others in Zendesk, support somewhere else entirely. Write once in Markdown and Doxxy publishes to all of them at once, so the people who need a doc actually see it - no exports, no copy-paste drift.

Yours to move

Your docs are plain Markdown in your repo, not hostages in a vendor's database. Switch destinations whenever you want and switch back - the source of truth never leaves git, so you're never the one locked in.

Bring your own AI

Plain Markdown is the universal feed for AI tooling. Because your docs stay portable - not trapped in a vendor's format - you can pipe a policy library or knowledge base into Bedrock, Foundry, or your own RAG stack.

No servers to run

Nothing to host, scale, or babysit. The sync runs inside your GitHub runner and exits - no daemon, no queue, no dashboard to keep alive. Your CI minutes are the only infrastructure involved.

Auditable by design

git already records who changed which word, when, and why - forever. Every doc edit carries the same audit trail as your code, down to the letter, so compliance gets its history for free.

The trust model

Your docs never touch our servers.

Doxxy runs entirely inside your own GitHub runner. Each destination driver talks directly to its platform's API - Confluence, Notion, Drive - and the bytes of your documentation never pass through Doxxy. We can't leak what we never receive.

Every dependency is pinned, and the Doxxy action refuses to run unless you version pin. Your build is reproducible and immune to a supply-chain attack - integrity and security aren't settings, they're the default.

What crosses the wire

Two things, ever - and never your content:

  • A license verdict, handled entirely via OIDC claims.
  • Basic telemetry: run success, version, timing.
  • Never: your docs, repo contents, or credentials.
  • Never: a binary we didn't pin and you didn't verify.

See it on your own repo.

Point Doxxy at a repo, push, and watch your docs land where your teams already work. Free to start.

Start free