Can GitBook host HTML files?

No. GitBook renders its own content format (created in the GitBook editor or synced from Markdown via Git). Uploaded arbitrary HTML files are not supported. If your HTML file comes from Claude Code, a test runner, or a data visualization tool, GitBook cannot host it.

Does Display have an editor?

No. Display is a publishing tool, not an authoring tool. You create content wherever you create it — Claude Code, Cursor, a CI pipeline — and Display publishes it behind company auth. There's no editor and no content management workflow.

What's the cheapest GitBook plan with visitor auth?

Ultimate: $249/month. This is the lowest tier that includes visitor authentication for a GitBook space.

Can I import GitBook content into Display?

GitBook supports exporting content as Markdown via Git sync. You can publish those Markdown files with Display using `dsp publish ./docs/`. Display renders Markdown to HTML and serves it at an authenticated URL.

GitBook vs. Display: Which Is Right for Internal Sharing?

Price comparison

	GitBook Ultimate	Display Teams
Monthly cost	$249	$49
Visitor authentication	✅ (included)	✅ (included)
Arbitrary HTML hosting	❌	✅
Markdown rendering	✅	✅
CLI publishing	❌	✅
MCP integration	❌	✅
Structured documentation editor	✅	❌
AI search on your docs	✅	❌
Per-seat pricing (editors)	✅	❌
Unlimited viewers	✅ (Ultimate)	✅

The $200/month price difference reflects two different products solving two different problems.

What GitBook is for

Maintained documentation sites. API references, developer guides, product knowledge bases, onboarding documentation — content that has a long-term editorial workflow, a tree structure, multiple editors, and continuous updates.

GitBook is excellent for this. The editor is clean, the Git sync (for docs-as-code workflows) is reliable, and the AI search is genuinely useful for large documentation sets. If you're building and maintaining structured documentation that lives indefinitely and has multiple authors, GitBook is a strong choice.

What GitBook can't do

Host arbitrary HTML. If you have an HTML file from Claude Code, a Playwright report, a D3 visualization, or a data export — GitBook cannot render it. GitBook's content model is its editor or Markdown via Git sync. It doesn't serve uploaded HTML files.

Publish ad-hoc. GitBook is designed for maintained documentation, not "I have a file and need my team to see it in 15 seconds." There's no CLI equivalent to dsp publish ./report.html.

Offer visitor auth under $249/month. Visitor authentication — restricting a GitBook space to specific viewers — is only available on the Ultimate tier. The Premium tier ($65/month per space) does not include visitor auth.

When to use GitBook

You're building and maintaining structured developer documentation, product docs, or an internal knowledge base with a long-term editorial workflow. You want collaborative authoring, AI-powered search, and a polished documentation UI. You need API reference generation or OpenAPI integration.

GitBook is doing a different job. If that's your job, it's a good tool.

When to use Display

You have HTML or Markdown files to share — artifacts, reports, presentations, CI outputs. You don't need an editor. You need a URL. You want arbitrary HTML rendered correctly, not converted to someone else's format. You want $49/month flat for your whole workspace, not $249/month for visitor auth on one documentation space.

Can you use both?

Yes, and many teams do. GitBook for structured, maintained external or internal documentation. Display for ad-hoc publishing of AI artifacts, CI reports, and internal presentations that don't belong in a documentation tree.

The distinction: GitBook is for content you maintain. Display is for content you produce and distribute.