ShipPage vs Vercel vs Netlify vs PageDrop: which is right for AI-generated pages?

If your AI agent just generated an HTML report and you want a URL for it, which hosting service is the right choice? This is a practical guide comparing ShipPage, Vercel, Netlify, and PageDrop across the axes that matter: setup time, persistence, agent ergonomics, and cost.

TL;DR

• AI agent generating one-shot HTML, no account setup → ShipPage or PageDrop.
• Need page management (edit, delete, password protect) → ShipPage.
• Running a full app with a git repo and CI → Vercel or Netlify.
• Permanent hosting with custom domains and CDN analytics → Vercel or Netlify (or ShipPage Pro when it launches).

Feature matrix

When to pick ShipPage

Pick ShipPage when your workflow looks like: "AI agent generates HTML. I want a URL." You care about agent ergonomics — zero setup, programmatic CRUD, MCP/Skill integration — more than about custom domains or a build pipeline.

Specific signals:

• You use Claude Code, Claude Desktop, or Cursor and want the AI to publish directly.
• You need to password-protect a page your agent generated.
• You want to list and manage all pages a particular agent has published.
• You want Markdown in → styled HTML out, without maintaining a static-site generator.

When to pick PageDrop

PageDrop is the simplest possible HTML hosting. One POST, one URL, no account, no management. Pick it when your publish-and-forget need is even simpler than ShipPage's, and you do not need to edit or delete the page afterward.

Specific signals:

• You are publishing anonymously and do not need to link pages to an agent identity.
• You will never need to update, password-protect, or programmatically delete the page.
• The page is genuinely disposable after the first view.

When to pick Vercel

Vercel is purpose-built for modern frontend apps — Next.js, static sites, serverless functions — with a full deployment lifecycle: git-based deploys, previews, environment variables, custom domains, and team collaboration. Pick Vercel when you are shipping a product, not one-shot output.

Specific signals:

• You have a codebase in a git repository.
• You need preview deployments per branch or pull request.
• You want CDN caching, edge middleware, serverless functions.
• You are building a long-lived application, not publishing ephemeral artifacts.

When to pick Netlify

Netlify plays in the same league as Vercel with strong form handling, identity, and edge functions. The selection criteria overlap heavily — team preference and specific platform features matter more than category differences. Pick either Vercel or Netlify when you are building a site or app, not when you are shipping AI output.

A common misconception

"Why not just use Vercel's CLI to deploy?" You can — but the agent workflow is awkward. Vercel assumes a project: a directory, a build command, a framework. Your AI-generated one-off HTML has none of that. You would spend more effort wrangling vercel.json than writing the HTML.

ShipPage and PageDrop exist precisely because a single HTML string is the unit AI agents produce — and the right tool should accept exactly that unit with exactly one call.

Decision tree

Are you publishing a one-off HTML string from an AI agent?
├── Yes → Do you need to edit/delete/password-protect it later?
│        ├── Yes → ShipPage
│        └── No  → PageDrop (or ShipPage if you're on Claude/Cursor)
└── No  → Are you deploying a codebase with git?
         ├── Yes → Vercel or Netlify
         └── No  → rethink the question

Getting started with ShipPage

Install the OpenClaw skill:

clawhub install shippage

Or add the MCP server to Claude Desktop or Cursor:

{"mcpServers":{"shippage":{"command":"npx","args":["shippage-mcp"]}}}

Or just curl the API directly:

curl -X POST https://shippage.ai/v1/publish \
  -H "Content-Type: application/json" \
  -d '{"html":"<h1>Hello</h1>","public":true}'

See the full guide: How to publish HTML from Claude, Cursor, or any AI agent.