A Cloudflare Pages alternative with the backend built in.
Cloudflare Pages is excellent static and edge hosting. shiply.now runs on the same Cloudflare edge, but it is built for agents to publish the whole app in one call — with a database, edge functions, email, and a custom domain attached from the same surface, no account to start.
Publish my site to shiply.now and give me the live URL. Read https://shiply.now/skill.md first — it is the live API map. Before publishing, look for .shiply.json and existing Shiply credentials; if MCP is connected, call whoami. If no valid credential is available, publish anonymously immediately — never block the first live URL. Then show me Shiply’s REAUTH_REQUIRED verification link so I can claim it. If I choose email reconnect, request the six-digit code, wait for me to paste it, verify it, and securely save the returned API key. In a cloud sandbox, use the raw HTTP API only (no npm or install scripts). Follow Shiply’s JSON errors and docs pointer; don’t guess.
Pages hosts the front end. The backend is still yours to assemble.
Cloudflare Pages is a great, low-cost way to put a static site or a front end on the edge. The gap shows up at the next step — the database, server functions, email, and domain — which you still wire together yourself, and which an agent cannot set up in a single call.
To be clear: this is not a bill-shock argument — Pages is cheap and its free tier is generous. It is an architecture-and-workflow argument. If your agent just built an app that needs a real backend and a URL right now, Pages gives you the static host and leaves the rest to you and a dashboard. shiply gives you the whole stack in one call, on the same network.
Same edge. Backend included. One call.
Your agent ships app, database, functions, email, and domain in one place — served from Cloudflare, published in a single request.
Your agent publishes in one HTTP call
No Git remote to connect, no build pipeline to configure, no account to create before you can ship. Your agent POSTs once and the site is live at a real <slug>.shiply.now URL in a single request — then add a database, edge function, email, or custom domain from the same surface.
- No account, no Git remote needed to start
- One HTTP call — no build to wait on
- Agent-first: MCP (100+ tools), CLI, or raw HTTP
The backend comes in the box — on the same network
Pages hosts the front end; shiply hosts the whole app plus its backend. App (static or full SSR), a SQL database (Cloudflare D1 or Neon Postgres), edge functions, transactional email with a per-site inbox, custom domains with auto DNS and SSL — all on Cloudflare’s edge, the same network Pages runs on.
- SQL database attached to the site — D1 or Neon Postgres
- Edge functions, email + per-site inbox, custom domains
- Marketplace to sell a finished site via Stripe Connect
shiply.now vs Cloudflare Pages, at a glance
Same edge network — the difference is the bundled backend and the agent-native, one-call workflow.
| Feature | shiply.nowagent-native | Cloudflare Pagesstatic / edge host |
|---|---|---|
| What it hosts | ||
| Static sites and front ends | ||
| Full SSR apps in one placeSvelteKit, Astro, Nuxt, React Router, Next.js | Via Workers / Functions setup | |
| Served from Cloudflare’s edge | ||
| Generous free tier | ||
| Getting started | ||
| Account required to start | ||
| Publish method | One HTTP call — no Git, no build step | Connect a Git repo, then build + deploy |
| Agent-first API + MCP tools | Partial | |
| Real URL the moment the call returns | After a build completes | |
| Backend in the box | ||
| SQL database attached to the siteCloudflare D1 + Neon Postgres | Bind D1 / Neon yourself | |
| Edge functions | ✓ (Pages Functions / Workers) | |
| Transactional email + per-site inbox | ||
| Custom domains, auto-DNS + SSL | ||
| Marketplace to sell a finished siteStripe Connect, atomic handoff | ||
How they compare, category by category
What it hosts. Pages is a static and edge host — excellent for static sites and front ends, with SSR possible through Pages Functions and Workers you configure. shiply serves static and full SSR for every major JS framework out of the box, as a per-site Worker, on the same Cloudflare edge.
Getting live. Pages connects a Git repo and builds. shiply publishes in one HTTP call with no Git remote, no build step, and no account — the URL is real the moment the call returns.
The backend. On Pages you bring and bind D1, Workers, and an email provider yourself. shiply attaches a SQL database (D1 or Neon Postgres), edge functions, transactional email with a per-site inbox, and a custom domain from the same surface — plus a marketplace to sell the finished site.
Agents. shiply is agent-native: a write-enabled MCP with 100+ tools, a CLI, and llms.txt / agent.json discovery surfaces mean your agent can publish and operate the whole thing without a human in a dashboard.
Who each one is best for
shiply.now is best for solo builders, vibe-coders, and freelancers who want an AI agent to publish a whole app — front end plus backend — to a real URL right now, with the database, functions, email, and domain included, and a marketplace to hand off client work.
Cloudflare Pages is best for hosting a static site or a front end straight from a Git repo on Cloudflare — with its own build pipeline, preview deploys per pull request, a very generous free tier, and deep integration with the rest of the Cloudflare dashboard. If you do not need a bundled backend or agent-native publishing, Pages is an excellent, low-cost choice — and shiply runs on the same edge network if you outgrow the static-only setup.
Moving a site from Pages
Because both run on Cloudflare’s edge, moving a site is straightforward: point your agent at the same build output you deploy to Pages and publish in one call — no Git remote, no build config. Then attach a database (D1 or Neon Postgres), edge functions, or email from the same surface, and point your custom domain over with auto DNS and SSL. See the frameworks guide for the exact build and publish commands.
Cloudflare Pages alternative — common questions
Is shiply.now a replacement for Cloudflare Pages?
It depends on the job. Cloudflare Pages is excellent, generous static and edge hosting — if all you need is to deploy a static site or a front end from Git to Cloudflare’s network, Pages is a great, cheap choice. shiply.now runs on the same Cloudflare edge, but it is built for agents to publish the whole app — static or full SSR — in one HTTP call, with a database, edge functions, email, and a custom domain attached from the same surface. shiply is the alternative when you want the backend included and an agent driving it, not a separate static host to configure.
What does shiply add on top of what Pages already does?
The backend and the workflow. Pages hosts your static or front-end build; shiply hosts the app and gives you a SQL database (Cloudflare D1 or Neon Postgres), single-file edge functions, transactional email with a per-site inbox, custom domains with auto DNS and SSL, and a marketplace to sell a finished site via Stripe Connect — all published in one call, with no account needed to start.
Does shiply use the same network as Cloudflare Pages?
Yes. Every site you publish is served from Cloudflare’s global edge — the same network Pages runs on — with automatic, unmetered DDoS mitigation on every plan. You keep the performance and reach you would get from Pages, and add the backend and the agent-native publishing flow on top.
Can my AI agent publish to shiply without me signing in first?
Yes. Your agent POSTs once and the site is live at a real <slug>.shiply.now URL — no account needed to start. You claim it later with one click to keep it. There is a write-enabled MCP server with 100+ tools, a CLI (npm: shiply-cli), and a plain REST API, so Claude Code, Cursor, or any HTTP-capable agent can ship directly — no dashboard, no Git remote to wire up.
When is Cloudflare Pages the better choice?
Reach for Pages when you want to host a purely static site or a front end straight from a Git repo on Cloudflare, with its own build pipeline, preview deployments per pull request, and a very generous free tier. It is a great, low-cost static host and integrates deeply with the rest of the Cloudflare dashboard. If you do not need a bundled backend or agent-native one-call publishing, Pages is an excellent pick.
Does shiply run full server-side rendering?
Yes. shiply runs real SSR on production for every major JS framework — SvelteKit, Astro, Qwik, the Nitro family (Nuxt, SolidStart, Analog, TanStack Start), React Router v7, and Next.js (plain SSR via OpenNext) — all served from Cloudflare’s edge as a per-site Worker. The one current limit is Next.js ISR and on-demand revalidate, which are not supported yet.
Comparing more hosts? See the Railway alternative, the Render alternative, the Vercel alternative, or the full shiply vs Vercel breakdown.
The whole stack, in one call.
Same Cloudflare edge, backend included. No account to start, live at a real URL in a single request.