Antora

Static site generator that assembles versioned AsciiDoc documentation from many git repositories

As of 31 August 2026, Antora is free to use. Antora is built for the case where documentation lives beside code in several repositories and several branches at once. Softwr lists it under Documentation. Antora is made by OpenDevise, available on Self-hosted.

Visit siteVisit Antora

Overview

What Antora does

Antora is a static site generator for technical documentation written in AsciiDoc, from the team behind Asciidoctor. Its content model is component, version and module: a documentation component is a git repository, its versions are branches or tags in that repository, and a single playbook file lists the repositories and branches to include. At build time Antora clones or fetches each source and produces one site containing every component and every version, with a working version selector and cross-references that resolve across repository boundaries. That is the whole reason to choose it. Most documentation generators assume one repository and one version, and multi-version support is bolted on by copying directories. Antora treats several products, each with several supported releases, each maintained by a different team in its own repository, as the normal case. For a software vendor that supports three releases of four components, this is the difference between a build system and a permanent coordination problem. AsciiDoc itself also carries more semantics than markdown: includes, conditionals, attributes and admonitions are part of the language rather than plugin syntax. The cost is that everything must be AsciiDoc, the conceptual model has to be learned before the first build succeeds, and the site appearance is controlled by a separate UI bundle that expects Handlebars templates and a build pipeline of its own. There is no built-in search, so you add a Lunr extension or a hosted search service. The buyers are enterprise software vendors and large open-source projects with real documentation teams; a single-product team with one version will find the machinery disproportionate.

What people use it for

Publishing one documentation site from several product repositories owned by different teams
Maintaining documentation for three or more supported releases without copying directories
Enterprise documentation teams that already write in AsciiDoc and need version-aware cross-references
Keeping documentation in the same repository and pull request as the code change it describes

Where it falls short

Concrete and checkable, so you can decide whether any of them matter to you. This is the half of a review a vendor will not write about Antora.

Content must be AsciiDoc, so an existing markdown documentation set has to be converted before you can evaluate the tool properly.
The component, version and module model must be understood before anything builds, and the first working site typically takes days rather than the afternoon a markdown generator needs.
Theming means building a separate UI bundle with Handlebars templates and its own pipeline, which is a front-end project most documentation teams are not staffed for.
There is no search included, so every deployment adds either a Lunr extension with its own index size limits or a paid hosted search service.
Builds fetch from every configured repository, so large multi-component sites become slow and depend on git availability during every documentation build.

Cross-shopped

What people choose instead of Antora

Each pairing was judged by two reviewers asking whether a buyer would genuinely weigh the two against each other. The ones that failed were deleted rather than published.

Antoravs
Sphinx
Sphinx: Deep cross-referencing and API documentation for Python and C projects, with a large extension set
Antoravs
Docusaurus
Docusaurus: Markdown, versioning and a React theme when contributors will not learn AsciiDoc
Antoravs
MkDocs
MkDocs: Far less machinery when the documentation is one product with one current version

Pricing

What Antora costs

Taken from the vendor's own pricing page. Prices move, so check before you buy.

Antora

Free

Mozilla Public Licence 2.0
Unlimited components and versions
No hosting or seat costs
Community support, with paid consulting available from OpenDevise

Capabilities

Features

Multi-repository sourcing
A playbook lists git repositories and branches, and Antora fetches content at build time
Version handling
Branches and tags become published versions with a selector and version-aware cross-references
AsciiDoc
Includes, attributes, conditionals and admonitions as language features rather than plugins
Cross-component references
Links between different products and versions validated at build time instead of failing silently
Separate UI bundle
Site appearance is a versioned artefact that can be shared across several documentation sites
Content reuse
Partials and shared modules included across components without copying text between repositories

Answered, with sources

Questions people ask

Each answer names the page it came from, so you can check it rather than take our word for it.

Can I use markdown with Antora?

Not as the primary format. Antora is an AsciiDoc pipeline, and treating markdown as a first-class input means a different tool.

Is it worth it for a single product with one version?

Usually not. The model pays off when you have several repositories or several supported versions; below that a simpler generator will do the same job with far less setup.

How does versioning actually work?

Each branch or tag of a source repository becomes a version of that component. You publish a new version by branching, not by copying a directory.

Who maintains it?

OpenDevise, the group behind Asciidoctor, under the Mozilla Public Licence. Paid consulting and custom UI work are available from them separately.