A URL for everything Copilot makes
Where humans and Copilot
work on proposals together.
Copilot generates the code. display.dev is where your team sees the output – architecture proposals, reports and dashboards behind company SSO, with no git push and no GitHub account for viewers.
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.
Copilot's HTML output has no home your team can open
GitHub Copilot and Copilot Workspace generate HTML artifacts: architecture proposals, competitive analyses, technical reports, implementation plans. All rendered, interactive, and self-contained. Sharing them is the same broken problem no matter which tool generated the file.
The artifact took minutes to generate. It has no home.
- ✗GitHub Pagesprivate repos require Enterprise Cloud ($21/user/month as of 2026). Your PM, designer, and product lead have no GitHub account.
- ✗Push to a repo and share a linkthe link shows raw HTML source, not the rendered page.
- ✗Screenshotinteractivity gone.
- ✗Slack uploaddownloads as a file.
Three ways to publish Copilot's output
npm install -g @displaydev/cli, then publish where Copilot already runs. The URL comes back in the same command.DISPLAY_TOKEN in secrets and every workflow run publishes the artifact.Who can open it
A public URL, no sign-in. Free covers unlimited public links.
Named email addresses only. Useful for a client or a contractor you don't want to hand company sign-in to.
Anyone signing in with a verified company domain gets in – Google Workspace, Microsoft Entra ID, or a one-time password by email. Viewers are unlimited on every plan.
No GitHub account anywhere. Viewers sign in with the Google or Microsoft account they already use. No Copilot license, no developer tooling.
Works alongside your GitHub workflow
display.dev doesn't replace GitHub – it adds the publishing layer GitHub doesn't have. Keep Copilot in your IDE and Copilot Workspace for code generation; when the output is an HTML artifact non-engineers need to review, dsp publish gives it a home outside the git tree.
The GitHub Pages gap for internal sharing
- Private repo Pages needs GitHub Enterprise Cloud
- $21/user/month. For 100 viewers, that's $2,100/month to read internal HTML.
- Every viewer needs a GitHub account
- PMs, executives, legal, sales, designers. Most don't have one, and shouldn't need one to read a migration proposal.
- display.dev is €49/month flat
- Any company email authenticates. No GitHub account and no GitHub license for viewers.
GitHub Copilot artifact sharing compared
| Option | Non-engineer viewers | Company auth | Interactivity | Time | Cost |
|---|---|---|---|---|---|
| GitHub Pages (private) | ❌ | ❌ / $2,100/mo | ✅ | git push | $0 / $2,100/mo |
| Raw GitHub link | ❌ (shows source) | ❌ | ❌ | seconds | $0 |
| Screenshot | ✅ (degraded) | – | ❌ | 10 sec | $0 |
| Vercel + SSO | ❌ | ✅ | ✅ | 20+ min | Enterprise tier |
| display.dev | ✅ | ✅ | ✅ | 15 sec | €49/mo flat |
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 its own 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 other agent that creates HTML or Markdown output. Change agents anytime: your URLs, versions, and comments stay put when you switch.
Try it free
- Publish a Copilot artifact in under a minute, no card
- Keep the URL when you upgrade
- Unlimited viewers on every plan
Common questions.
Do viewers need a GitHub account?
No. display.dev uses your company's Google or Microsoft email for authentication. Viewers don't need a GitHub account, a Copilot license, or any developer tooling.
Can I publish from within VS Code where Copilot runs?
Yes. Open VS Code's integrated terminal and run dsp publish ./file.html. Or configure the display.dev MCP server so the agent publishes its own output.
How is this different from just pushing to GitHub Pages?
GitHub Pages serves to anyone (public) or requires GitHub accounts plus Enterprise for private. display.dev adds company-email authentication on top of file serving, without the GitHub account requirement or the per-seat pricing.
Can I share Copilot Workspace task outputs?
Yes. Copilot Workspace generates HTML task summaries and implementation plans. Download them, run dsp publish, share the URL.
Can a CI run publish the artifact automatically?
Yes. Add a dsp publish step to the workflow with DISPLAY_TOKEN in secrets. Every run publishes the generated HTML and returns its URL.
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).

