An Appwrite Sites Alternative For Static Builds

Need an Appwrite Sites alternative for a static React or Vite build? Free is 1 member and 5 GB, Pro is $25 a month per project. Five hosts compared, Nov 2026.
The OxyPages Team · · 8 min read
You picked Appwrite for the backend: auth, a database and a couple of functions. When Appwrite Sites launched in May 2025 as "the open source Vercel alternative", putting your React front end in the same project felt obvious. One console, one bill, preview URLs on pull requests.
Then a second developer joined, and the free plan said one member. Or you opened the console after a quiet week and found the project paused.
That's usually when people start looking for an Appwrite Sites alternative. Here's the part most posts skip: you don't have to leave Appwrite to do it. A static build can live on any host and still call Appwrite's API, as long as you tell Appwrite about the new domain.
This post covers what Sites costs a small team, who should keep everything in one place, and five hosts that can serve the front end instead. Every vendor figure was checked on the vendor's own pages in November 2026, and prices are monthly unless marked. For the whole field, every static host compared side by side has the bigger table.
TL;DR: Appwrite Sites hosts static builds and server-rendered apps next to Appwrite's backend, with pull request previews and instant rollbacks. The Free plan gives 5 GB of bandwidth, one member and two projects, and free projects pause after a week of inactivity. Pro starts at $25 a month with unlimited members, plus $15 for each extra project. Stay if your site uses server rendering or you value one bill for backend and hosting. If your Site is a static React, Vue or Vite build, you can host it on Netlify, Cloudflare, Vercel, Firebase Hosting or a flat-priced static host and keep calling Appwrite from there.
What Appwrite Sites Is Good At
Appwrite Sites is web hosting built into Appwrite, the open-source backend platform. It serves single-page apps, landing pages and docs as static files, and it runs server-rendered apps for Next.js, Nuxt, SvelteKit, Astro and Remix.
The strengths are real:
- Everything in one project. Your site, database, auth, storage and functions share a console and a bill.
- Pull request previews. Each pull request gets its own preview URL, which is the feature small teams ask for first.
- Instant rollbacks and deploys from GitHub on every push, plus a CLI and manual uploads.
- Unlimited members on Pro. Appwrite doesn't charge per seat, so adding a teammate costs nothing extra.
- Self-hosting. Appwrite is open source, so you can run the whole stack on your own server.
Commercial use is allowed on Free too. Appwrite's terms only bar commercial use on its Education plan.
Why People Look For An Appwrite Sites Alternative
People move their front end off Sites for four reasons, all from Appwrite's own pricing page as of November 2026.
Free is one member. The Free plan lists "1 member". If two developers need console access, you're on a paid plan.
Free projects pause. Appwrite says "Free projects are paused after 1 week of inactivity." A side project that nobody touches for a week goes quiet, backend included.
5 GB of bandwidth on Free. Your site's images and JavaScript share that 5 GB with every API call. At the limit, Appwrite says the project freezes and the console goes read-only.
Pro is priced per project. Pro starts at $25 a month and includes one project. Each extra project is $15 a month.
There's also a cheaper Start plan from $10 a month with three members and 80 GB of bandwidth, but it's offered only in 19 listed countries, including India, the Philippines, Vietnam and Nigeria.
What A Small Team Pays On Appwrite
Say you're a team of three running three client apps, each in its own Appwrite project. On Pro that's $25 for the first project plus 2 × $15, so $55 a month. You get unlimited members, 2 TB of bandwidth and 150 GB of storage, which is a lot of headroom.
Now say one of those three is just a marketing site with no backend. It still costs $15 a month as its own project. That's the case where moving one static build pays for itself.
Be honest with yourself about the other two. If the backend stays in Appwrite, moving the front end doesn't remove the project fee or the inactivity pause on Free. It only moves the hosting.
Who Should Stay On Appwrite Sites?
Stay on Appwrite Sites when the things that make it different are the things you use. Here's when moving would cost you more than it saves.
- Your app is server-rendered. Next.js with server actions, Nuxt or SvelteKit in SSR mode needs a server, and a static host can't run it.
- You want one bill and one console. That convenience is the whole pitch, and it's worth paying for.
- You're already on Pro. Members are unlimited and previews are included, so a static host adds a second place to manage.
- You self-host Appwrite. Hosting the front end on the same server keeps everything inside your own setup.
- You need free commercial hosting with a custom domain. Appwrite Free allows commercial use. Several static hosts' free plans don't.
If none of those apply, your Site is a folder of built files that happens to sit next to a backend.
Choosing An Appwrite Sites Alternative
Pick on three things: preview links, whether the bill grows with your team, and whether the free plan allows commercial use. All prices are monthly and as of November 2026.
| Host | Free tier | Paid from (monthly) | Preview links | Commercial use on free | The catch |
|---|---|---|---|---|---|
| Appwrite Sites | 5 GB bandwidth, 1 member, 2 projects | Pro $25 + $15 per extra project | Pull requests | Yes | Free projects pause after a week |
| Netlify | 300 credits, hard limit, 1 member | Pro $20, unlimited members | Every pull request | Yes | Deploys and bandwidth spend credits |
| Cloudflare Pages / Workers | Unlimited static requests, 500 builds | Workers Paid $5 per account | Branches and pull requests | No clause in terms; marketed for hobby use | Two overlapping products |
| Vercel | Hobby: 100 GB transfer, 1 seat | Pro $20 per deploying seat | Every pull request | No, personal or non-commercial | Per-seat billing plus usage |
| Firebase Hosting | 10 GB storage, 360 MB a day transfer | Blaze pay as you go, $0 minimum | Preview channels | No restriction on the pricing page | Spark sites disabled at quota |
| OxyPages | 1 site, 25 MB, 5,000 page views | Lite $5 ($48 a year), Starter $10 | No per-pull-request URLs listed | No, personal only | No server code at all |
Netlify
Netlify suits a small team that wants previews and no seat math. It builds a Deploy Preview for every pull request, and previews don't consume credits. Free allows commercial projects but one member. Pro is $20 a month flat with unlimited members and 3,000 credits. The catch: each production deploy costs 15 credits, bandwidth costs 20 credits per GB, and sites pause at zero unless you turn on auto-recharge.
Cloudflare Pages Or Workers
Cloudflare suits a site with spiky traffic, because static requests are free and unlimited. Pages builds preview URLs for branches and pull requests, and Workers Paid is $5 a month per account, not per person. The catch is the split between two products: Cloudflare's Pages docs now send new projects to Workers.
Vercel
Vercel suits a team heading towards Next.js, which also covers the server-rendered case a static host can't. Hobby is personal or non-commercial only, with one developer seat. Pro is $20 a month per deploying seat, so three developers pay $60 before usage. The Vercel alternatives post goes deeper on that bill.
Firebase Hosting
Firebase Hosting suits teams who already know Google's console. The free Spark plan gives 10 GB of storage and 360 MB of transfer a day, with custom domains and preview channels. Past that, Blaze is pay as you go at $0.15 per GB. The catch: on Spark, sites are disabled when the transfer quota runs out, and on Blaze, budget alerts don't cap your charges.
OxyPages
We make this one, so here's the plain version. There's no per-seat or per-project fee: Lite is $5 a month ($48 a year) for two sites with custom domains, password protection and commercial use, and Starter is $10 a month for five. It hosts built React, Vue, Svelte, Vite and Astro output with a single-page app mode, _redirects, version history and GitHub builds on every plan.
The limits matter here. It runs no server code, so OxyPages is the wrong pick for a server-rendered Site. Its free plan is personal use only with no custom domain, which is smaller than Appwrite Free. It does build a preview link for every GitHub branch and pull request on every plan, public but hidden from search on Free and password-protected from Lite, so if your repo is on GitHub, previews come with it. If it's elsewhere, Netlify or Cloudflare fit better.
Moving The Front End And Keeping The Backend

Moving a static Site off Appwrite while keeping the backend takes about 30 minutes, plus DNS time. Here's the order I'd follow on any host.
- Check that the Site is static. If your build produces a
distorbuildfolder of HTML, CSS and JavaScript, you're fine. If it needs a running server, stop here and stay. - Copy your build variables. Your Appwrite endpoint and project ID usually live in variables like
VITE_APPWRITE_ENDPOINT. Set the same ones on the new host, because a Vite build bakes them in at build time. How Vite environment variables work explains the prefix rule. - Add a single-page app fallback. If you use client-side routing, add a rule that serves
index.htmlfor every path, or refreshing an inner page returns a 404. - Deploy and get the new address. Use the host's preview or default subdomain first, before touching your real domain.
- Register the new domain in Appwrite. In the Appwrite Console, add a Web platform with the new hostname. Appwrite's own guide says the hostname should be the domain where you host your web app, and skipping this step causes CORS errors. MDN's explanation of CORS covers why the browser blocks the calls.
- Test sign-in and data. Log in, load a page that reads from the database, and upload a file if your app does that.
- Move the domain, then delete the Site. Point your DNS at the new host, add that domain as a Web platform too, and remove the old Site so it stops counting against your plan.
What To Do Next
Open your Appwrite project and look at what the Site actually is. If it's server-rendered, or you love having one console, stay. Appwrite Sites does that well.
If it's a static build, decide what you're solving. For previews with unlimited teammates, Netlify Pro at $20 a month flat is the closest match. For a simple flat bill across a few static sites with custom domains, compare the plans and pricing and test one build on a free account first.
Either way, keep the backend where it is. For most teams the right move shifts only the front end and leaves the database alone.
FAQ
Is Appwrite Sites Free?
Sites is included on Appwrite's Free plan, but it isn't unlimited. Free gives 5 GB of bandwidth a month, one member and two projects, and free projects pause after a week of inactivity. Sites was free of usage limits only during its launch period, until 1 August 2025.
Can I Host My Front End Elsewhere And Still Use Appwrite?
Yes. A static front end can run on any host and call Appwrite's API from the browser. Add the new hostname as a Web platform in the Appwrite Console, or the browser will block requests with a CORS error.
How Much Does Appwrite Pro Cost?
Pro starts at $25 a month as of November 2026, with unlimited members, 2 TB of bandwidth and one project. Each additional project costs $15 a month, and bandwidth overage is $15 per 100 GB. There's no per-seat charge.
Does Appwrite Sites Support Server-Side Rendering?
Yes. Appwrite Sites runs server-rendered apps for Next.js, Nuxt, SvelteKit, Astro and Remix, as well as static sites. If your app relies on that, a static host won't work as an Appwrite Sites alternative, and Vercel or Netlify are the closer matches.