Share a live page with the right people, and take it back.
Password it, set an expiry, name the guest list, watch who opens it, and revoke it the instant you need to. Publish whatever your AI builds to a stable link you own.
Unlike a public share link, a Poured page reaches the exact people who should see it: tracked, revocable, and published straight from your AI.
Those pages can hold data and sign people in, so the same passwords, expiry, and revoke cover the small apps you build on them.
How it works
Build it with your AI
Ask Claude, ChatGPT, Codex, or Claude Code to make a page, or a small app. Prefer to do it yourself? Paste or upload a file.
Publish to Poured
Add the connector once and “publish this, password it” is a sentence in the chat, or upload directly. A stable link on a real domain, served exactly as you built it.
Share it, take it back
Send it to the right people, see who's opened it, and password, expire, or revoke from one dashboard.
Publish straight from your AI
Poured ships one standard connector (MCP). Add it to Claude Cowork in a minute (Claude Code, Codex, and ChatGPT use the same one), and “share this as a page, password-protect it” becomes a single sentence in the conversation. Your AI publishes and hands you the link.
What people build
From a small app that reads and writes data behind a sign-in, to a page you just want the right people to see. All governed the same way: shared with exactly the right people, and revocable.
Weekly shift planner
Lay out the week; the team signs in and grabs the shifts they want, and the grid fills in live.
New-project proposals
Collect pitches from across the org, each tied to who sent it, then review and greenlight.
Event & training sign-ups
An RSVP sheet where people sign in to add themselves, and only you can read the list.
Client status dashboard
A private, password-gated view for one client, revoked the day the engagement ends.
Share a doc or PRD
The spec, brief, or writeup you just made with your AI, on a real link, sent to the right people and pulled back when it goes stale.
Show what your project does
A simple one-pager for a tool or program: what it does, how to run it. Password it for a client, or take it down when it moves on.
The rest of the toolkit
Edit in place
Change a published page right in the dashboard, visual or source. Every save is a new version to roll back to.
Analytics
Who opened it, when, from where, on what. Counted server-side, with no tracking cookie on the served page.
QR code
Every page gets one, ready to drop into a slide, a poster, or a table tent.
Governed embed
Drop a page into another site as an iframe. Disable, expire, or password it and the embed follows.
Named share links
Give different people their own revocable link, or gate one to a group, without touching the page.
Your own URL
Pick a custom slug at publish time, so the link reads the way you want.
You stay in control
Passwords
Protect any page with a password. Change it and outstanding sessions expire.
Versions & rollback
Every publish is an immutable version. Roll back with one click; links never break.
Expiry & instant revoke
Set a page to expire, or disable it, and the link stops working immediately.
Audit trail
On request, a full log of every change you made: access flips, new versions, takedowns.
Hosting and privacy
- EU-hosted on Google Cloud (europe-west3).
- Your pages are served from their own domain, isolated from the application.
- No tracking cookies on this site. Page views are counted server-side.
- A report link on every published page routes to a review queue.
Questions
What files work?
Any single, self-contained HTML file up to 10 MB, with images embedded as data URIs and CSS and JavaScript inlined. AI assistants produce pages and small apps like this by default.
Who can see my page?
You choose per page: anyone with the link, password-protected, limited to a named guest list or group, or disabled. The link is an unguessable URL, so a link page is private unless you share it.
Can a page store data, or be an app?
Yes. A page can read and write data through a built-in store, update live for everyone viewing, and require sign-in to write, with no database or backend to set up. You choose who can read and who can write from a few presets, and a plain page stays static until you add data.
How do people sign in to an app, and what do they share?
Writing to an app takes a one-time sign-in and consent. People appear under a handle they choose, never their real name or email, and each app only ever sees a per-app pseudonym. Everything they add stays tied to that handle, and they can stop and leave any time.
What does it cost?
Poured is free during the beta.
How do I connect my AI?
Add Poured as a custom connector using the connector URL, then sign in. Claude Cowork and Claude Code have step-by-step guides on the Connect page, and the same standard connector works in other MCP clients like Codex and ChatGPT.
Can I take a page down?
Yes, instantly. Disable a page and its link stops working immediately. You can also roll back to any earlier version, or delete it.
Where is my data hosted?
In the EU, on Google Cloud (europe-west3). Served pages run on their own domain, isolated from the application.