Key Updates
Go API backends no longer need custom `vercel.json` redirects or the `/api` folder convention to deploy correctly. Vercel automatically provisions resources and configures the app path for Go servers. The release also defaults these backends to Fluid compute with Active CPU pricing, so scaling is tied to traffic and active compute rather than idle capacity.
What Developers Need to Know
This lowers the deployment overhead for Go teams that want a simple platform path instead of managing runtime glue. It also makes Vercel a more realistic option for lightweight backend services, not just frontend apps. From a cost standpoint, Active CPU pricing should be attractive for spiky workloads because you pay for active work instead of idle reservation.
How to use it or Next Steps
If you already deploy Go services, test one endpoint on Vercel and compare the operational simplicity against your current setup. Watch for cold start behavior, latency, and traffic-based billing. For new projects, this makes it easier to keep the stack compact and let the platform handle the first layer of infrastructure.