--- url: /stacktree-alternative title: Stacktree Alternative with Company SSO – display.dev priority: P0 keyword: stacktree alternative secondary_keywords: stacktree vs display.dev, stacktree alternative with SSO, private HTML hosting with company auth, agent publishing behind company SSO funnel_stage: Decision schema: FAQPage, SoftwareApplication description: "Stacktree publishes agent HTML behind per-link gates. display.dev publishes it behind your company's Google or Microsoft SSO, with org ownership, inline comments your agent reads back, and an audit trail." --- # The Stacktree alternative with company SSO and an org that owns the work Stacktree gives one agent-made HTML page an unguessable URL and a per-link gate. display.dev puts that same page behind your company's Google or Microsoft login, owned by your organization, with inline comments your agent reads back and a full audit trail. Both keep the same URL across every update. [Try display.dev free →](https://app.display.dev) · [See pricing](/pricing) --- ## display.dev vs. Stacktree | | display.dev | Stacktree | | ------------------------------------------ | -------------------------------------------------------------------- | ------------------------------------- | | **Company SSO (Google + Microsoft)** | ✅ Pro, €49/mo | ❌ Not in the hosted product (roadmap) | | **Organization ownership + roles** | ✅ Members, verified domains, roles | ❌ Anonymous token or single account | | **Inline comments the agent reads back** | ✅ via MCP, then republish + resolve | Feedback toolbar only | | **Audit log + per-version attribution** | ✅ 90 days (Pro), 365 days (Enterprise) | ❌ | | **MCP server** | ✅ In production: Claude Code, Claude Desktop, Cursor, Codex, ChatGPT | ✅ | | **Same URL on every update** | ✅ Versioned republish | ✅ `update_site` | | **Unlimited viewers, no per-seat fee** | ✅ Every tier | ✅ No per-seat fee | | Anonymous no-account first publish | Local CLI claimable link | ✅ 24-hour link, remote | | Per-link password, expiry, burn-after-read | ❌ | ✅ | | Optional end-to-end encryption | ❌ | ✅ AES-GCM, key in the URL fragment | | Self-host license | ❌ | ✅ $999 | | Real, named customers | ✅ Indigo Engineering | ❌ None public | | Flat pricing | €15 / €49 / from €499 | $8 / $19 / $999 self-host | Pricing and feature facts for Stacktree are from [stacktr.ee](https://stacktr.ee/pricing) and its docs, verified July 2026. Where they lead, we say so below. --- ## Where Stacktree is genuinely good Stacktree is not a page builder with MCP bolted on. It read the same thesis we did and built a crisp, agent-native product. Four things it does well, and where display.dev is different: **Anonymous first publish.** A developer can call `publish_html` mid-session with no account and get a URL that lives for 24 hours. That is the lowest-friction way to prove the workflow, and it is a real activation advantage. display.dev has a no-account path too, but it runs through the local CLI (`dsp mcp` with no login returns a public preview URL and a one-shot claim link), not the remote endpoint. **Per-link gates.** Password, expiry, burn-after-read, revocable share tokens, and optional end-to-end encryption cover a lot of solo and small-team jobs without provisioning anything. display.dev does not have shared-password links, per-link expiry, burn-after-read, or E2E encryption. If a single-use secret link is the whole job, Stacktree fits it directly. **A tiny, legible MCP surface.** `publish_html`, `update_site`, `set_expiry`, `set_password`, `set_email_gate`, `list_sites`, `delete_site`. One job each. Clean. **A self-host license.** For $999, Stacktree sells a source-available build that deploys into your own Cloudflare account. If your requirement is "the vendor never holds the bytes," that is a direct answer. display.dev is hosted only today; our compliance answer is Enterprise (SAML, a signed DPA, 365-day audit retention), not a source license. If your job is a single throwaway link with a password and a timer, Stacktree is a good, honest tool. The rest of this page is about the job it does not cover. --- ## Where display.dev wins: the company, not the link Stacktree gates a link. display.dev gives the work an owner. **Company SSO, not a per-link check.** On display.dev, an artifact can be visible to everyone at your company behind Google or Microsoft login. A viewer clicks the URL, signs in once with the account they already use for email, and sees the page. No password to circulate, no per-link setup. Stacktree's hosted product does not have company-wide SSO; its own docs state it is not enterprise SSO yet. An email-domain link sent per site is not central identity: no group policy, no session revocation, no audit-grade record of who opened what. **The organization owns the artifact.** Members, verified email domains, and roles. When the person who published leaves, the work stays with the org, not with an anonymous token or a personal account. **Inline comments are the agent's reverse channel.** A teammate leaves a comment pinned to the artifact. Your agent reads it via MCP, fetches the current version, republishes to the same URL with the `short_id` and `base_version`, and resolves the thread. That is a maintenance loop, not a static page. Stacktree exposes a feedback toolbar toggle; its docs do not describe an anchored-thread model or a tool for the agent to read comments back. **An audit trail with real attribution.** Every version and every comment is attributed to the agent and the human it acted for. Pro keeps 90 days of audit logs; Enterprise keeps 365. Stacktree records hashed view logs for 30 days and has no per-version author trail in the hosted product. **Customers who will say their name.** Indigo Engineering's 7-person team runs its agent output through display.dev. Stacktree's public surface names its founder but no customers, no SOC 2, and no DPA. --- ## Correcting Stacktree's comparison page: our MCP server is in production Stacktree's `/display-dev-alternative` page lists our MCP server as "Roadmap / partial." That is out of date. display.dev's MCP server is in production and exposes seven tools: `publish`, `share`, `rename`, `find`, `get`, `export`, and `delete`. It works today across every major MCP host: - [Claude Code](/docs/mcp-claude-code) - [Claude Desktop](/docs/mcp-claude-desktop) - [Cursor](/docs/mcp-cursor) - [Codex](/docs/mcp-codex) - [ChatGPT](/docs/mcp-chatgpt) Connect it as a custom connector with an OAuth sign-in, point a host at the remote endpoint with an API key, or run it as a local subprocess. All three produce identical artifacts. Details in the [MCP server docs](/docs/mcp-server). Publishing, updating to the same URL, changing visibility, searching your org, and reading source back are all one tool call each. --- ## Workflow: publish, comment, update **display.dev, from any MCP host:** > "Publish this competitive analysis to my team." Your agent calls `publish` and returns a URL gated to your company. A teammate opens it with their Google or Microsoft account, leaves an inline comment, and your agent reads it back, republishes to the same URL, and resolves the thread. Every step is attributed and logged. **display.dev, from the terminal:** ```bash dsp publish ./analysis.html ``` ⏱ A URL in about 15 seconds. Company SSO on Pro at €49/month flat, unlimited viewers. --- ## When to use Stacktree You want an anonymous 24-hour link mid-session, a password or single-use gate on one page, or a self-hosted deploy into your own Cloudflare account, and you do not need central identity, org ownership, or a comment-and-update loop. ## When to use display.dev You want agent output behind your company's Google or Microsoft SSO, owned by your organization with roles and verified domains. You want teammates to comment on the page and your agent to read those comments back and update the same URL. You want a per-version audit trail. You want unlimited viewers with no per-seat fee, and you want to point at real customers when you defend the choice. --- ## Pricing **Free (€0)** – 10 gated artifacts, unlimited public artifacts, CLI + MCP + web, one-time password login for viewers. **Solo (€15/month)** – unlimited gated artifacts, 1GB storage, 10 versions per artifact. **Pro (€49/month)** – Google + Microsoft SSO, private artifacts, 25GB storage, 50 versions, 90-day audit logs. **Enterprise (from €499/month)** – SAML, 365-day audit retention, a signed DPA, SLA, custom storage. No per-seat fees at any tier. Unlimited viewers everywhere. [See all pricing →](/pricing) --- ## Try display.dev free - **Company SSO from €49/month flat** – not a per-link password, real identity - Org ownership, inline comments your agent reads back, and a per-version audit trail - First artifact in about 15 seconds · No credit card [Get started free →](https://app.display.dev) · [What is gated publishing?](/blog/what-is-gated-publishing) --- ## FAQ **Is display.dev a Stacktree alternative?** Yes, for the same core job: an agent writes HTML, you need a private URL, and updates should land on the same link. The difference is the gate. Stacktree gates each link with a password, an email-domain check, or expiry. display.dev gates the artifact with your company's Google or Microsoft SSO and gives your organization ownership, roles, comments, and an audit trail. **Does Stacktree have company-wide SSO?** Not in the hosted product. Stacktree's own documentation states it is not enterprise SSO yet; its per-link email-domain check is a per-site gate, not central identity. display.dev puts Google and Microsoft SSO in front of every artifact on the Pro plan at €49/month, and adds SAML on Enterprise. **Does display.dev support anonymous no-account publishing like Stacktree?** Partly. Run the local CLI without signing in (`dsp mcp` with no login) and the publish tool returns a public preview URL plus a one-shot claim link, so you can prove the workflow first and claim the artifact into an org later. Stacktree's anonymous path runs over its remote endpoint and produces a 24-hour link, which is lower friction for a one-off first publish. **Can my agent update an artifact in place on display.dev?** Yes. Publishing again with the artifact's `short_id` and its current `base_version` replaces the content at the same URL and keeps the version history. It maps to the same agent-iteration loop as Stacktree's `update_site`. **Does display.dev do password links, expiry, or burn-after-read?** No. display.dev does not have shared-password links, per-link expiry, burn-after-read, or end-to-end encryption. Access is identity-based instead: anyone with the link, specific invited email addresses, or everyone at your company behind SSO. If a single-use secret link is the requirement, Stacktree covers it directly. **Can I self-host display.dev?** Not today. display.dev is hosted only. For teams that need a stronger compliance posture, Enterprise adds SAML, a signed DPA, and 365-day audit retention. Stacktree sells a $999 source-available self-host license if running it in your own Cloudflare account is a hard requirement.