Put the pages your AI builds in front of your team

PutPage is where vibe-coded prototypes, reports, and dashboards go live — one command from your terminal, or straight from your agent. Shared with exactly the people you choose.

Request a workspace → Try the demo now — no waiting

Free while in beta · Requests reviewed within a day

$ pp ./q2-report.html
✔ Uploaded q2-report.html  (version 3)
● Live at https://acme.putpage.com/p/joe/q2-report
  Access: workspace members only

AI can build a working page in minutes. Sharing it is still broken.

Artifacts live in someone else's chat

Claude artifacts and ChatGPT canvases are great for drafting, but the output stays buried in a conversation thread, on the vendor's turf — not in your team's space.

Screenshots kill the demo

Pasting a PNG into Slack throws away everything interactive.

localhost dies with your laptop lid

"Check out :3000" doesn't survive the afternoon.

Public deploys are wrong for internal work

Vercel/Netlify links are for shipping products, not sharing drafts with your team's access model.

How it works

  1. Install

    curl -fsSL https://acme.putpage.com/install.sh | sh

    The install script comes from your own workspace domain — the CLI points at your workspace out of the box.

  2. Publish

    pp ./page.html

    A single file or a whole directory bundle. Every publish automatically becomes a new version.

  3. Share

    Workspace members can view and comment immediately. Share to individuals by email, send a magic link to outside guests, or make it public — explicitly.

Built for agents, not just humans

Connect PutPage over MCP — Claude Code, Cursor, or any MCP client — and your agent publishes its own work. Ask Claude to build a dashboard; it ends the turn with a live URL.

The pp CLI ships with an embedded skill your agent can read to learn the whole workflow on its own.

> Build a churn dashboard from this CSV and put it in front of the growth team.

  … working …

  Done — published to https://acme.putpage.com/p/agent/churn-dashboard
  (version 1, access: workspace members)

NEUTRAL GROUND

Your AI's output shouldn't belong to your AI vendor

"You essentially pay for intelligence twice — once with money, and again with something even more valuable: the proprietary knowledge you must reveal to make that intelligence useful." "The Reverse Information Paradox", snscratchpad.com

Model-agnostic by design

Publish from Claude Code, Cursor, Codex, or any MCP client. Switch models tomorrow; your page library stays.

Your workspace, not a chat log

Pages are versioned, organized, access-controlled, and searchable in a space your team owns.

Own the actual bytes

Bring your own S3/R2 bucket and serve from your own domain. Your content lives on infrastructure you control.

Everything a page needs after it's built

Versions on every publish

Run pp again and it's v4; roll back instantly when the demo breaks.

Access control that fits your org

Workspace-only by default; share to individuals by email; magic links for outside guests; public only when you choose.

Comments where the work is

Feedback docks right on the page itself, not in a lost chat thread.

Collections & subscriptions

Group sprint demos or weekly reports; teammates subscribe to updates.

Slack-native

Shares and comments arrive as Slack DMs; names and avatars come from your Slack workspace.

Custom domains

Serve pages from pages.yourco.com with automatic TLS.

Bring your own storage

Page content stored in your own S3-compatible bucket.

Live updates

Republish and every open tab refreshes in place.

Private by default. Auditable always.

Pricing

During beta, every workspace gets every feature — free.

Free

$0

For small teams getting started. Core publishing, versions, access control, comments, Slack notifications.

Request a workspace

Team

Coming soon

Higher quotas, priority support, custom domains, bring-your-own storage.

Enterprise

Coming soon

SSO/OIDC, audit log, forensic watermarking, dedicated support, compliance commitments.

Tier boundaries aren't final — everything is included while in beta.

FAQ

What can I publish?

A single HTML file or a whole folder of static assets. If it renders in a browser, pp can put it up.

Why not just keep using Claude artifacts?

Artifacts are great for drafting. But the output lives inside a chat thread, on the vendor's infrastructure. PutPage gives it a home your team owns — versioned, access-controlled, on your own domain and storage — and your agent can publish there directly via MCP.

Who can see my pages?

Workspace members by default; email shares and magic links for guests; public only by explicit choice.

How do agents publish?

Via MCP (Claude Code, Cursor, any MCP client) or the pp CLI, which ships an embedded skill agents can read.

Can I try it before requesting a workspace?

Yes. Join the shared demo workspace with just your email — publish a page, try the CLI and MCP, poke around. It's a shared space: everything in it is visible to other visitors and wiped periodically.

How do I get a workspace?

Fill in a short request; we review and email you a link to your new workspace, usually within a day. Reviews keep workspace URLs with their rightful owners and the beta high-signal.

Is this production hosting like Vercel?

No, deliberately: PutPage is for putting work in front of people, not serving production traffic.

What happens after beta?

The free tier stays. Clear notice before any paid tier lands.

Give your AI's work a home

Request a workspace →

…or try the demo workspace first

Free while in beta.