Python on Vercel Reaches General Availability With Native SDKs and Framework Support

Framework detection and runtime

Vercel says it reads a project's dependency files, including those managed by uv, and detects frameworks such as FastAPI, Flask, Django and FastHTML. The company describes this as framework defined infrastructure: it configures builds and request routing, with framework-specific support for serving static assets through the CDN.

The runtime uses CPython, the standard Python interpreter, on Linux. Vercel says this is meant to preserve compatibility with the packages and tools Python developers already rely on. It also supports uv and pyproject.toml for dependency management, according to the changelog.

Applications run on Fluid compute, which manages concurrent requests and scales with traffic. For long-running workers that pull jobs from queues or databases, Vercel Daemons keeps containers running with the Python code, its packages and any system dependencies.

Python SDKs for Vercel infrastructure

Vercel has built a set of Python SDKs that it says follow the conventions of the language, including type annotations, async / await and context managers. The company lists the following:

• AI SDK for Python: generate and stream model responses, call tools and build agents. The changelog marks it as Beta.
• Sandbox SDK: create and control isolated environments for running code.
• Workflow SDK: define durable workflows with retries and saved execution state. Listed as Beta in the changelog.
• Queues SDK: send and receive messages for background work and notifications. Listed as Beta in the changelog.
• Blob SDK: upload and retrieve files in object storage.
• Connect SDK: obtain credentials for calling external APIs.

The SDKs can be used individually or combined in the same application, and they work alongside the chosen framework and libraries.

One workflow for frontend and backend

Many Python applications include a JavaScript frontend. Vercel Services brings both parts into one project, with shared previews and atomic deployments and rollbacks. Running vercel dev starts both locally, and logs can be viewed by service. Backends can be connected privately through service bindings.

In the changelog example, a frontend in frontend/ and a FastAPI app in backend/main.py are wired together with a vercel.toml file at the repository root. Requests under /api/ reach the matching FastAPI routes with the path unchanged, while other requests go to the frontend.

A demo application

To show how the pieces fit together, the author of the announcement built a collaborative web application for creating and browsing Python notebooks. It pairs a Vite frontend with a FastAPI backend and uses PostgreSQL for notebook source and chat history.

When a signed-in user opens a notebook, FastAPI creates or reuses a Vercel Sandbox running Jupyter, which keeps user code isolated from the backend. Published notebooks are rendered as HTML and uploaded to Blob, so they can be read through the CDN without starting a Python kernel. After a change is published, FastAPI sends a message through Vercel Queues, and backend instances push updated listings to browsers over WebSockets. An AI assistant built with AI SDK for Python runs inside Vercel Workflows, which saves execution state and retries failed steps. The source code is available on GitHub.

Community investment and what comes next

Vercel says the Gel Data team, led by the article's author and Elvis Pranskevichus, joined the company last December to build Python support. At the same time, Vercel announced sponsorship of the Python Software Foundation and committed to funding one year of Serhiy Storchaka's CPython maintenance. According to the company, Serhiy has authored over 600 commits to CPython's main branch so far in 2026. Vercel also sponsored PyCon US and EuroPython and published PEP 827, which, if accepted, would add type manipulation features that could help frameworks such as FastAPI offer simpler APIs with less boilerplate and more precise type checking.

For developers, the release means Python backends can be deployed on Vercel alongside a JavaScript frontend using a single workflow. Vercel says it will keep improving the Python SDKs, runtime performance and development workflows for both people and coding agents, and asks users to share deployment issues or missing SDK features in Vercel Community.