Short answer
Forge runs your app in-region, close to the people who actually use it. That is the design, not an upgrade you configure later — the platform is built for this region from the ground up.
Why distance is a feature
Every request your app handles is a round trip. If your users are here and your server is not, every tap of every button crosses an ocean and back before your code even runs. Pages feel slow in ways no amount of clever code fixes, because the problem is geography.
When the app runs close to your users, pages load the way they are supposed to. Forms confirm instantly. Dashboards feel live instead of sluggish. That difference is usually what separates an app people trust from an app they tolerate.
Where your data lives
By default, data stays in the region where it was collected. For a business serving local customers, that matters twice: your customers' records are not silently crossing to another continent, and the conversation with anyone who asks where data goes — a client, a bank, an auditor — gets much simpler.
What ships on by default
Authentication, access control, and encryption are on by default. Your app starts with the baseline a real business needs before it shares a login with anyone outside the team, and none of it is configuration homework.
If a contract needs specifics
If a client or regulator needs exact infrastructure or region details in writing, confirm those details before you deploy rather than after. It is a five-minute question that is much easier to ask before launch.
The takeaway
Choosing where an app runs is really choosing who it is fast and safe for. Forge optimizes for your users and their data staying close to home — if that matches who you are building for, everything else about the stack follows from it.
Related reading: What does it cost to run an app on Forge? and How to move an existing app to Forge.