A Bolt Hosting Alternative: What Can Leave Bolt Cloud

Need a Bolt hosting alternative? Check which parts of your Bolt app need a server, why free sites go offline at the cap, and which hosts fit. Nov 2026.
The OxyPages Team · · 8 min read
Your Bolt site was fine until the day it wasn't. Maybe it went offline near the end of a busy month. Maybe a customer asked why the page says "Made in Bolt". Or maybe you priced a custom domain and found it needs a paid plan.
Whatever started it, you're now looking for a Bolt hosting alternative, and the first question nobody asks you is the one that decides everything: what's actually in your Bolt app?
Bolt builds two very different things behind the same Publish button. Some projects are just screens, files that run in the visitor's browser. Others lean on Bolt Cloud for a database, logins, file storage, payments or server functions. The first kind can move to almost any host in an afternoon. The second kind can't move its backend to a static host at all.
So this post sorts first and shops second. Every vendor fact below comes from the vendor's own pages, and prices are as of November 2026. I run a static host, so I'll be plain about which Bolt projects it can't take. For the wider field, every static host compared side by side has the full table.
TL;DR: Bolt publishes to its own hosting on a bolt.host address by default. The free plan's hosting is capped at 10 GB of bandwidth and 333,333 requests a month across your whole account, and sites go offline until the month resets. Free sites carry Bolt branding, and custom domains need Pro at $25 a month. Before moving, check whether your project uses Bolt's database, logins, storage, payments or server functions. If it doesn't, it's a frontend-only build that Netlify, Cloudflare, Vercel, Render or another static host can serve. If it does, those parts stay on Bolt, and no static host can run them.
Why Do People Look Beyond Bolt Hosting?
Most people leave Bolt hosting because of the free plan's hard cap, the badge, or the price of a custom domain. The building side of Bolt usually isn't the problem.
The cap is the one that bites. Bolt's free plan allows "up to 10 GB bandwidth + 333,333 requests per month", and it's per account, not per site. When you hit it, sites "stop serving content once they reach their monthly limits and stay offline until usage resets." A test project you forgot about counts against the same allowance as the site your customers use.
To put 333,333 requests in perspective: one page visit isn't one request. The browser asks separately for the page, its scripts, styles, fonts and each image. If a visit makes 20 requests, an assumption that varies a lot by site, the cap works out at about 16,000 visits a month across everything you've published.
Then there's the "Bolt branding on websites" on the free plan, and custom domains, which need a paid plan. Pro is $25 a month billed monthly. Teams is $30 per member per month, so a three-person team pays $90.
Who Should Stay On Bolt Hosting
Stay if your app uses Bolt Cloud's backend. Bolt v2, launched on 2 October 2025, put databases, logins, storage, payments and hosting in one place, and that's genuinely convenient when you don't have a developer.
Stay too if you're still building every day. Publishing from inside Bolt is one click, and Pro raises hosting to 30 GB and 1 million requests a month, with optional pay-as-you-go above that up to a spending cap you set.
Which Parts Of Your Bolt App Need A Server?

Anything that has to store data, check who someone is, or run private code needs a server; screens that look the same for everyone don't. Go through your app with this list:
- The screens and layout. Once built, these are HTML, JavaScript, CSS and images. They run in the browser. Static.
- Sign-up and login. If Bolt Cloud handles these, they need Bolt's backend. Server.
- A database. Saved bookings, orders, user profiles or anything that's still there after a refresh. Server.
- File uploads. Photos or documents your users add are kept in backend storage. Server.
- Payments. Taking money needs private keys that can't sit in the browser. Server.
- Server functions. Bolt calls these "server functions, also called edge functions". They're code that runs on Bolt's side. Server.
- Links out to other services. A booking widget, a newsletter sign-up hosted elsewhere, a map. These live on someone else's servers, so they work from any host.
If everything in your app is item one or item seven, you have a frontend-only project. Bolt's own docs draw the same line: you can publish to Netlify instead of Bolt hosting, but "Netlify is limited to frontend-only sites." So if Bolt would let you publish it to Netlify, a static host can take it.
MDN's overview of how browsers and servers split the work is a good plain explanation of why that line exists.
Where Can A Frontend-Only Bolt Project Go?
A frontend-only Bolt project can go to any static host that builds from GitHub or takes a folder upload. These five are the realistic picks. Prices are monthly unless marked, as of November 2026.
Netlify
Netlify suits people who want the route Bolt already supports, since you can connect it from inside Bolt. Its Free plan allows commercial projects and custom domains, on 300 credits a month: a production deploy costs 15 credits and each GB of bandwidth costs 20. When credits run out, sites pause. Personal is $9 a month and Pro is $20 a month with unlimited members. How Netlify compares for simpler sites goes deeper.
Cloudflare
Cloudflare suits a busy site that needs to stay free. Static asset requests are free and unlimited, custom domains are included, and the Pages plan allows 500 builds a month. The catch is that Cloudflare runs two overlapping products, and its own Pages docs now point new projects to Workers instead.
Vercel
Vercel suits a personal project, or a team that plans to add server code later. The free Hobby plan includes 100 GB of fast data transfer a month, but it's for "personal or non-commercial use" only. A business site needs Pro: a $20 monthly platform fee with one deploying seat, plus $20 a month for each extra deploying seat.
Render
Render suits people who expect to add a Node server later and want it in the same place. Static sites are free to deploy, but the free Hobby workspace includes only 5 GB of bandwidth a month, then $0.15 per GB, and static sites count toward it. An always-on web service is $7 a month.
OxyPages
OxyPages is the one I run. It builds the project from GitHub on every push, or takes a ZIP of the built folder, with SPA mode and version history. Free is one personal, non-commercial site with 5,000 page views a month and no custom domain. Lite is $5 a month or $48 a year, with custom domains, commercial use and 20,000 views, and the quota counts page views rather than bandwidth or requests.
It can't run anything from items two to six above: no database, logins, storage, payments or server functions on any plan.
Comparing Each Bolt Hosting Alternative
Every figure is from the vendor's own pricing page or docs, as of November 2026.
| Host | Runs Bolt's backend features? | Free tier | Custom domain from | Business use on free? | The catch |
|---|---|---|---|---|---|
| Bolt hosting | Yes | 10 GB + 333,333 requests a month, account-wide | $25 Pro | Not stated | Offline until reset at the cap |
| Netlify | No (frontend only) | 300 credits a month | Free | Yes | Sites pause when credits run out |
| Cloudflare | No (frontend only) | Unlimited static requests | Free | Not banned | Two overlapping products |
| Vercel | No (frontend only) | 100 GB transfer | Free on Hobby | No, $20 Pro needed | Per deploying seat |
| Render | No (frontend only) | 5 GB bandwidth | Free (2 included) | Static sites: no ban found | $0.15 per GB over 5 GB |
| OxyPages | No (frontend only) | 1 site, 5,000 views | $5 Lite ($48 yearly) | No, Lite needed | No servers or databases |
Notice the second column. None of these hosts runs Bolt Cloud's database, logins or payments. If your app needs those, the backend stays with Bolt.
A Walkthrough: A Café Site That Hit The Cap

Picking a Bolt hosting alternative is easier with a real case, so here's a typical one. Say you run a café and built its site in Bolt on the free plan: a menu, opening hours, an events page, and a "Reserve" button that opens a booking service you already pay for. You also have two half-finished test projects published on the same account.
A local food blog features you, traffic jumps, and in the third week of the month the site goes offline. The test projects shared the same cap.
Run the list. Menu, hours and events are item one. The Reserve button is item seven. No database, no logins, no payments in Bolt. It's frontend-only, so it can move:
- Connect GitHub from inside Bolt. That gives the new host a copy of the code that updates whenever you change it in Bolt.
- Import the repository on the new host. For the usual Vite setup, the build command is
npm run buildand the output folder isdist. The full steps for deploying a Vite app cover the settings on most hosts. - Turn on SPA mode if the site has more than one route. Without it, a refresh on
/eventscan show a 404. - Check every page on the temporary address. Click the Reserve button and confirm the booking service still opens.
- Point your domain at the new host. Leave the
bolt.hostversion up until the new one has run cleanly for a few days. - Unpublish the test projects on Bolt. They no longer share a cap with anything important, but there's no reason to leave them live.
For a commercial café site, the cheapest honest options are Cloudflare's free plan or Netlify's free plan, both of which allow a custom domain. A $5 plan makes sense if you want a flat price with no credit meter.
What To Do Next
Run the seven-item list against your app before you look at a single pricing page. If everything is screens and links out, you have a frontend-only project and a lot of hosts to choose from. If it uses Bolt's database, logins, storage, payments or server functions, the backend stays on Bolt, and the realistic choice is Pro or keeping the free plan with an eye on the cap.
Got a frontend-only Bolt build and want to see it live before you decide? Try your Bolt build on a free subdomain and test it before you move the domain.
FAQ
Can I Host A Bolt App Somewhere Other Than bolt.host?
Yes, if it's frontend-only. Connect GitHub from inside Bolt and let another host build it, or build it and upload the output folder. Projects that use Bolt Cloud's database, logins, storage, payments or server functions need those parts to stay on Bolt.
What Happens When A Free Bolt Site Hits Its Limit?
It stops serving content and stays offline until your monthly usage resets. The limit is 10 GB of bandwidth and 333,333 requests a month, shared by every site on the account. Pro raises it to 30 GB and 1 million requests, with optional pay-as-you-go up to a cap you set.
Does Bolt Still Deploy To Netlify?
Netlify is still an option, but since Bolt v2 launched on 2 October 2025, new projects publish to Bolt hosting by default. Bolt's docs say Netlify is limited to frontend-only sites, so a project that uses Bolt's backend features has to stay on Bolt hosting.
Is Bolt Hosting Free?
Bolt's free plan includes hosting with no card required, but it carries Bolt branding and has no custom domain. Pro costs $25 a month and adds a custom domain and higher limits. If the app is frontend-only, any Bolt hosting alternative with a free custom domain can serve it instead.