Hobby customers can now select their preferred region for Serverless Functions

Deploying your Serverless Functions in a region close to your data can greatly improve performance by reducing latency.

Previously, Hobby customers could only choose US East (iad1) regardless of where their data was hosted. Starting today, all plans can co-locate their Functions with their data for lower latency when server-rendering with hybrid frameworks like Next.js, SvelteKit, and more, or when using API Routes.

Check out the documentation as well.