VibeHost vs Vercel, Netlify, Cloudflare Pages, Render, GitHub Pages (2026)

Most comparisons of static hosts rank build speed and CDN edges. If you are shipping work someone else has to look at before it goes public, the question that decides the platform is narrower: who can open this URL, and what does it cost to change that.

Every competitor cell below is a quote from that platform's own documentation, with the URL. Where a platform's docs do not answer a question, the cell says so rather than guessing.

Who can open a new deploy

The row that costs the most money is the third one. Four of the six platforms answer "restrict this preview" with "make the viewer authenticate", which means the client, the designer, or the stakeholder has to create an account on your hosting platform to look at one page.

Vercel documents both halves of that plainly. From Vercel's guide to sharing a preview deployment (last updated 2026-08-28):

"The collaborator does not need to have a Vercel account, but will need to create one if they wish to view a deployment that is protected, use the toolbar, or leave comments."

An unprotected deployment is open to anyone with the link; a protected one requires an account. The sharable link is Vercel's way out of that, with a documented ceiling on the cheap plan. From Vercel's sharable links documentation (last updated 2026-08-28):

"Developers on the hobby plan can only create one shareable link in total per account."

The invite path has the same shape: "Users on Pro and Enterprise teams can use this method to add one or more collaborators. Hobby users are limited to one collaborator at any one time."

Netlify's private mode is explicitly account-based. From Netlify's project visibility documentation (last updated 19 August 2026):

"Private projects are enforced with Netlify login: only your team and people you invite can view a private project."

The same page limits who that can be on the cheaper tiers:

"On a Free and Personal plan, private projects can only be seen by the Team Owner. On Pro plans, you can add unlimited team members to your project or team to view a project."

Netlify does get credit for the default. From the same page:

"On Credit-based plans, new projects start private by default when this setting is enabled for your team."

"Previews stay private unless you change the preview visibility setting."

Cloudflare's default runs the other way. From Cloudflare's preview deployments documentation:

"By default, these deployment URLs are public."

"By default, preview deployments are enabled and available publicly. In your project's settings, you can require visitors to authenticate to view preview deployment."

GitHub Pages ties access to the repository, and gates private publishing on an organization plan. From GitHub's Pages visibility documentation:

"To publish a GitHub Pages site privately, your organization must use GitHub Enterprise Cloud."

"A privately published site can only be accessed by people with read access to the repository the site is published from."

VibeHost's answer is a share link: a minted URL whose holder needs no account and never signs in. The plaintext token is returned once at creation and the server keeps only a hash plus a short display prefix. Optional expiry from 1 to 90 days, or none. Revoking it stops the visitor's next request, because the gate re-reads the link's revocation state from the database on every request rather than waiting for a cookie to expire.

What it costs to put a password on a preview

Vercel's add-on carries a lock-in clause worth quoting, from Vercel's deployment protection documentation (last updated 2026-08-28):

"You must have used the feature for a minimum of 30 days before you can disable it."

The same page places each method on a plan. Vercel Authentication is "Available on all plans"; Password Protection is "Available on the Enterprise plan, or as a paid add-on for Pro plans"; and "Pro plan customers can access these features for an additional $150 per month".

Netlify's basic password is included further down the ladder. From Netlify's password protection documentation (last updated 28 July 2026):

"Basic password protection for your entire site is available on all Pro plans."

VibeHost's password gate is Business only, and Free has no shared-password option at all. That is the honest read: on the free tier VibeHost gives you private visibility, per-email grants, and share links, and no password.

What creates a preview, and what it needs

Four of the six make a preview out of a git event. From Netlify's deploy overview (last updated 26 August 2026):

"By default, Netlify automatically builds Deploy Previews when you do one of the following: start an agent run that makes a file change to your site/app; open pull / merge requests in a connected site repository from GitHub, GitLab, Bitbucket, or Azure DevOps."

From Render's pull request previews documentation:

"For Git-backed services, Render can create a service preview for pull requests opened against your linked branch."

Render's preview is a whole extra instance, and priced as one: "For each service preview, Render creates a separate, temporary instance of your service with its own onrender.com URL." and "PR Previews are billed at the same rate as your base service. They are always prorated by the second." A free static site's previews are free too.

Render also documents the difference between unindexed and unreachable:

"Render automatically sets the HTTP response header X-Robots-Tag: noindex for all preview instances."

That keeps a preview out of search results. It does not stop a person who has the URL.

VibeHost has no git integration at all. A preview is a channel — production, pr-42, dark-mode — and the server holds zero git knowledge. That is a real limitation if you want previews to appear automatically on pull request, and the reason the platform works at all when the code came out of an agent and never touched a repository.

Documented ceilings

VibeHost's own per-plan and per-runtime caps, including every row above, are on the limits page.

The constraint that catches paid work sits on GitHub Pages, from GitHub Pages limits:

"GitHub Pages is not intended for or allowed to be used as a free web-hosting service to run your online business, e-commerce site, or any other website that is primarily directed at either facilitating commercial transactions or providing commercial software as a service (SaaS)."

VibeHost plan numbers

Over the storage cap, deploys return 402 — free up space or upgrade. Usage-based overage billing is not live yet, so going over is never a charge today. Bandwidth is metered and shown on the usage card, but nothing is blocked when you go over it.

Business is priced per workspace. Not per app, and not per member — there is no seat fee, which is the reason granting one contractor read access on one app has no billing consequence.

When to pick which

Vercel — a Next.js application with server-side rendering, edge functions, and a git-driven release process. The framework integration is the product.

Netlify — a git-driven site where previews should be private by default and a shared password is included at Pro rather than sold as an add-on. On credit-based plans Netlify's default is the closest of the five to VibeHost's.

Cloudflare Pages — a public, high-traffic site, or a team that already runs Cloudflare Access. The free file allowance and 100 custom domains per project on the free plan are more generous than VibeHost's.

Render — a front-end that lives alongside a web service, a database, a worker, or a cron job. Running them on one platform beats splitting them, and VibeHost hosts none of the others.

GitHub Pages — a public site whose source already lives in a GitHub repo, on a project that is not commercial. Free, no setup, and the build runs on GitHub.

VibeHost — a static artifact that has to be private the moment it exists and reviewable by someone who should not have to create an account. No repository, no build step for a static app, no seat fees. Ten coding agents and CLIs, two chat clients over MCP, and five AI canvas surfaces through a Chrome extension are documented paths to the same API.

What VibeHost does not do

Static only. The static runtime is the only generally available one; a server-rendered runtime for Next.js apps with API routes and middleware is in private beta. No databases, no queues, no persistent websockets, no cron, no workers.

No builds and no git. There is no repo linking and no automatic per-pull-request preview.

Nothing on Free beyond *.vibehost.space: zero custom domains, no shared password, and a watermark on the link preview card.

Sources

Every competitor quote on this page comes from that platform's own documentation:

• Vercel — Deployment protection
• Vercel — Sharing deployments
• Vercel — Sharable links
• Netlify — Project visibility
• Netlify — Password protection
• Netlify — Deploy overview
• Cloudflare Pages — Preview deployments
• Cloudflare Pages — Pages overview
• Cloudflare Pages — Limits
• Render — Static sites
• Render — Pull request previews
• GitHub Pages — Changing the visibility of your GitHub Pages site
• GitHub Pages — GitHub Pages limits

Replit is not in the six-way table on purpose: it is a build environment that also publishes rather than a static host. It has its own comparison.

See also

• One-on-one comparisons: Cloudflare Pages, Render, GitHub Pages, Replit
• Migration walkthroughs: Netlify, Replit, Weebly, and Vercel, whose full walkthrough is still being written and currently points at the Netlify steps
• Concepts — workspaces, apps, channels, grants, and why the server holds no git state
• Limits — per-plan caps, generated from what the API enforces
• Share private deploys — the private-app-plus-share-link pattern end to end