Skip to content

Why Topicary

The gap between easy and powerful

Why I built the docs tool I wanted as a one-person docs team, where it goes deeper than the easy tools, and where it honestly doesn't go as deep as the enterprise ones.

The gap

Easy tools vs powerful tools

Documentation tools split into 2 camps. On one side: Paligo, MadCap Flare, Heretto. Structured authoring: content reuse, conditions, multi-format publishing. They cost $2,999+/author/year (Flare Desktop) to $32,680/year median (Paligo), require weeks of training, and target teams of 25+ writers.

On the other side: GitBook, Confluence, Notion, Document360. Modern UX, fast onboarding, lower pricing. But no component-level reuse, no conditional content, and no real multi-format output.

A sweep of 200+ documentation tools (May 2026) confirmed this: no tools offer component-level content reuse, conditional content, and multi-channel publishing in a cloud-native interface below $185/mo.

Independent software

Bootstrapped. No venture capital.

Topicary is bootstrapped. No venture capital. No board to satisfy. No pivot toward enterprise sales when the growth metrics dip. I built this because I needed it and could not find it. That means no acqui-hire risk, no “sunsetting” announcement, no forced migration to a platform you did not choose. I publish a dated changelog with every feature shipped.

Migration

Import details by format

Drag a file or zip onto the import dialog. Format auto-detected, preview before you commit.

Markdown

Transfers

Headings, paragraphs, lists, code blocks, images, tables, links

Does not transfer

Front matter (preserved as raw text)

HTML

Transfers

Semantic structure, tables, images, links, lists

Does not transfer

JavaScript, external stylesheets, embedded scripts

DITA

Transfers

Concepts, tasks, references, ditamaps with hierarchy, conrefs as component references

Does not transfer

Relationship tables, specializations, subject schemes

Confluence

Transfers

Pages, hierarchy, macros (cleaned/converted), images, tables

Does not transfer

Confluence-specific macros (Jira, Roadmap), user mentions

MadCap Flare

Transfers

Topics, snippets as components, table of contents as maps, variables, conditions

Does not transfer

Micro content, target settings, custom stylesheets, skins

Word (.docx)

Transfers

Headings, paragraphs, lists, tables, images

Does not transfer

Track changes, comments, embedded objects, macros

OpenAPI 3.x

Transfers

Endpoints as topics with method badges, schemas, parameters, examples

Does not transfer

Server-side validation, webhook definitions

Comparison

Feature by feature

Content reuse

Topicary

Block + inline, where-used tracking, orphan detection, per-instance variable overrides

Paligo

Block + inline (text fragments), reuse dashboard

MadCap Flare

Snippets, cross-project linking

GitBook

Reusable blocks (no tracking, no conditions)

Conditional content

Topicary

Boolean expressions (AND/OR/NOT), visual builder, per-block, in-editor preview

Paligo

Dimensions, filter sets, profiling dashboard

MadCap Flare

Conditions, target-based filtering, expressions

GitBook

Not supported

Variables

Topicary

Variable sets, per-instance overrides on component refs, publish-time replacement

Paligo

5 types (text, translatable, image, XML, dynamic)

MadCap Flare

Variable sets, target-level overrides

GitBook

Not supported

Content branching

Topicary

Topic branches, three-way merge, release management (Draft/Published/Archived)

Paligo

Publication branches, DeltaXML merge, release management

MadCap Flare

Not supported (uses source control)

GitBook

Draft/merge workflow

Real-time collab

Topicary

Yjs CRDT, cursor presence, offline queue

Paligo

Basic concurrent editing

MadCap Flare

Not supported (desktop)

GitBook

Supported

Track changes

Topicary

Suggest mode, per-suggestion accept/reject, bulk actions, author notifications

Paligo

Basic review annotations

MadCap Flare

Not supported

GitBook

Not supported

Translation

Topicary

XLIFF 2.0 round-trip, Phrase TMS, per-locale status tracking

Paligo

XLIFF, 6+ TMS integrations, bilingual editor

MadCap Flare

Lingo, XLIFF

GitBook

Not supported

Web publishing

Topicary

Hosted, dark mode, AI search, custom CSS, custom domains, password protection

Paligo

Self-host or Netlify, Zendesk/Salesforce

MadCap Flare

Self-host, context-sensitive help

GitBook

Hosted, custom domain

PDF output

Topicary

Configurable layout, TOC with page numbers, cross-ref page numbers, cover page

Paligo

XSL-FO, Layout Editor, full page design, running headers

MadCap Flare

Full print: auto-numbering, index, master pages, prepress

GitBook

Basic export

AI

Topicary

Context-aware inline AI, chat with tool use, automatic staleness / duplicate / contradiction detection, schema validation, MCP

Paligo

Basic AI writing assistance

MadCap Flare

GPT-4o writing assistance

GitBook

GitBook Agent

LLM-ready output

Topicary

llms.txt, .md URLs, sitemap.md, ?ask= endpoint, MCP server, structured JSON

Paligo

None

MadCap Flare

Plugin ($99/yr) for llms.txt

GitBook

llms.txt, .md URLs, MCP server

SSO

Topicary

SAML 2.0 SP, XSW-hardened

Paligo

SAML, SCIM

MadCap Flare

None (desktop)

GitBook

SAML (Enterprise)

API and webhooks

Topicary

REST API (8 endpoints), webhooks (10 events, HMAC-SHA256)

Paligo

API available

MadCap Flare

None

GitBook

API

GitHub sync

Topicary

Bidirectional, HMAC webhooks, conflict resolution

Paligo

None

MadCap Flare

Limited

GitBook

Native

Import formats

Topicary

7 (Markdown, HTML, DITA, Confluence, Flare with full preservation, Word, OpenAPI)

Paligo

4 (DITA, Word, HTML, Markdown)

MadCap Flare

DITA, Word, RoboHelp, HTML

GitBook

Markdown, GitHub

SME review

Topicary

Token-based (no login), suggest mode, formal assignments with due dates

Paligo

Contributor accounts required

MadCap Flare

No built-in review

GitBook

Not supported

Approval workflows

Topicary

Custom status chains, role-based transitions, stage enforcement

Paligo

Basic workflow

MadCap Flare

None

GitBook

None

app.topicary.com
Structured authoring without XML in the Topicary editor: a reusable component, an audience-conditioned block, and a variable token in a single topic, with the content map and properties panels

This table is honest. Paligo has deeper translation integrations (6+ TMS, bilingual editor) and more variable types. Flare has a more mature PDF engine for prepress production. If those are requirements, evaluate Paligo or Flare directly.

Pricing

Cost comparison at real team sizes

Verified pricing with sources and dates. No contact-sales guesswork.

3 writers

Topicary

$79/mo (Pro)

Paligo

~$1,430 to $3,535/mo*

MadCap Flare

$750/mo ($2,999/yr × 3)

ClickHelp

~$630/mo†

GitBook

$89/mo ($65 + $12×2)

5 writers

Topicary

$149/mo (Team)

Paligo

~$1,430 to $3,535/mo*

MadCap Flare

$1,250/mo ($2,999/yr × 5)

ClickHelp

~$1,055/mo†

GitBook

$113/mo ($65 + $12×4)

10 writers

Topicary

$149/mo (Team)

Paligo

Negotiated

MadCap Flare

$2,499/mo ($2,999/yr × 10)

ClickHelp

~$1,200+/mo†

GitBook

$173/mo ($65 + $12×9)

The math

Per-writer cost at real team sizes

A 3-writer team pays $79/mo total on Topicary Pro, $26 a writer. The same team on Paligo pays an estimated $1,434 to $3,535/mo (Vendr contract data). On Flare Desktop, that is $2,999/yr per author ($750/mo for 3). On ClickHelp with equivalent features (API, SSO, AI, translation): ~$630/mo. At 5 writers on Topicary Team, you pay $149/mo, $30 a writer. Topicary charges by plan, not by seat, and includes SSO, API, AI, translation, and webhooks at no extra cost.

*Paligo does not publish pricing. Range from Vendr marketplace: median annual contract $32,680, range $17,203 to $42,425. Source: vendr.com/marketplace/paligo, checked 2026-05-26.

†ClickHelp advertised price for 5 contributors is $310/mo. Add API access (+$125/mo), SSO (+$125/mo), AI features (+$300/mo), and translation (+$195/mo), all included in Topicary, and the real cost is $1,055/mo. Source: clickhelp.com, checked Jun 2026.

Honest positioning

Where enterprise tools go deeper

Topicary matches or exceeds enterprise tools on most dimensions relevant to 2 to 15 writer teams. 2 areas where incumbents have genuinely deeper implementations:

  • Professional PDF composition Topicary generates branded PDF with cover page, table of contents, and configurable headers/footers. Flare and Paligo offer deeper PDF control: running section headers, auto-numbering, and back-of-book indexes via XSL-FO layout engines.
  • Inline / sentence-level reuse Components are block-level: full paragraphs, callouts, tables. You cannot yet reuse a single phrase or sentence within a paragraph. Paligo supports text-fragment reuse.
app.topicary.com
The Topicary translation panel showing per-locale status for a topic — Spanish and German translated, French untranslated — with XLIFF export for each locale

If either of these is a hard requirement, Paligo has 6+ TMS integrations and a bilingual editor. MadCap Flare has a 20+ year prepress PDF engine. I link to their documentation on the comparison pages because sending you to the right tool builds more trust than claiming I do everything.

Start writing today

Free during beta. All features, no limits, no credit card.