Executive Summary
Vercel has introduced project-level routing rules, a new feature enabling developers to create and update CDN-level routing configurations, such as response headers and rewrites, without initiating a new deployment. These changes take effect instantly and can be managed through the dashboard, API, CLI, or Vercel SDK. This feature is now available on all plans, designed to make routing adjustments more efficient and decoupled from the build process.
Key Takeaways
* New Feature: The ability to define "Project-level routes" is now available.
* No Redeployment Required: Routing rules can be created and updated instantly without triggering a new build and deployment.
* Capabilities: Users can configure settings like response headers and rewrites to external APIs.
* Management Tools: The feature is accessible via the project dashboard, Vercel API, CLI, and SDK.
* Execution Order: Project-level routes execute after bulk redirects but before routes defined in the deployment configuration (e.g., `vercel.json` or `next.config.js`).
* Availability: The feature is available immediately on all Vercel plans.
Strategic Importance
This update decouples infrastructure configuration from application code, improving developer agility by allowing for rapid, non-disruptive changes to CDN behavior.