The ShipPage alternative that is private by default.

Why people look for a ShipPage alternative

• Public by default. ShipPage returns a public URL; privacy means adding a password afterward. If the artifact is an internal report, a client deliverable, or anything with data in it, you may want the opposite default: unreadable unless you hold the link.
• No company-email gate. A shared password is the only documented gate. When the audience is "anyone at the client", verifying a work address by magic link is the gate that fits, and it still asks the viewer for no account.
• The URL is not yours. Custom domains are listed under a Pro tier marked coming soon with pricing TBD. A deliverable sent from a third-party hostname reads as a third-party deliverable. Stacktree maps your domain today, one on Solo and ten on Studio.
• Nowhere for the client to reply. ShipPage documents no on-page feedback, so a review round goes back to email threads and screenshots rather than notes anchored to the thing being reviewed.

Where ShipPage genuinely wins

It deserves the credit: ShipPage's onboarding is about as frictionless as agent publishing gets. The first POST /v1/publish auto-registers the agent and returns an API key, no signup, no configuration. It ships an MCP server and an OpenClaw skill, works with Claude Code, Claude Desktop, and Cursor, and responds fast on Cloudflare infrastructure. If you want a throwaway public page from an agent in one call with zero ceremony, it does exactly that.

Where Stacktree differs

• Private by default. Every URL is unguessable and acts as the credential. Add a passcode, a magic-link email-domain gate, or end-to-end encryption (the server stores only ciphertext) per site.
• No account for the viewer, ever. Gated or not, the person you send the link to opens it in a browser. There is no Stacktree login, no seat, and nothing to install, so a client or a contractor is never blocked by your vendor choice.
• Custom domains now. One on Solo at $19 a month, ten on Studio at $79, live through Cloudflare for SaaS rather than a roadmap item. Paid pages carry no Stacktree badge either, so the page names nobody but you.
• Replace-in-place. update_site swaps content under the same URL, so the link shared yesterday shows today's version. Thirty iterations in a session, one URL.
• The client answers on the page. Viewers react and leave notes anchored to the exact element, with no account. The agent reads them back with list_feedback, ships the fix to the same URL, and resolves them.
• Agents can pay for themselves. A headless agent provisions a persistent identity for $1 over x402 (live on Base mainnet) and buys unlocks a-la-carte: $5 to make a page permanent, $5 per 30 days for a custom domain. No equivalent is documented on ShipPage.
• OAuth and a dashboard. Hosted MCP clients connect over OAuth 2.1; humans manage sites, keys, and gates in a dashboard.

What the two free tiers are actually for

Neither free tier is a place to keep client work, and it is worth being straight about that. ShipPage gives you 20 publishes a month at 500KB each, expiring after 14 days, with permanent retention parked in a Pro tier priced TBD. Stacktree gives you 3 pages in total, each expiring after 7 days, carrying a small Made with Stacktree footer, with no passcode available. Both are there to prove the loop works before anyone pays.

The difference shows up on the other side of the paywall. Stacktree's is a published price you can act on today: Solo at $19 a month for permanent pages, a passcode or company-email gate on all of them, one custom domain and no badge, and Studio at $79 for ten domains and the engagement view. ShipPage's permanent tier is still coming soon. See pricing for the full ladder.

Who should pick which

Pick ShipPage for instant, zero-setup public pages from an agent, where the page is meant to be public and two-week retention is fine.

Pick Stacktree when the artifact is private, goes to a client who should not have to log in anywhere, needs your domain on it, or belongs to an autonomous agent that pays its own way. Same one-call publish, opposite defaults.