megachangelog
Announcement

Python on Vercel is now generally available

Python is now generally available on Vercel, allowing you to build and run Python applications with automatic framework detection, full-stack development capabilities, and idiomatic Python SDKs for storage, queues, workflows, and AI integration. Your applications run on Vercel's Fluid compute platform with shared development and deployment workflows for Python backends and JavaScript frontends.

Python on Vercel is now generally available. Build and run Python applications with the frameworks, libraries, and tools you already use.

Vercel automatically detects supported frameworks and configures the build and deployment. Your applications run on Fluid compute, which manages concurrent requests and scales with traffic. Idiomatic Python SDKs let you work with storage, queues, durable workflows, and AI models directly from Python. For full-stack projects, the Python backend and frontend share a workflow for local development, preview deployments, and production releases.

Ten months ago, we . We wanted the experience to fit how Python developers already work, with three goals guiding our decisions:set out to make Vercel the best place to build and run Python applications

The first test of those goals is what happens when you deploy a Python application on Vercel: its framework, dependencies, and project structure should guide how it’s built and run.

We’ve worked to make Python feel native on Vercel. Vercel reads your project’s dependency files, including those managed by , and automatically detects frameworks such as FastAPI, Flask, Django, and FastHTML. configures builds and request routing, with framework-specific support for serving static assets through the CDN.uvFramework defined infrastructure

For applications with a frontend, brings both parts into one project. Running starts them together, and shared previews let you test backend changes with the frontend that uses them.Vercel Servicesvercel dev

For long-running workers that pull jobs from queues or databases, keeps your containers running with your Python code along with any of its packages, and system dependencies.Vercel Daemons

A Python backend might need to store files, send messages, run durable workflows, or call AI models. We’ve built Python SDKs for these tasks, with APIs that follow the conventions of the language:

These SDKs work alongside your framework and libraries, and the example below shows how they connect within a full-stack application.

Whether you’re starting a new project or deploying existing code, the cover setup and deployment on Vercel. For a guided full-stack project, the walks through building a FastAPI backend and Next.js frontend, then deploying them together with Services.framework guidesPython on Vercel course

To show how these pieces work together, I built a collaborative web application to create and browse Python notebooks. It lets people create their own notebooks, publish them for others to browse or fork, and work with an AI assistant to write and run Python code.

The application pairs a Vite frontend with a FastAPI backend and uses PostgreSQL for notebook source and chat history. Services keeps the frontend and backend in one deployment, with the frontend served through the CDN.

Here’s how the main parts connect:

The includes the complete application and its deployment configuration. You can use it to explore these integrations or as a starting point for your own Python application.source code on GitHub

Last December, the Gel Data team, led by me and Elvis Pranskevichus, to build Python support and continue our open-source work.joined Vercel

At the same time, we announced our sponsorship of the Python Software Foundation and committed to funding one year of Serhiy Storchaka’s CPython maintenance through the foundation. Serhiy has authored over 600 commits to CPython’s main branch so far in 2026.

We also sponsored PyCon US and EuroPython this year, where the team and I met Python developers and heard where they were getting stuck. Those conversations help us figure out what to fix next.

We also published , 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.PEP 827

We’re continuing to improve Python SDKs, runtime performance, and development workflows for both people and coding agents. If you run into a deployment issue or find something missing in the Python SDKs, so the team can use it to guide that work.share your feedback in Vercel Community

Read more

Our goals for Python on Vercel

Deploying Python applications on Vercel

Python SDKs for Vercel infrastructure

Start building with Python on Vercel

Investing in the Python community

What’s next for Python on Vercel

  • Working with Vercel infrastructure should feel familiar to Python developers, with APIs that use type annotations, /, and context managers.Idiomatic Python SDKs.asyncawait

  • Python applications often include a JavaScript frontend, so developers should be able to run both locally, review them in the same preview deployment, and release or roll them back together.A shared workflow for both the frontend and backend.

  • The runtime should use CPython, the standard Python interpreter, on Linux to preserve compatibility with the packages and tools Python developers already rely on.Compatibility with the Python ecosystem.

  • When a signed-in user opens their notebook in the editor, FastAPI creates or reuses a Vercel Sandbox running Jupyter, keeping user code isolated from the application backend. The browser connects directly to Jupyter, while mounted Drives provide the Python dependencies and workspace files.Editing and running code:

  • The browser periodically sends the current notebook to FastAPI. FastAPI saves the source in PostgreSQL, renders changes as HTML, and uploads the result to Blob, so people can read published notebooks through the CDN without starting a Python kernel.Saving and publishing:

  • After publishing a change, FastAPI sends a message through Vercel Queues. Each backend instance with connected browsers receives the notification and sends updated notebook listings over WebSockets, so people see changes without reloading.Sharing updates:

  • The agent uses AI SDK for Python and runs inside Vercel Workflows, which saves execution state and retries failed steps. Chat history stays in PostgreSQL, while notebook editing and execution tools work through the connected browser, which sends results back through FastAPI to resume the workflow.Assisting with code:

Resources

pythongeneral-availabilityframeworksfull-stackdeployment

Source: original entry ↗

More from Vercel

Follow Vercel to get its new changes in your feed and email digest.

Announcement2026.10.19

Updates to Hobby and Pro Terms of Service

Vercel is updating Terms of Service for Hobby and Pro customers effective October 19, 2026, clarifying credit policies, managed accounts, auto-renewal practices, and adding statutory cancellation and refund rights for UK and EU consumers, including protections for service changes with negative impact.

termsbillingcreditspolicylegal
Announcement

Mercury 3 now available on AI Gateway

Inception's Mercury 3 model is now available on Vercel's AI Gateway with 50% launch pricing and generation speeds exceeding 1,000 tokens per second. The model enables parallel text refinement with a 1M-token context window, ideal for real-time applications like browser agents and customer support.

ai-gatewaymodelsinferencellmlaunch
Announcement

MiniMax M3.1 Flash now available on AI Gateway for free

MiniMax M3.1 Flash, an open-weight multimodal model with 1M-token context window for coding and agentic work, is now available on Vercel's AI Gateway at no cost through October 20. The model excels at complex agent tasks, coding applications, and cybersecurity work, and can be used through multiple APIs and coding agents.

ai-gatewaymodelscodingagentsapi
See all Vercel changes →