← comparisons
cristina vs GitBook
docs that ship with your code. artifacts that don't.
GitBook is the cleanest solution for versioned technical documentation. Write in their editor, connect a GitHub repo, and your docs deploy with every merge. That workflow is excellent — for humans committing markdown. When an agent produces an HTML dashboard or a generated prototype, GitBook has no answer. There's no endpoint that receives HTML and returns a URL.
feature by feature
feature
GitBook
cristina
POST endpoint for agents
no
yes — /api/artifacts
raw HTML rendering (sandboxed)
no
yes — iframe, allow-scripts
permanent URL per artifact
yes
yes
API key auth for agents
no direct API
one API key
Git-synced versioned content
yes
no
folder organization
yes — sections
yes — color-coded folders
inline comments / annotations
limited
yes — pinned markers
where gitbook wins
- +Git-synced docs — every commit to main updates the published docs automatically
- +Beautiful default documentation themes that need no design work
- +Versioning and changelog support baked into the publishing flow
- +OpenAPI spec imports for auto-generated API reference pages
- +Custom domain publishing with SSL in minutes
where gitbook falls short
- −No POST endpoint for agents — content arrives via editor or Git only
- −Raw HTML rendering: not the use case; markdown to styled docs is the model
- −Living artifacts that change on each agent run: no concept for this
- −Internal team use with quick sharing — GitBook is optimized for external documentation
- −Comments and discussion: the tooling is minimal compared to collaborative wikis
where we're honestly worse
we'd rather say it than have you find out later
- ·Versioned documentation — GitBook's Git-sync is purpose-built for this; we have no versioning
- ·Public-facing doc sites — GitBook produces polished external docs; cristina is internal-first
- ·OpenAPI rendering — auto-generated reference pages from a spec are not something we do
- ·Custom domains — GitBook's publishing flow is one click; we're behind your team's login
- ·Long-form structured content — navigating a docs site with sidebars, anchors, search
why cristina anyway
- →Agents POST an artifact and get a URL — no Git commit, no human editor step
- →HTML renders as-is in a sandbox — no markdown conversion, no theme override
- →A URL per artifact from the first POST, not from the next deployment
- →Internal team browsing by folder — not a public-facing documentation site
- →PATCH to update a living artifact — the same URL stays valid as the agent re-runs
bottom line
GitBook is the right tool for versioned documentation your engineers write. Cristina is the right tool for HTML your agents build.