vercel-services

Use Vercel Services by defining experimentalServices in vercel.json with an entrypoint and routePrefix for each service. Set the project Framework Preset to Services in the dashboard, then deploy both services under one domain.

Set the service entrypoint to your application file such as backend/main.py and assign a routePrefix like /api. Dependencies go in pyproject.toml in the service directory, and the framework is auto-detected.

Yes, Go services are supported and production-ready. Set entrypoint to the service directory rather than a file, and you must explicitly set "framework": "go" in vercel.json because auto-detection does not work for Go.

A 404 usually means the project Framework Preset is not set to Services. Go to Project Settings, then Build & Deployment, select Services from the Framework Preset dropdown, and redeploy.

No, Vercel strips the routePrefix before forwarding requests, so handlers declare routes without it. For example, a service mounted at /api defines a /health route, while other services call it at /api/health.

Services is in beta, with only Python and Go tested and production-ready. Node.js, Bun, Rust, Ruby, Wasm, and Edge runtimes may work but are not yet validated, and unknown vercel.json fields cause build failures.