A Display.dev alternative that starts with a tool call.

Display.dev wraps HTML in company auth. Stacktree wraps HTML in an MCP tool call — so the agent publishes directly, the URL replaces in place across iterations, and a developer can try it without spinning up a workspace.

Get started free

What is a Display.dev alternative?

Stacktree. Both products solve the "agent emitted HTML, now what?" problem with a private URL. Display.dev is workspace- and SSO-first; Stacktree is primitive-first — anonymous publishes, MCP tool calls, update_site for stable URLs across revisions, and three independent gating layers (unguessable URL, password, email-domain gate) so you can match the security to the artifact instead of the org.

Where they agree

HTML emitted by agents needs a home that isn't a screenshot in Slack.
Private-by-default beats public-by-default for anything internal.
Per-seat pricing is the wrong shape for agent-scale workloads.

Where they differ

The product shape is the biggest divergence. Display.dev is "gated publishing as a managed workspace": you create an account, you invite teammates, you wire SSO, agents publish on behalf of the workspace, viewers authenticate via your IdP.

Stacktree is "gated publishing as a primitive": the first publish takes one MCP tool call with no account at all. When you do sign up, what unlocks isn't a workspace — it's longer expiries, replace-in-place across sessions, custom domains, and the ability to layer password + email-domain gates per link.

Three things Stacktree does that Display.dev doesn't

Replace-in-place via MCP. update_site is a first-class verb, designed for the case where an agent revises the same artifact 12× in a session. The URL stays put; the content changes underneath it.
Anonymous first publish. The 60-second test path is "install MCP, publish, send link to coworker" — no workspace, no SSO, no invite chain. You upgrade when you outgrow the anonymous 24-hour expiry, not before.
End-to-end encryption. A toggle on upload — AES-GCM in the browser, key in the URL fragment, ciphertext on the server. Useful when the HTML embeds real customer data and the answer to "could Stacktree read this?" needs to be no.

When Display.dev is still the right pick

If your primary requirement is "every viewer must be in our IdP," and you want every artifact across the org auto-gated to your SSO without per-link configuration, Display.dev's workspace model is a tighter fit today. Stacktree's per-link gates cover ~90% of the practical cases ("only my team," "only @yourco.com," "only people with the password"), but they're configured per artifact rather than once per workspace.

Stacktree vs. Display.dev

Criterion	Display.dev	Stacktree
Anonymous first publish	No: workspace + account required.	Yes: 24-hour link, no account.
MCP server	Roadmap / partial.	Yes: seven verbs, stdio + HTTP.
Replace-in-place URL	Limited: workspace-scoped artifacts.	First-class: update_site verb.
SSO (SAML/OIDC)	Yes: workspace-level.	Per-link email-domain gate; full SSO on roadmap.
Email-domain gate	Via workspace SSO only.	Per-link, magic-link verified.
Password gate	Limited.	Yes: toggle on any link.
End-to-end encryption	No.	Yes: AES-GCM, key in URL fragment.
Custom domain	Yes (paid).	Yes (Pro, Cloudflare for SaaS).
Pricing shape	Workspace flat tier.	Workspace flat tier.

FAQ

Frequent questions

How is Stacktree different from Display.dev? +

Both put a private URL in front of agent-emitted HTML. Display.dev focuses on company SSO and team workspaces. Stacktree focuses on being an agent primitive: anonymous first publish, MCP tool call, update_site for stable URLs across iterations, and three gating layers (unguessable URL → password → email-domain gate) that scale from solo to team without a workspace setup step.

Does Stacktree do SSO? +

Email-domain gating with magic-link verification covers the common case ("only people with @yourco.com can see this"). For SAML/OIDC SSO in front of every site on a workspace, that's on the roadmap; today the verification is per-link.

Is there a free tier on Stacktree? +

Yes — including a truly anonymous publish that requires no account at all. Display.dev gates publishing behind a signed-up workspace from the start.

Can agents publish without me approving each upload? +

Yes. The MCP tool call goes straight to publish. If you want to spot-check, list_sites lets the agent (or a human) review what's been published and delete or expire any of it.

Do I need a company email to use Stacktree? +

No. Sign in with any email (or skip signing in altogether for 24-hour anonymous publishes). Pro plans are billed per workspace, not per seat.

How does pricing compare? +

Both have free tiers and a flat (non-per-seat) Pro tier. The headline price points are in the same ballpark; the more important difference is that Stacktree's free tier doesn't require a workspace, so a developer can prove value in an afternoon before bringing the team.

Keep reading

Related guides

References

Sources and further reading

Try the primitive in 60 seconds.

No workspace setup. No SSO wiring. Install the MCP server, publish, share.