Skip to content

What Display.dev does not do

The jobs Display.dev does not do, what is planned, and which tool to use instead.

On this page

Display.dev publishes HTML and Markdown documents for a company and its agents. It does not run server-side code, build sites or replace an app platform. It has no password links, expiring links, burn-after-read links or end-to-end encryption. Access follows each reader's sign-in. Display.dev runs only as a hosted service. Custom domains, self-serve SAML, folders and search across all artifacts are planned. Invited outside guests can view artifacts. They cannot comment yet.

For plan limits such as storage, upload size and retained versions, see Plans and limits.

Summary

Display.dev does notStatusUse instead
Run server-side code or a databaseNot offeredA deploy platform such as Vercel, Netlify or Cloudflare
Host a public site with a build pipelineNot offeredNetlify, Cloudflare Pages or GitHub Pages
Gate a link with a passwordNot offeredCompany or Private visibility
Expire a link after a timeNot offeredRemove the invited person, change the audience, or delete the artifact
Delete a link after one viewNot offeredA tool with burn-after-read links
Encrypt end to endNot offeredA tool with end-to-end encryption
Run on your own serversNot offeredA self-hosted tool
Add a custom domainEnterprise, by contractA deploy platform
Connect SAML on a self-serve planPlannedGoogle or Microsoft sign-in on Pro
Let outside guests commentPlannedAdd the reviewer as an organization member, or collect comments by email
Organize artifacts in foldersPlannedClear artifact names, and the list and search tools
Search the text inside all artifactsPlannedSearch artifact names. Search the text of one artifact with dsp search <text> --in <shortId>
Publish a directory or a ZIP filePlannedPublish one self-contained HTML or Markdown file
Import Word, PDF, PowerPoint or Excel filesPlannedConvert the file to HTML or Markdown first
Edit together with live cursorsNot offeredGoogle Docs or Notion
Run an approval workflowNot offeredYour ticket or review tool

Server-side code and public sites

Display.dev serves the file that you publish. Scripts in the file run in the reader's browser. Display.dev does not run your code on a server, store your app data or build a project. A public artifact is one page at a Display.dev URL. It is not a site host.

Use a deploy platform for an application or a marketing site. Use Display.dev for the report, plan, specification or prototype that the agent writes.

Passwords, expiry and end-to-end encryption

Display.dev controls access by identity. A reader signs in with Google, Microsoft or a one-time password sent to an invited email address. There is no shared password for a link. There is no timer that expires a link. There is no link that deletes itself after one view. Display.dev does not encrypt content end to end, so Display.dev can serve the content to a reader who has access.

To stop sharing with one person, remove that person from the artifact. To stop sharing with everyone outside the audience, change the audience. To end all access, delete the artifact. See Sharing and access.

Self-hosting

Display.dev runs only as a hosted service. There is no self-hosted license. To learn where Display.dev stores data and how it protects it, read the security page.

Custom domains and SAML

Artifacts open at <org>.dsp.so. Custom domains and SAML single sign-on are on Enterprise, by contract. Self-serve SAML is planned. Pro includes Google and Microsoft sign-in without SAML. For Enterprise contract terms, see Plans and limits.

Outside guests cannot comment yet

You can invite a person outside your organization by email. They enter a one-time password and view the artifact. They cannot comment or edit. Comments from outside guests are planned. Until then, add the reviewer to the organization as a member, or collect their feedback outside Display.dev.

On Pro and Enterprise, an Owner can restrict Public artifacts or outside sharing for the whole organization. While outside sharing is restricted, invited guests cannot open artifacts. See Organization artifact access.

Folders, search, directories and file imports

These features are planned. They are not available today:

  • Folders to organize artifacts.
  • Full-text search across all artifacts. Today, search finds artifact names, and dsp search <text> --in <shortId> finds text inside one artifact.
  • Publishing a directory or a ZIP file. Today, publish one self-contained HTML or Markdown file.
  • Imports of Word, PDF, PowerPoint and Excel files.

The roadmap can change. Ask support@display.dev for the current status.

Editing and approvals

An organization member can change a published page in the browser. Each save creates the next version at the same URL. One person edits at a time. Display.dev does not show live cursors for two people who edit at the same time. It has no approval step that blocks publishing. Comments and version history record the review.

FAQ

Does Display.dev host websites?

No. Display.dev publishes single HTML and Markdown artifacts at their own URLs. It does not build projects, run server code or serve a site from a custom domain.

Can I put a password on an artifact?

No. Choose Company or Private visibility. Invited people outside your organization sign in with a one-time password sent to their email.

Can I stop people outside my company from opening artifacts?

Yes, on Pro and Enterprise. An Owner can restrict Public artifacts or outside sharing for the whole organization. Organization members keep their normal access. See Organization artifact access.

Can people outside my company comment?

Not yet. They can view an artifact after an invitation. Comments from outside guests are planned.

Can I run Display.dev on my own servers?

No. Display.dev runs only as a hosted service.

Was this page helpful?