What is AI-native hosting?

There's a new category of web hosting emerging. We call it AI-native hosting — and if you've been shipping sites with Claude Code, Cursor, or Windsurf, you've probably wanted it without knowing the name.

This post defines the category, explains why the old hosting platforms don't fit, and shows what to look for.

The short version

AI-native hosting is web hosting that treats AI agents as first-class deployers and editors of your site, not as a security threat or an afterthought.

It means:

• Your AI can deploy a folder of files in 60 seconds, not "submit a PR and wait for CI"
• Your AI can edit your live site ("change the about page headline to X") in 8 seconds, not "open a git branch, commit, push, wait for rebuild"
• Your AI can roll back to a previous deploy when an edit goes wrong, in one command
• The hosting provider's CLI is open source and runs on your machine, so you can read every line

If you've used any of these platforms, you know none of them do this today.

How we got here

For the last ten years, the dominant web hosting platforms — Vercel, Netlify, Cloudflare Pages, Render, GitHub Pages — have all assumed the same deploy flow:

1. Write code
2. Commit to git
3. Push to GitHub
4. CI builds the site
5. CDN deploys the result
6. User sees the change

This makes sense when the "deployer" is a human developer pushing code through a git workflow. The whole industry is built around it.

But the deployer isn't always a human anymore. In 2026, an AI agent shipping changes on a builder's behalf is increasingly common. And the git-based flow doesn't fit:

• An AI shouldn't need to know about git
• A single typo fix shouldn't trigger a 40-second full rebuild
• An AI committing to a shared repo with the developer's credentials is a security nightmare
• Waiting for CI when you're iterating with an AI is unbearable

The old platforms treat AI agents as second-class citizens at best. Some treat them as security threats.

What AI-native hosting is

A hosting platform that has AI agents built into its core. Concretely, that means:

1. The AI has tools, not access

The AI doesn't need your git credentials, your GitHub token, or your deploy keys. It calls tools over a standard protocol (we use MCP, the Model Context Protocol). Each tool is scoped — it can deploy, it can patch, it can rollback. It can't access your other repos or read your other services.

This is the same security model as a smartphone app having access to your camera but not your contacts.

2. The build step is optional

A full deploy still does a build (it's faster and lets you use build tools). But a patch — "change one line in this file" — doesn't need a rebuild. It just lands on the live site.

This is what makes conversational editing possible. Your AI makes 10 small edits, the user sees them all live, and the "deploys" feel as fast as typing in a doc.

3. Quotas are designed for AI usage

Traditional hosting charges per build minute. AI agents make a lot of small edits, not a few large builds. So AI-native hosting charges per "deploy" with patches counting as a tenth of a full deploy.

This means a builder can patch their site 200 times a day without hitting a quota. Try that on Vercel's free tier.

4. The CLI is open source

The CLI and the MCP server are MIT-licensed. You can read every line. You can self-host if you want. You can fork it.

This isn't about ideology. It's because an AI agent running your deploys is a high-trust action. The CLI being open source means a security researcher can audit it, and you can verify it's not doing anything weird.

5. The hosting itself is good at static

AI-native hosting doesn't try to be all things. It's good at static sites, SPAs, and simple multi-page apps. It doesn't pretend to handle Kubernetes or microservices. You use Cloudflare Workers or Vercel Functions for dynamic stuff, Krexel for the static shell.

This focus means it's faster, cheaper, and simpler than the alternatives for the 90% case.

What it isn't

It's not:

• "Vercel but with AI bolted on" — Vercel is a git-based platform with AI features added later. AI-native is built around AI from day one.
• "AI that builds your site for you" — that's a different category (autonomous website generators like Durable, Mixo, etc.). AI-native hosting is when you're building with an AI and need to deploy what you built.
• "Serverless everything" — AI-native hosting is optimized for static. Dynamic compute is a separate concern.
• "Just an MCP wrapper around Vercel" — that's basically what we tried first. It didn't work because the git flow underneath is too slow for conversational editing.

Why now

Three things converged in 2026:

1. AI agents got good enough to ship real code. Claude Code, Cursor, and Windsurf can write production-quality frontend code.
2. MCP became a standard. Before MCP, every AI tool needed a custom integration. Now there's a protocol, and any AI client can use any MCP server.
3. Edge networks got fast enough. A patch deploy that lands in 8 seconds is only possible because the CDN is right next to the user.

If any one of those weren't true, this category wouldn't exist.

What to look for in an AI-native host

If you're evaluating options, here's the checklist:

• MCP server, not just a CLI. The CLI is for you. The MCP server is for your AI.
• Patch deploys (not just full deploys). If every edit is a full rebuild, it's not really AI-native.
• Open source CLI. Security researchers need to be able to read it.
• Quota model that fits AI usage. Per-deploy with patch-as-fraction, not per-build-minute.
• Conversational editing that actually works. Your AI should be able to read the current site state, generate a patch, and deploy it, all in one tool call.

Krexel does all five. We're biased. But the checklist is real.

Who AI-native hosting is for

The category fits:

• Solo founders building MVPs with Claude Code as their pair programmer
• Designers shipping portfolios and client sites without learning git
• Indie hackers iterating on landing pages daily
• Small teams where one person uses an AI to ship most of the frontend

It doesn't fit (yet):

• Enterprises that need SSO, audit logs, compliance certifications
• Large engineering teams with established git workflows and CI pipelines
• Backend-heavy apps that need a database, queues, etc.

For those use cases, traditional hosting still wins.

What's coming

A few predictions:

1. Every major hosting platform will add an MCP server in the next 12 months. They have to. AI agents are how the next generation builds.
2. Patch deploys will become standard. Full rebuilds for one-line edits will feel as slow as dial-up does now.
3. The "hosting for AI agents" category will get crowded. That's good. We're not trying to be the only one — we want this category to be real.
4. Open source CLIs will be the norm. Closed-source deploy tooling will feel as sketchy as closed-source crypto wallets do now.

We're betting on AI-native hosting being the default for new sites within 3 years.

Try it

If you've read this far, you're probably the target audience.

npm install -g krexel
krexel deploy

Sixty seconds later, you have a live site. Then install the MCP server and your AI can edit it for you.

---

This post is by Saad, founder of Krexel. We define the category because we're trying to build the best version of it. If you disagree with anything here, email hello@krexel.com — we want to know.