For teams · Self-hosted

Bring your ideas to life.

Publish HTML pages, AI prototypes, and small tools on your own infrastructure. PageGo supports web, CLI, and MCP publishing with version management and access controls for reviews and client delivery.

Self-host PageGo

Single HTML files or multi-page site folders, safety-checked either way

Deploy it yourself · No public online sign-up

PageGo

Deploy first, then connect your workflow

Prepare your infrastructure

Choose Cloudflare or Docker and configure domains, storage, and authentication.

Connect your publishing tools

Use the web interface on your instance, or connect the CLI and MCP server.

Publish and manage

Preview your content, publish it, and manage access and versions.

More capabilities

What happens after you hit publish

A stable link, versions you can roll back

Every publish keeps its own immutable address, while the stable link always points at whichever version you pick — switch back the moment something breaks.

You decide who can see it

Public, password-protected, or organization-only — switch visibility anytime, and approve access requests one by one.

Let your agent publish for you

Hook up the CLI or MCP server so Claude, Cursor, and similar tools can publish the page they just generated without you copying anything.

Open the source for remixing

Turn on remix access and visitors can download the full source to build on your work.

Organizations and collections keep work tidy

Cloudflare deployments support organization collaboration and collections. Docker currently limits login to the instance owner’s email.

AI agent integration

Let the agent hit publish itself

After deploying and authenticating with your instance, tools such as Claude Code and Cursor can publish generated HTML through the CLI or MCP without manual downloads and uploads.

CLI and MCP, either way inCalled directly by Claude Code, Cursor, and similar toolsConnect and authenticate with your own instance first

# MCP / CLI

$ pagego publish prototype.html

→ https://pages.example.com/a/team-prototype

Use cases

Client delivery

Publish prototypes, proposals, and demos with access permissions suited to each delivery.

Training materials

Organize interactive lessons and exercises on an instance you operate.

Team reviews

Let colleagues try AI prototypes and use a stable link to review the current version.

Internal tools

Publish static utilities and visualizations instead of passing files around.

Bold work, clear boundaries

Catch risks before publishing

PageGo checks high-risk HTML capabilities and discloses external origins. Public work is isolated from the signed-in console, visitors can report problems, and owners can quarantine a deployment immediately.

iframes, external forms, auto-redirects, and embeds are blocked outright

Public content and the signed-in console live on separate domains — uploaded scripts can't read your session

A stable link and immutable version addresses, side by side — switch back anytime

CSP restricts network capabilities to disclosed external origins

About PageGo

Your own Cloudflare account or Docker deployment

Your own domain, public content kept apart from the console

Resource costs depend on your provider, storage, and traffic

Self-hosted

Your data stays on your own turf

You deploy and operate PageGo. Work and account data are stored on the infrastructure you configure, using your Cloudflare account or Docker environment. This website introduces the software; it does not offer public online hosting.

FAQ

What you might want to know about PageGo

No. This is the PageGo product website, with no public online sign-up or hosting. Obtain the deployment materials and set up your own instance first. Existing users should sign in at the address provided by their administrator.

PageGo is for teams that want to operate their own publishing service. Administrators configure infrastructure, domains, and authentication. Teams can publish static content through MCP or the CLI without connecting a repository or CI for every project.

Yes. Deploy your own PageGo instance and authenticate first, then connect the CLI or MCP server so your agent can publish generated HTML.

Work and account data are stored on the Cloudflare or Docker infrastructure configured by your administrator. PageGo checks high-risk HTML capabilities and discloses external origins before publishing, with content isolated from the login service. Cloud infrastructure, authentication, and external resources may still involve other providers.

Cloudflare deployments support organization collaboration. Docker currently permits only the configured instance owner’s email to sign in through Google or Microsoft OAuth. Evaluate this limitation before choosing Docker for a team. Both options require your own domain configuration and maintenance.

Every publish keeps its own immutable version address, while the stable link always points at whichever version you picked. Switch back the moment you spot a problem, or quarantine a deployment outright.