If your team writes Python and needs an API next to the website, for bookings, a price calculator or reports, this is for you. Vercel will run FastAPI with almost no setup. Whether it should depends on five limits, and you can check them before anyone moves a file.
What does Vercel do with a FastAPI app?
It runs the whole app for you, with no server to size or patch, and scales it with traffic. Technically, it turns the app into one Vercel Function. Vercel looks for a FastAPI instance named app in app.py, index.py, server.py, main.py, wsgi.py or asgi.py, and the function runs on Fluid compute by default, so it scales with traffic. Python 3.12 is the default, with 3.13 and 3.14 available.
Files in a public/ folder are served from Vercel's CDN, not the function. Since a recent change, frontends and static folders mounted inside FastAPI can be served from the CDN too.
Which five limits decide it?
These five, all from Vercel's docs read on 16 October 2026.

The first one catches most owners. A Python team used to its own server rarely thinks about upload size until a customer sends a scanned 12-page document and gets an error.
Which files skip your login checks?
Anything served from the CDN. Vercel's FastAPI docs say CDN-served files "bypass the function entirely", so middleware and Depends() guards do not run for them.
Vercel guards against the obvious mistake. When your app has top-level middleware, or a frontend with a Depends() guard, it keeps those files in the function. Two things undo that protection:
- 01Setting cdn = true in pyproject.toml. Vercel then serves the files from the CDN even when guards exist.
- 02Putting files in public/. Vercel serves that folder from the CDN at the platform level, with no check at all.
Keep anything private, such as reports, invoices or patient papers, in storage that your API hands out after a login, never in public/.
What does it cost, as of 16 October 2026?
Vercel Pro is USD 20 a month with one deploying seat and USD 20 of usage credit. Extra deploying seats are USD 20 a month each, and viewer seats are free. Above the credit, functions are metered: USD 0.128 per Active CPU hour and USD 0.0106 per GB-hour of memory (USD 0.14 and USD 0.0116 in Mumbai), plus USD 0.60 per million invocations. Active CPU is not charged while your code waits on a database or another API, though memory still is. New teams get a default on-demand budget of USD 200.
In one line: USD 20 a month for each deploying seat, and well under a dollar of usage for the sample below, inside the included credit. Our arithmetic for the clinic below, from list prices at Mumbai rates, not a measured bill. Assume 50,000 API calls a month, each 30 ms of Active CPU while the rest is database wait, and 2 GB held for 300 ms. That is 0.42 CPU hours (USD 0.06), 8.3 GB-hours (USD 0.10) and USD 0.03 of invocations: about USD 0.19, inside the USD 20 credit.
We are not a Vercel partner and earn nothing from your Vercel bill. Our own site runs on Netlify. What stays portable: a FastAPI app is a standard ASGI app that runs in any container. What is Vercel's: the pyproject.toml tool.vercel settings, vercel.json services and the CDN promotion.
The free Hobby plan is for non-commercial, personal use only, so a business API belongs on Pro. Your database and file storage are billed separately.
If the website and the API should live together, Vercel's Services, in beta on all plans, puts both in one project. You declare a Next.js frontend and a FastAPI backend in vercel.json, and rewrites send each path to the right one.

What would we do for a clinic?
Take a sample outpatient clinic in Dubai with a booking website and a small Python team that wants patients to upload lab reports and read results online. This is an illustration, not a client story.
- 01Put the website and the FastAPI backend in one project with Services, so one preview link shows both.
- 02Send lab report uploads straight to storage with a short-lived upload link, so no file passes through the 4.5 MB limit.
- 03Keep results out of public/ and serve each one through the API after the patient logs in.
- 04Check where the storage and database keep their data. There is no Vercel region in the UAE or Saudi Arabia; Mumbai (bom1) is the nearest.
- 05Move the nightly report that reads a month of bookings into a queue, so it never races the run-time limit.
- 06Have the clinic manager approve every change on its preview link before it goes live.

Patient records carry their own rules on where data is kept. Settle those with your compliance lead before choosing any host. See how we work with clinics, and Mindcat Clinic if you would rather not build the patient side at all.
What goes on the security questionnaire?
Vercel splits the answers in its shared responsibility model, read on 16 October 2026. Here is who writes each line.
If a contract says data must be processed inside the UAE, Vercel cannot meet it today. Say so before you sign, not after.
For a bad month, set Spend Management. Vercel sends alerts at 50%, 75% and 100% of the amount you set, and pauses production when you reach it if Pause Production Deployments is on. A budget alone does not stop usage, and the check can lag by several minutes. If a change breaks the site, Instant Rollback on Pro returns production to any earlier production deployment from the dashboard; environment variable changes are not rolled back with it. Vercel offers a HIPAA business associate agreement on Pro for USD 350 a month, which matters for US patient data; UAE health data rules are a separate question for your compliance lead.
Vercel or a server of your own?
Here is the rule we use.
If your Python team already runs the API on a server it knows, and nothing about it is hurting, leave it there. This post is for teams choosing where a new or moving API should live.
What happens on the first call?
We call the method Preview every change: each change gets its own preview link, someone on your side approves it on a phone, then it goes live, and any release can be rolled back. Send us the repository and tell us what the API does and who uses it. The written assessment is free and checks your app against each limit above. The first build week is a fixed AED/SAR 14,900, and a Run plan keeps the site and the API patched afterwards. More on how we build and run apps is on our Vercel page.

