Hi Vercel team,

I'm experiencing a persistent deployment issue with a Next.js application on the Hobby plan. The application builds successfully, but Vercel rejects the deployment with:

exceeded_serverless_functions_per_deployment

Project: victory-design-studio-staging

Most recent failed deployment: dpl_8QsGbz6NsyNrknxBhqr1zefYcq9d

Last successful deployment: dpl_5248LPwnjVdEreaKaVvysn7sBgtG

The last successful deployment contained 8 functions. Since then, we've added seven new routes for a rendering and project-review feature.

What we've investigated:

• The Next.js build compiles successfully.
• We have tried a deployment with --force, completely bypassing the build cache.
• We collected actual trace sizes from Vercel's Linux build environment.
• Only six routes exceed the builder's 225 MB function-isolation threshold.
• The new rendering POST route traces approximately 319 MB and should become one additional function.
• The other six new routes trace only 2–3 MB each and should join existing function groups.
• Local analysis using Vercel's builder logic predicts approximately 9–10 functions, below the Hobby limit of 12.
• The deployment still fails at the patchBuild stage with the same function-limit error.

We have reproduced the previous successful deployment's function structure locally, but the rejected deployment doesn't expose its function count or membership list.

Could someone from Vercel please help us determine:

1. How many Serverless Functions Vercel actually counted for the failed deployment?
2. Which routes or function groups contributed to that count?
3. Whether middleware or another deployment artifact is counted differently from the local builder?
4. Whether this is a function-packaging issue or a platform limitation?
5. Whether there's a way to resolve this on Hobby without removing application features?

We've completed several rounds of diagnostics and don't want to make speculative changes to the application.

Any guidance would be greatly appreciated. Thank you!