Netlify Alternative
You built a site with an AI coding agent and you want a real URL for it — one a colleague or a client can open, and nobody else.
Netlify is closer to that than most platforms, and it got closer in July. So this comparison starts with a correction.
Through the summer this page said “Netlify: public by default”. On 28 July 2026 Netlify changed that, and the replacement is not the opposite claim — which is the part worth reading slowly. From Netlify’s project visibility documentation (last updated 19 August 2026):
“Teams created on or after July 28, 2026 start with this default setting: Private for new projects. Teams created before then keep this default setting: Public.”
The default is a property of your team’s age, not of the product, and it is scoped by plan family: “This feature is available on Credit-based Free, Personal, and Pro plans only.”
So “Netlify is public by default” is now wrong, and “Netlify is private by default” would be wrong too. Two teams on the same product can behave in opposite ways, and if yours predates the change, nothing moved. Where the setting is on, Netlify carries it through: “Previews stay private unless you change the preview visibility setting.” A better default than most of the field.
Once previews are private on both, the question is how you let one specific person in. Netlify answers by signing them in:
“Private projects are enforced with Netlify login: only your team and people you invite can view a private project.”
Free when your reviewer is a colleague, a dead end when they are a client. The same page limits who you can invite on the cheap tiers: “On a Free and Personal plan, private projects can only be seen by the Team Owner”, and “On Free and Personal plans, projects are single-seat. To invite others, upgrade to Pro.” So a Free private project has an audience of one: you.
The shared password is the way past the login, and Netlify puts it one tier lower than VibeHost, where it is a Business feature and Free has none. From Netlify’s password protection documentation (last updated 28 July 2026): “Basic password protection for your entire site is available on all Pro plans.” The same page is explicit that the two gates are alternatives rather than layers:
“If your project is set to private, it already requires users to sign in with their Netlify credentials, so you do not need to configure a password.”
That is the design difference. On Netlify a password replaces the login gate, and “Anyone can use your basic password to access a site deploy”. On VibeHost it composes with the access gate, so a leaked password still does not open a private app.
A newly created app is private, and access is evaluated at the edge on every request. Three things open one up: a share link, whose holder never signs in and whose revocation stops their next request; an email or team grant on one app, matched against the email on the account with no workspace-membership condition, so a client does not count toward the member cap; and workspace visibility, the one path that does require membership.
There is no repository and no build: point the CLI at a directory with an index file and the server assembles a release. Previews are named channels, so one exists because you deployed to it. Mechanics in share links and grants and visibility.
Pick Netlify if…
Pick VibeHost if…
What VibeHost does not do: functions, edge functions, builds, git integration. Free apps sit on a vibehost.space subdomain with no custom domain and no password.
It depends on when your team was created. Netlify's documentation says “Teams created on or after July 28, 2026 start with this default setting: Private for new projects. Teams created before then keep this default setting: Public.” The setting is also scoped: “This feature is available on Credit-based Free, Personal, and Pro plans only.” Where it is on, “Previews stay private unless you change the preview visibility setting.”
One. Netlify documents that “On a Free and Personal plan, private projects can only be seen by the Team Owner”, and that “On Free and Personal plans, projects are single-seat. To invite others, upgrade to Pro.” On VibeHost an email grant attaches to one app, not the workspace, so a reviewer takes no seat.
Yes. Netlify's wording is “Private projects are enforced with Netlify login: only your team and people you invite can view a private project.” The shared-password route skips the login but needs a paid plan: “Basic password protection for your entire site is available on all Pro plans.” A VibeHost share link is the third shape — its holder opens the app with no account.
Yes, in several documented ways: “dragging a project folder containing your site files (like .html files) to Netlify Drop”, the CLI with “netlify deploy --prod”, and the API “using a file digest or a ZIP file”. What still needs Git is the automatic preview: Deploy Previews come from a pull or merge request in a connected repository, or from an agent run that changes a file.
No. Static output is currently the only generally available runtime, and a server-rendered runtime for Next.js apps with API routes is in private beta. Netlify's documentation describes Functions as a way to “build full-stack applications without having to manage servers”, which is a real reason to stay there.
On price: VibeHost Free is 100 apps, 5 GB and 3 members; Business is $20 per month per workspace for unlimited apps, 500 GB, 20 custom domains and unlimited members. Netlify’s credit allowances are not stated on the documentation pages read here, so this compares access gates rather than meters. The rest is in the docs comparison, with five other platforms.