/
display
█
/
display
█
How it works
Pricing
Blog
Get started free
Display
/
Blog
Blog
Notes on gated publishing, AI artifact sharing, and the engineering behind display.dev.
What Is Gated Publishing?
Gated publishing: serving HTML or Markdown behind company identity — no public URL, no GitHub, no IT ticket. Here's how it works and when to use it.
Vercel SSO vs. Display: Which to Use for Internal HTML Sharing
Vercel requires a full deployment pipeline to serve an HTML file. Display skips the pipeline — drop any file, get a company-gated URL in 15 seconds.
Tiiny Host Alternatives With Real Company Auth (Not Shared Passwords)
Tiiny.host is fast for public HTML. For internal content you need company SSO, not a shared password. Here's what teams use when viewers shouldn't need accounts.
Host Swagger UI Behind Company Auth (Without Cloudflare Access)
Swagger UI and Redoc export standalone HTML. Here's how to host internal API docs behind company SSO without Cloudflare Access or a new server.
The Compliance Case for Managed Gated Publishing
Sharing internal HTML via public URLs or open S3 buckets creates audit findings. Here's the compliance case for managed gated publishing and SOC 2.
Publish a Plotly Dashboard Behind Company SSO
Plotly and Dash export interactive HTML. Publishing them behind company login so stakeholders can view without a Python environment takes one command.
Share Jupyter Notebook HTML With Stakeholders (No Email Attachments)
Jupyter exports to HTML. Sending it as an email attachment means recipients can't open it properly. Here's how to share it as a permanent authenticated URL.
Share Internal Docs Without Confluence
Confluence is overkill for a Markdown spec or HTML report. Here's how to share internal docs behind company auth without a wiki or per-seat pricing.
The 7 Ways Engineers Share HTML Files With Their Team (And Why 6 Fail)
There are 7 ways engineers share HTML files internally. Screenshots, Slack uploads, PDFs, Google Docs — six destroy the interactivity. One works.
How to Share Claude Code Artifacts With Your Whole Team
Claude Code writes HTML to your local filesystem. Here's how to share those artifacts with your whole team — including non-engineers — in one command.
How to Share Your Claude Artifacts Securely — No Terminal Required
PMs and analysts use Claude too. Here's how to share Claude artifacts with your whole team — including people without Claude access — no terminal needed.
Share Interactive Architecture Diagrams With Your Team
D3, Mermaid, and Excalidraw export interactive HTML. Screenshots lose the interactivity. Here's how to share architecture diagrams with your team in full fidelity.
Build vs. Buy: S3 + Cognito vs. Managed Gated Publishing
S3 + Cognito + CloudFront is the DIY version of gated publishing. Here's an honest build vs. buy breakdown: time, cost, and maintenance.
How to Publish Storybook Internally With Company Auth (Without Vercel)
Storybook exports static HTML. Publishing it internally behind company SSO — accessible to designers and PMs without GitHub — takes one command.
Why Per-Seat Pricing Kills Internal Sharing
Per-seat pricing makes sense for active users. For content shared with passive viewers — PMs, execs, clients — it punishes you for having a larger audience.
Share a MkDocs Site With Your Team (No GitHub Account Required)
MkDocs builds a static HTML site. Here's how to share it with teammates who don't have GitHub, behind company auth, without any new infrastructure.
MCP Tools for Publishing: How AI Agents Share Their Own Output
AI agents can now publish their own output via MCP. Here's how MCP publish tools work and why they change how teams receive AI-generated content.
The Imgur Parallel: Building the Default HTML Host for Engineering Teams
Imgur became the default image host because uploading was instant. Gated publishing is the missing equivalent for engineering teams sharing HTML internally.
GitHub Pages Private Repos: What Engineering Teams Use Instead
Private GitHub Pages requires Enterprise at $21/user/month, and every viewer needs a GitHub account. Here's what teams use instead for internal HTML sharing.
From GitHub Actions to Authenticated URL: A Better Way to Share CI Artifacts
GitHub Actions produces HTML reports. Here's how to publish them behind company auth automatically — one step in your workflow, no manual upload.
GitBook vs. Display: Which Is Right for Internal Sharing?
GitBook charges per reader for visitor authentication. Display gates HTML and Markdown behind company SSO for a flat monthly fee. Here's how they compare.
Gated Publishing vs. Public Hosting: What's the Difference?
Public hosting gives you a URL anyone can see. Gated publishing restricts it to your company. Here's the difference and when to use each.
Why Google Drive Can't Share Your HTML File (And What Can)
Google Drive, Slack, Dropbox — none render HTML files for teammates. Here's what happens with each sharing method and what actually works instead.
Why We Called It "Gated Publishing" (And the 7 Names We Rejected)
We tested 7 names for this category before landing on gated publishing. Here's what each got wrong and why the definition matters.
Cloudflare Access Alternatives: Internal Static Hosting Without Per-Seat Pricing
Cloudflare Access charges per seat to gate static files. Here's how teams get authenticated internal HTML hosting without the per-seat pricing.
Why Claude's "Publish" Button Doesn't Work for Internal Sharing
Claude's Publish button creates a public URL anyone can see — no access control. Here's how to share Claude artifacts behind your company login instead.
How to Publish Claude Desktop Artifacts to Your Team (MCP Setup Guide)
How to add Display as an MCP tool in Claude Desktop so you can publish any artifact to your team in one conversation turn — no terminal, no GitHub.
From Claude Code to Team URL in 15 Seconds
Claude Code output sits in a local file. Here's how to turn it into a company-gated URL your whole team can open — one command, 15 seconds.
Azure Static Web Apps and the Google SSO Problem
Azure Static Web Apps only supports Microsoft Entra, not Google Workspace. Here's what teams on Google SSO use instead for internal HTML hosting.
AI Agents Are Creating an Internal Publishing Problem Nobody Has Solved
AI agents generate polished HTML reports and docs — and then there's no good way to share them internally. Here's why standard tools all fail.
Agent-Native vs. Human-Native: Why Your Knowledge Tool Needs to Be Built for AI From the Start
AI agents don't browse wikis. An agent-native knowledge platform stores information in formats agents can query directly — not formats built for human browsers.