A URL for every docs build you publish
Where your engineers
and agents work on internal docs.
A runbook meant for employees is published to a public site, or its replacement gets a new URL and leaves the old instructions in Slack. Build with MkDocs, Docusaurus, Sphinx or any static doc generator, then publish behind company auth at the same URL. €49/month flat for the entire company.
The demo shows an agent publishing a doc to display.dev – from a chat or a terminal – then the team opening its URL, commenting, the agent publishing v2 at the same URL, and the doc being shared with someone outside the company.
Cursor, Codex, Claude Code – any agent that writes a file. Switch agents anytime – your URLs, versions and comments stay put.
Indigo Engineering
The command
# After building your docs
dsp publish ./site/ --name "internal-runbooks"
# Returns: https://acme.dsp.so/0kzNYG7O-internal-runbooksAny @yourco.com email authenticates with one click and reads the documentation.
Starting from a blank page? The product spec, incident postmortem, and meeting notes templates publish in one click – no account.
Internal documentation needs internal access control.
An internal runbook should not become public because the publishing tool lacked a company-only option. It should also keep the same address after the next build. display.dev pairs explicit company access with in-place updates and retained versions. Runbooks, architecture decision records, onboarding guides, process docs – readable by the whole company, not by the public internet. Every existing option charges for that in seats or in setup days (prices as of 2026).
Publish your MkDocs or Docusaurus build and get a company-gated URL. €49/month, no per-seat pricing.
- ✗Confluence$6.05–$11.55 per user per month, so every reader is a paid seat, and static doc builds don't import cleanly.
- ✗GitHub Pages, privateEnterprise Cloud at $21 per user per month, plus a GitHub account for every reader. PMs, ops and HR don't have one.
- ✗GitBook$249/month for visitor auth, treated as an enterprise upgrade on a product built for public docs.
- ✗Notionno way to serve arbitrary HTML. You rebuild the docs in Notion's editor instead.
- ✗VercelSSO is $300/month, and every site needs a git project.
- ✗S3 + Cognitoengineering days to set up and someone to maintain it after that.
display.dev vs. alternatives for internal docs
| display.dev | Confluence | GitBook (visitor auth) | GitHub Pages (private) | |
|---|---|---|---|---|
| Monthly price (100 viewers) | €49 flat | $1,155/mo (Premium) | $249/mo | $2,100/mo |
| Google SSO | ✅ | ✅ | ✅ | ❌ |
| Microsoft SSO | ✅ | ✅ | ✅ | ❌ |
| Any static HTML site | ✅ | ❌ | ❌ | ✅ |
| Viewers need accounts | ❌ | ✅ (paid seats) | ❌ | ✅ (GitHub) |
| CLI publish | ✅ | ❌ | ❌ | git push |
| Collaborative editing | ❌ | ✅ | ✅ | ❌ |
_Competitor prices as of 2026; check their current plans._
What display.dev is not
- Not an editor
- display.dev doesn't edit your documentation. It publishes it.
- Not a wiki
- For docs a team writes and maintains together, Confluence, Notion and GitBook are good at exactly that. Use them for it.
- The publishing step
- When you have a built static site and it needs to reach the company behind company auth, that's this. Write in Confluence, publish the HTML artifacts here.
Workflows by generator
CI/CD – publish on every merge
name: Publish Internal Docs
on:
push:
branches: [main]
jobs:
docs:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Install and build
run: |
pip install mkdocs mkdocs-material
mkdocs build --site-dir ./site
- name: Install display.dev CLI
run: npm install -g @displaydev/cli
- name: Publish docs
run: |
BASE_VERSION=$(dsp get-metadata "${{ vars.DISPLAY_ARTIFACT_ID }}" | jq -r .currentVersion)
dsp publish ./site/ --id "${{ vars.DISPLAY_ARTIFACT_ID }}" --base-version "$BASE_VERSION"
env:
DISPLAYDEV_API_KEY: ${{ secrets.DISPLAYDEV_API_KEY }}Every merge to main automatically updates the published documentation using the artifact ID stored in DISPLAY_ARTIFACT_ID.
Pricing
Try it. No credit card.
- Included: 10 gated artifacts
- Included: Unlimited public artifacts*
- Included: 50MB storage
- Not included: Version history
- Not included: Google + Microsoft SSO
- Not included: Audit logs
display.dev branded
Individuals. Unlimited gated sharing.
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: 1GB storage
- Included: 10 versions
- Not included: Google + Microsoft SSO
- Not included: Audit logs
For teams that need company auth.
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: 25GB storage
- Included: 50 versions
- Included: Google + Microsoft SSO
- Included: 90 days audit logs
For compliance-driven organizations.
From €499/mo
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: Custom storage
- Included: Unlimited versions
- Included: Google + Microsoft SSO
- Included: 365 days audit logs
Features
Viewers click a link and sign in with their Google or Microsoft account, or a one-time password. No app to install. No account to create. No IT ticket.
Inline comments on every artifact. Your agent reads them via MCP, fetches the current version, republishes with short_id and base_version, and resolves the thread. The artifact stays the current version at the same URL, not a one-shot screenshot.
dsp publish ./file.html from your terminal, or one sentence in Claude Desktop. No git repo, no deploy pipeline, no project to configure.
Every artifact gets a URL that keeps working. Share in Slack, link in Notion, paste in email. It still works six months later.
No per-seat pricing at any tier. Share with your PM, exec, legal team, or designer for the same flat price.
Cursor, Codex, and Claude Code all work, along with any agent that creates HTML or Markdown output.
What teams say
It's been an unexpectedly great way to move on from Google Docs, since so many of our docs are now native to markdown and getting them into a friendly Google Doc format for visibility and collaboration had become a real chore.
Try it free
- Publish a docs build in 15 seconds, no card
- Every reader signs in with the company account they already use
- Unlimited viewers on every plan, no per-seat charge
Common questions.
Can display.dev replace Confluence for our team?
For read-only documentation published from a static generator – yes. display.dev is simpler and cheaper. For collaborative wikis with in-browser editing, search, and Jira integration, Confluence does things display.dev doesn't. The two complement each other.
Does search work in MkDocs or Docusaurus published via display.dev?
Yes, if the search index is generated at build time (which MkDocs Material and Docusaurus do by default). Client-side search works fully. Server-side search integrations (Algolia, Elasticsearch) work if the search provider is accessible.
Can I have multiple documentation sites?
Yes. Each dsp publish call with a unique name creates a separate artifact. acme.dsp.so/0kzNYG7O-platform-runbooks, acme.dsp.so/0kzNYG7O-engineering-handbook, acme.dsp.so/0kzNYG7O-onboarding-guide – all under the same €49/month.
What's the storage limit for documentation sites?
MkDocs sites: 5–20MB. Docusaurus sites: 10–50MB. Sphinx sites: variable. display.dev's Pro tier (25GB) handles hundreds of documentation sites simultaneously.
Can I set a custom domain for internal docs?
Yes, on Enterprise – e.g., docs.yourcompany.com. Custom domains are an Enterprise feature; every other tier serves from acme.dsp.so.
Publish your first artifact in 15 seconds.
Free tier. No credit card. One-time password auth on free, Google + Microsoft SSO on Pro (€49/month flat).