Scroll · Arrows · Space

Platform evaluation · April 2026

Sharing AI Work
— the right way.

Your team is generating real work with AI — prototypes, reports, tools, artifacts. Right now that work either sits in someone's Claude history or gets screen-shared in a meeting. There's a better way. This is the map.

From "look at my screen" to "here's the link."

The shift happening right now

AI is generating real deliverables. The sharing infrastructure hasn't caught up.

Six months ago, AI outputs were interesting experiments. Today they're client prototypes, internal dashboards, and process tools that need to reach stakeholders — privately, reliably, and without an IT ticket.

≤60s
To generate a prototype
Minutes to share it securely
$0
It should cost to fix this

What's actually broken

The requirements are simple. The market wasn't built for them.

🚫 Non-technical access

Most hosting platforms assume a developer is in the loop. Non-technical employees shouldn't need a git repo to share a Claude-generated HTML page.

🔐 Private-by-default

Not everything should be public. Internal work stays internal. External sharing goes to specific people — not just "anyone with the link."

💸 No enterprise wall

Vercel, GitHub Pages, and others lock access control behind enterprise contracts. A 15-person team shouldn't pay $50K/yr to protect a prototype.

The underlying tension: Traditional hosting platforms were built for deploying production apps. You need something built for sharing work-in-progress — with appropriate guardrails, at human speed.

The fork in the road

Infrastructure approach vs. Product approach.

Two genuinely different philosophies. Both can work. They serve different teams.

🏗️ Infrastructure Approach

What: Cloudflare Pages, Netlify, Vercel — platforms built for shipping production web apps, adapted for artifact sharing.

Pros: Maximum control, custom domains, scales to anything, trusted brands.

Cons: Designed for developers. Non-technical daily use requires workarounds. ACL setup has friction. Ongoing updates are clunky.

Right for: Teams with a technical person who can set it up and maintain it. Long-term platform for multiple use cases.

🎯 Product Approach

What: Display.dev, Bolt.new hosting, Lovable publishing — platforms built specifically for "AI generates → human publishes → stakeholder views with auth."

Pros: Zero friction for non-technical users. MCP integration (AI publishes directly). Auth built in. Purpose-fit.

Cons: Newer, smaller companies. Less flexibility. Potential platform dependency. $49–$99/mo vs. $0.

Right for: AI-forward teams who want the workflow to just work. Especially if already using Bolt/Lovable/Claude.

Infrastructure approach — honest comparison

Vercel, Netlify, Cloudflare Pages.

The three platforms everyone considers. Here's where they actually stand for this use case.

Platform Non-Tech Deploy ACL/Private Sharing 10-person cost/mo Verdict
Vercel ❌ No drag-drop
Git or CLI only. Developer required.
❌ $150/mo add-on
Password = +$150/mo on top of Pro. SSO = +$300/mo.
$350+
$200 base + $150 ACL
Wrong fit
Netlify ✅ Netlify Drop
Drag folder → live. No login needed to try.
⚠️ Basic password
Site-wide shared password on Pro. No per-user. SSO = Enterprise only.
$20/mo*
*Verify: may be $20/mo flat (unlimited seats) or $20/user
Strong option
Cloudflare Pages + Zero Trust ⚠️ Drag-drop exists
BUT: full re-upload per change. 1K file limit. IT-oriented dashboard.
✅ Best ACL value
Free for ≤50 users. Email OTP or Google SSO. Domain restriction.
$0
Free for teams under 50. Requires one-time technical setup.
Best value
If you have technical bandwidth

* Netlify pricing has conflicting sources — verify directly at netlify.com/pricing before committing. Could be $20/mo flat unlimited seats or $20/user/mo. Significant difference for teams of 10+.

The pricing wall

The "Vercel needs enterprise for ACL" claim — verdict.

The claim is partially accurate but overstated. Here's the full picture:

  • Preview-only auth: Free on all plans (viewers must have Vercel account)
  • Production password protection: $150/mo add-on on Pro — not Enterprise-only, but expensive
  • SAML SSO for viewers: $300/mo Pro add-on
  • IP allowlisting: Enterprise only — no exceptions
  • Directory sync (SCIM): Enterprise only

Bottom line: not locked to Enterprise, but the add-on costs make Vercel the most expensive path to ACL by a wide margin.

Monthly cost comparison — password protection only

Cloudflare Pages + Zero Trust $0
Netlify Pro (flat) $20
Display.dev Pro $49
Vercel Pro + password add-on (10 users) $350

The product approach — a category that didn't exist 18 months ago

Purpose-built AI artifact platforms.

A wave of tools emerged in 2024–2025 specifically for the "AI generates → human publishes → stakeholder views" workflow. These aren't hosting platforms adapted for AI — they were built for this from day one.

🎯 Display.dev

Gated publishing engine. Drag or MCP → URL with auth in 30 seconds. Viewers use existing Google/Microsoft accounts. Domain restriction. $49/mo flat.

Best fit

⚡ Bolt.new (native hosting)

If you're building in Bolt — publish is one click. Email-domain whitelist for access control on paid plans. Viewers see the app, not the code.

Tool-dependent

💜 Lovable (native publishing)

Business/Enterprise plan: workspace-only or specific-people ACL. Separates "who can edit" from "who can view." Custom domains.

Tool-dependent

Display.dev launched in 2024. Small company — evaluate vendor stability before committing for critical workflows. The category is real; the specific players may consolidate.

Closest to purpose-built for this exact problem

Display.dev — the gated publishing engine.

Two ways to publish

A
MCP integration — Inside Claude Desktop: "publish this to my team" → Display.dev generates a gated URL automatically. No dashboard required.
B
Web upload — Drag an HTML file to display.dev → gated URL in 30 seconds. No install, no CLI, no git.

Access control

  • Viewers authenticate with existing Google or Microsoft work accounts — no new accounts
  • Restrict to company email domain (@builderprime.com)
  • Add specific external emails for client sharing
  • Published artifacts persist independently — survive conversation close

Pricing

  • Free: Magic link auth, limited projects
  • Pro ($49/mo): Unlimited viewers, unlimited publishers, SSO auth, domain restriction, analytics

Why it wins for this use case

  • $49/mo flat vs. Netlify's per-user or Vercel's $200-350/mo for ACL
  • Non-technical team members can publish in 30 seconds with zero training
  • MCP integration = AI tools can publish directly without human in the loop
  • Separates viewing from editing — keep code private while sharing the output
⚠️ Caveat: Small company, founded ~2024. Vet stability before relying on it for client-critical workflows.

Infrastructure approach — the $0 option

Cloudflare Pages + Zero Trust.

Best total-cost option by a huge margin. Real ACL with email-domain restriction. The catch: it's not a self-service platform for non-technical daily use — it needs a technical person to set it up and someone comfortable maintaining it.

✅ What it does well

  • $0/mo for teams under 50 users — Cloudflare Zero Trust free tier is genuinely full-featured
  • Email domain restriction (@builderprime.com only) via Zero Trust Access policy
  • OTP-by-email for external stakeholders (no new accounts needed)
  • Unlimited bandwidth, custom domains, 500 builds/month
  • Cloudflare's CDN edge — fast everywhere

⚠️ Where it falls short

  • Must re-upload entire project for any change — no incremental file updates via drag-drop. Painful for iterative work.
  • 1,000-file drag-drop limit (breaks complex generated apps)
  • Dashboard is enterprise IT-oriented — "Zero Trust," "WARP client," "service tokens" — not a consumer publishing experience
  • OTP friction for viewers — email code every visit without Google IdP configured
  • Pages being folded into Workers — product roadmap uncertainty. All new features land on Workers only.
Recommendation: Set it up once, with Google IdP configured, custom domain attached, and a clear process for uploading new artifacts. Excellent long-term value if you invest the initial setup time.

What this actually looks like in practice

Three flows. Pick the one that fits.

Flow A — Internal sharing
AI artifact → team only

1
Generate artifact (Claude, Bolt, Cursor, etc.) — export as HTML or folder
2
Upload to Display.dev (drag) or say "publish this to my team" in Claude Desktop (MCP)
3
URL generated, automatically gated to @builderprime.com
4
Team member clicks link → signs in with Google Workspace → views. Anyone else: denied.

Zero external setup

Flow B — Client/stakeholder sharing
Selective external access

1
Generate and upload to Display.dev or Cloudflare Pages + Zero Trust
2
Add client's email address to the allow-list (or share password via Netlify Pro)
3
Client clicks link → authenticates with Google/Microsoft or enters OTP → views prototype
4
When project ends: revoke access in one click

Per-person control

Flow C — Non-technical self-serve
Anyone on the team can publish

1
Export artifact as HTML/ZIP from Claude (copy artifact HTML to a file, or use Bolt/Lovable)
2
Go to display.dev → drag file → URL in 30 seconds
3
URL automatically gated per org policy — no per-upload configuration needed
4
Share link in Slack or email. Done.

No training required

Full cost comparison

What 10 and 20 people actually pay.

Platform 10-person / mo 20-person / mo ACL included? Non-technical?
Cloudflare Pages + Zero Trust $0 $0 ✅ Email SSO, domain restrict ⚠️ Setup friction
Netlify Pro (flat $20/mo)* $20 $20 ⚠️ Basic password only ✅ Drag-drop
Display.dev Pro $49 $49 ✅ Google/MS SSO, domain restrict ✅ Purpose-built
Netlify Pro ($20/user/mo)* $200 $400 ⚠️ Basic password only ✅ Drag-drop
Vercel Pro + ACL add-on $350 $550 ⚠️ Password only ($150 add-on) ❌ No drag-drop
Bolt.new / Lovable (native hosting) Bundled Bundled ✅ Email domain whitelist ✅ One click

* Netlify pricing is actively disputed in sources — verify directly at netlify.com/pricing. Both $20/mo flat and $20/user/mo have been cited for the Pro plan.

How to choose

One question to start: what AI tools are you actually using?

"We build in Bolt.new or Lovable"

Use their native hosting. It's already there, ACL is built-in, and adding a separate platform creates unnecessary complexity. Bolt's email-domain whitelist on Teams plan covers the internal/external sharing need.

→ Stay native. No separate platform needed.

"We use Claude, Cursor, or mixed tools"

You need a platform-agnostic solution. Display.dev at $49/mo flat covers the full workflow with MCP integration and Google/Microsoft SSO. Best match for an AI-forward team that doesn't want to think about infrastructure.

→ Display.dev Pro.

"We have technical bandwidth and want maximum control"

Cloudflare Pages + Zero Trust at $0/mo. Invest 2-4 hours one-time to configure with Google IdP, custom domain, and upload process documentation. Then it runs itself for years.

→ Cloudflare Pages + Zero Trust.

Open questions to resolve: What AI tool(s) is the team primarily using? How "non-technical" does the publishing flow need to be — can someone manage a Cloudflare dashboard, or does it need to be drag-and-forget? How many external stakeholders will be authenticated users (50-user free limit on Cloudflare Zero Trust)?

Appendix — additional context

Reference & Auxiliary Options

Tiiny.host — quick ad-hoc sharing (auxiliary)

Simplest possible "upload and share" tool. Not an org-level platform — useful for individual quick shares.

  • Flow: Drag a ZIP/HTML file → choose subdomain → live in 10 seconds. Supports 100+ file types.
  • ACL: Single shared password on Solo tier ($13/mo). No per-user control.
  • Pricing: Free (1 site, 3MB), Solo $13/mo (5 sites, 75MB, password), Pro $31/mo (15 sites, 10GB, team members)
  • New (April 2026): AI Agent Publish Skill — compatible with Claude Code, Codex, Cursor, Copilot, Gemini CLI, 20+ agent platforms
  • Limits: File size caps make it unsuitable for complex generated apps. No domain restriction, no per-user ACL.
  • Best for: Non-critical quick shares, PDFs, simple HTML pages, individual use.
Claude native sharing — limitations worth knowing

Claude's built-in artifact sharing has a notable gap:

  • Free/Pro/Max plans: "Publish" creates a public URL — anyone with the link can view. No ACL, no password.
  • Team/Enterprise plans: "Share" restricts to org members only (must be logged in). Cannot publish externally.
  • No middle ground natively — there's no way to share with specific external people or restrict by email domain within Claude itself.
  • Sharing an artifact also exposes conversation attachments — potential data leak risk.

This gap is exactly why Display.dev and similar platforms emerged.

Netlify — the drag-and-drop infrastructure option

Best traditional hosting UX for non-technical users. Worth revisiting once pricing is confirmed.

  • Netlify Drop: Drag a folder to the browser → live URL in seconds. The smoothest drag-and-drop of any traditional platform.
  • Password protection: Pro plan — site-wide shared password (not per-user). Simple toggle in dashboard.
  • Pricing dispute: Some sources say $20/mo flat (unlimited seats). Others say $20/user/mo. Verify directly before committing — for a 10-person team, the difference is $180/mo.
  • If flat $20/mo: Excellent value — competitive with Display.dev at $49, with better deployment UX than Cloudflare for non-technical users.
  • SSO/email domain restriction: Enterprise only. Shared password is the ceiling at Pro.
Cloudflare gotchas — what the $0 price doesn't tell you
  • Re-upload everything on every change: Direct upload has no incremental file replacement. Every update = full re-upload of the project.
  • 1,000-file limit: Hard cap for drag-drop uploads. Complex generated apps with many assets will hit this.
  • Pages → Workers migration: Cloudflare is folding Pages into Workers. All new features land on Workers. Pages still works but product direction is uncertain. Consider this a 2–3 year commitment risk.
  • OTP friction: Without Google IdP configured, viewers get an email OTP code every visit. This creates enough friction that people complain. Worth the one-time investment to configure Google IdP properly.
  • 50-user free limit: The Zero Trust free tier is 50 users. If you're adding external stakeholders (clients, partners) to the authenticated user count, this fills up faster than you'd expect.
HuggingFace Spaces / Streamlit / Gradio — not the right fit here

Only relevant for very specific use cases:

  • HuggingFace Spaces: Great for ML model demos. Git-based deploy, requires technical knowledge. Not designed for general AI artifact sharing.
  • Streamlit: Python-to-web-app framework. Best for data dashboards. Requires Python and technical setup.
  • Gradio: Python ML demo library. Creates temporary URLs for quick sharing (72h) or permanent via HuggingFace. Requires Python.
  • Relevance for Builder Prime: Only if the team is specifically building ML/data tools in Python. Not a match for general AI artifact workflow.

Research conducted April 2026. Pricing and features may change. Verify all pricing at official vendor sites before committing. Key sources: official pricing pages, Cloudflare docs, community forums, Gartner/G2 reviews.