Python Projects Now Support Routing Rules on Vercel

What shipped? Vercel extended its routing rules system — redirects, rewrites, headers, and middleware — to Python projects.

What changed? Previously, routing rules via vercel.json were effectively a Node.js/frontend-framework feature. Python deployments (Django, FastAPI, Flask) had to handle URL mapping at the application level. As of August 26, any Python project deployed on Vercel can use the same vercel.json routes, redirects, rewrites, and headers configuration that JavaScript projects have always had. That includes pattern-based matching, header-based routing, and geolocation-aware rules.

Why a builder cares: If you're running a Python API or site on Vercel, you can now handle redirects, A/B testing splits, and security headers at the platform layer instead of in your app code. One less thing for your Python framework to do, and one unified config file for the whole deployment.