Python projects now support routing rules
Python projects can now use routing rules to set response headers or rewrite requests to internal paths. Rules are evaluated by the Vercel CDN before requests reach your application and take effect immediately without requiring a new deployment.
Python projects can now use to set response headers or rewrite requests to internal paths, including apps built with FastAPI, Django, and Flask.routing rules
The evaluates rules before requests reach your application, so changes apply without a new deployment.Vercel CDN
For example, this FastAPI app serves a route:/new
To send requests for to that route, create a rewrite from the CDN tab in your project dashboard or with the :/oldVercel CLI
Published rules take effect immediately across all regions, and you can roll back to a previous version from the History tab.
You can also manage rules from Python with the , which wraps the . stages the rule, and publishes it: SDKvercelVercel REST APIadd_routeupdate_route_version
Rewrites can also be defined in :vercel.json
Project-level rules live outside your deployment and are evaluated before its routes, so a published rule takes precedence over a rewrite for the same path. Each surface fits a different workflow:vercel.json
Update Vercel CLI to the latest version and read the to get started.routing documentation
How you define it | Takes effect | Best for |
|---|---|---|
CDN tab in the dashboard | On publish | Editing and testing rules visually |
Vercel CLI | On publish | One-off changes from the terminal |
Python SDK or REST API | On publish | Automation and CI/CD |
| On each deployment | Rewrites that ship with the application code |
Source: original entry ↗