For

Display for Cursor

Cursor builds it in seconds. Display is how you share it with the team behind your company's Google or Microsoft login. One command. Permanent URL. No accounts for viewers to create.

Free tier available$49/month flat for TeamsGoogle + Microsoft SSOUnlimited viewers
terminal
$ display publish ./report.html
 
Uploading    47kb
Auth       Google Workspace ✓
 
✓ Published
 
→ https://view.display.dev/p/f474hfd/8f3kx9
 
Viewers    anyone at acme.com
Expires    never
Version    1
 
$ 

Cursor builds fast. Sharing breaks.

Cursor's agent mode generates full React dashboards, D3 visualizations, interactive reports, and polished UI prototypes — in minutes. You have a ./dist folder or a standalone HTML file that looks great in your browser.

Then you need to share it.

The options that exist: screenshot (loses interactivity), GitHub Pages (requires Enterprise for private repos, excludes non-engineers), Vercel (requires a git project, $320/month for SSO). None of them fit the "Cursor just built this in 3 minutes" workflow.

Display fits. One command. Done.


From Cursor to team URL

For a single HTML file:

dsp publish ./output.html

For a build directory (React, Vite, etc.):

dsp publish ./dist/ --name "dashboard-v2"

What your teammates see: Click the link. Authenticate with company Google or Microsoft email — once, five seconds. Full interactive build: React components, animations, live-looking data, everything Cursor generated.

No accounts to create. No GitHub access needed. No Vercel project to configure.


What Cursor builds — and what Display publishes

Cursor outputDisplay command
Standalone HTML filedsp publish ./output.html
React/Vite builddsp publish ./dist/
Component demodsp publish ./demo/index.html
Data visualizationdsp publish ./chart.html
Internal tool prototypedsp publish ./tool/

Any static output Cursor writes to disk. Display serves it at a permanent, company-authenticated URL.


Why other options don't work

GitHub Pages: Requires a git repository and, for private repos, GitHub Enterprise Cloud at $21/user/month. Your PM, designer, and VP don't have GitHub accounts. The audience Cursor content was built for can't access it.

Vercel: No file upload. Requires a git project and a deployment pipeline. SAML SSO is a $300/month add-on. Overkill for sharing a Cursor build.

Netlify drop: Drag-and-drop deploy works for public content. For company-restricted sharing, there's no auth option short of Netlify Enterprise.

Display: dsp publish ./dist/ → URL. $49/month flat. Google and Microsoft SSO included.


Pricing

Free — one-time password auth, 50MB, unlimited viewers
Teams ($49/month) — Google + Microsoft SSO, 25GB, custom domain, unlimited viewers

See all pricing →


Publish your first Cursor build free →


Common questions.

Does Display work with Cursor's Agent output specifically?+

Yes. Cursor Agent writes files to your local filesystem just like any other build process. dsp publish works on any directory or file — it doesn't matter which tool generated it.

What if Cursor generates multiple files (React app with assets)?+

Run dsp publish ./dist/ to publish the entire build directory. Display serves index.html at the root URL and resolves all relative asset paths (JS bundles, CSS, images).

Do viewers need a Cursor subscription?+

No. Viewers authenticate with their company Google or Microsoft email. No Cursor account, no Claude account, no Display account required for viewers.

Can I update the artifact after sharing?+

Yes. Republish with the same name: dsp publish ./dist/ --name "dashboard-v2" overwrites the existing artifact. The URL stays the same.

Publish your first artifact in 15 seconds.

Free tier. No credit card. One-time password auth on free, Google + Microsoft SSO on Teams ($49/month flat).