What happened
I created a Neon project without explicitly confirming the region and it defaulted to aws-us-east-1. I needed EU data residency (Frankfurt, aws-eu-central-1) and didn't notice for about a week, since the region doesn't surface anywhere in application code or .env files, only in project settings or neon projects list output.
Why this is costly
A project's region is fixed forever at creation; there's no "move region" operation. Fixing it meant creating an entirely new project and migrating data across, rather than changing a setting. For anyone with GDPR or other data-residency requirements, missing this once is expensive, and today there's no prompt, confirmation step, or CLI flag requirement that surfaces the choice before it's locked in.
What I'd like to see
neon projects create (CLI) could print a one-line confirmation of the chosen region before creating the project, and/or require --region to be passed explicitly rather than silently defaulting to one.- The console's "Create project" flow could make the region selector more prominent, with an explicit note that it cannot be changed later.
- The MCP server's
create_project tool could do the same: echo back the region used, or require it as an explicit parameter without a silent default.
This is easy to miss once and expensive to fix after the fact, since it isn't a config value, it's account-level state invisible to the repo.
What happened
I created a Neon project without explicitly confirming the region and it defaulted to
aws-us-east-1. I needed EU data residency (Frankfurt,aws-eu-central-1) and didn't notice for about a week, since the region doesn't surface anywhere in application code or.envfiles, only in project settings orneon projects listoutput.Why this is costly
A project's region is fixed forever at creation; there's no "move region" operation. Fixing it meant creating an entirely new project and migrating data across, rather than changing a setting. For anyone with GDPR or other data-residency requirements, missing this once is expensive, and today there's no prompt, confirmation step, or CLI flag requirement that surfaces the choice before it's locked in.
What I'd like to see
neon projects create(CLI) could print a one-line confirmation of the chosen region before creating the project, and/or require--regionto be passed explicitly rather than silently defaulting to one.create_projecttool could do the same: echo back the region used, or require it as an explicit parameter without a silent default.This is easy to miss once and expensive to fix after the fact, since it isn't a config value, it's account-level state invisible to the repo.