Application performance depends on latency. When your backend is geographically close to your users, API calls respond sooner and real-time updates arrive with less delay.
Ulabase lets you choose the region where your backend runs, so your API is close to your users.
Available Regions
Free, Starter and Pro
Free, Starter and Pro services are available in two regions.
EU Central 1 is in Frankfurt, Germany, in AWS region eu-central-1. It is the best location for European users and for applications that require GDPR compliance.
US East 1 is in Northern Virginia, USA, in AWS region us-east-1. It is the best location for North American users and for applications that require US data residency.
Choose the region closest to most of your users when you create your service.
Enterprise
An Enterprise service runs on dedicated nodes, in the AWS region you choose.
All European regions are available, including Frankfurt, Ireland, Paris, Stockholm, Milan, Spain, and Zurich. All US regions are supported: Virginia, Ohio, California, Oregon, and GovCloud. Asia Pacific regions include Tokyo, Seoul, Singapore, Mumbai, Hong Kong, Jakarta, Osaka, and Melbourne. South America has São Paulo. The Middle East has Bahrain and UAE. Africa has Cape Town. Canada has Montreal.
You can choose a region for several reasons: to be close to your users for low latency, to meet data residency requirements under GDPR or other regulations, to integrate with existing infrastructure in a specific location, or to satisfy the regulatory needs of your industry.
Why Region Matters
Latency Impact
Network latency grows with geographic distance. A request within the same region has the lowest latency. A request within the same continent takes longer, and a request across continents takes the longest.
A typical web application makes several API calls per page, so the difference adds up on every page. With the backend on another continent, users notice the delay.
Real-World Impact
Consider a European application. With a backend in the EU, each API call stays within the continent. With a backend in the US, every call crosses the Atlantic and back. European users get faster responses from the EU backend.
For a global application the strategy changes. With Enterprise nodes in several regions, users can be routed to the nearest backend. Every user then has a backend nearby, wherever they are.
Compliance and Data Residency
Some applications have legal requirements about where data is stored, and these decide the region.
Under GDPR, many European applications need to keep user data in the EU. An EU region keeps the data there.
Data sovereignty requirements in some countries mandate that data be stored locally. A local region satisfies them.
Industry regulations in healthcare, finance, and government often have specific residency requirements. With Enterprise you choose a region that meets them.
Choosing Your Region
For Free, Starter and Pro
Two questions guide your decision.
First, where are most of your users? If they're primarily in Europe or Africa, choose EU Central 1. If they're primarily in the Americas, choose US East 1. For a global mix, choose based on your larger user base or where you expect the most traffic.
Second, do you have compliance requirements? GDPR or EU data residency requirements point to EU Central 1. US data residency requirements indicate US East 1.
For Enterprise
Several factors influence your decision.
Consider the distribution of your users. For a single-region deployment, choose the location closest to them. To serve users globally with low latency, run nodes in several regions.
Compliance often determines the region. Data residency requirements, regulatory mandates, and industry standards all limit where data can be stored and processed.
Integration requirements matter when you connect to other services. Consider where those services are located, where your existing infrastructure is deployed, and where partner systems are hosted.
Cost can influence the choice as well. Data transfer costs between regions vary, and bandwidth costs add up when integrated services are far apart.
Multi-Region Deployment
On Enterprise, a deployment can grow to several nodes in one region or many, with Atlas shards where your users are. Users everywhere then have a backend nearby.
We design the layout with you: which regions, how many nodes, and where the data lives.
The benefits are these. Users have low latency wherever they are. A second region is a backup if one region has problems. You can comply with multiple jurisdictions by keeping data in the appropriate regions. The load is distributed, and there is a fallback.
The costs are these. Operations are more complex with several deployments, and the price follows the design.
Request a Region
If your preferred region is not offered for Free, Starter and Pro, tell us. We add regions based on user feedback.
Write to support@ulabase.com to request a specific region, discuss regional needs, or share your use case. Your feedback helps us decide where to expand next.
Region Selection When Creating Services
Free Service
When you create a Free service, you select the region during the creation process. Choose the Free plan, pick EU Central 1 or US East 1, and the service is provisioned in that region.
Starter and Pro Services
The process is the same for Starter and Pro: choose the plan, select the region, pay through Stripe Checkout, and the service is provisioned there.
Enterprise Service
Choose Enterprise when you create a service: the console opens a form to our team. Tell us the AWS region you want, and we set the service up there.
Performance Tips
Choose Wisely
The region is selected when the service is created and cannot be changed later without a migration. Choose it based on your users and your long-term plans.
Monitor Performance
Use your application monitoring to track API response times from different user locations. The data tells you whether the region is the right one and whether a multi-region deployment would help.
Consider CDN
For global applications, use a CDN for static content, while Ulabase handles API calls from regional backends. This covers both content delivery and API performance.
Test Before Deciding
On Free, you can create test services in both regions and measure performance from your actual user locations. The measurement replaces the guess.
For Enterprise, talk to our team: we can help you choose regions based on your user distribution and requirements.
Migration Between Regions
To move an existing service to a different region, the process depends on your plan.
On Free, Starter and Pro, create a new service in the region you want. In its Settings, under Bring data into this service, click Contact support: we copy the data, the configuration and, if you want, the users. Then point your application to the new address and delete the old service.
On Enterprise, talk to our team about the move.
Regional Pricing
Free, Starter and Pro cost the same in both regions: €0, €9 and €25 a month.
Enterprise is priced on its design, and the regions are part of that design.
Get Started
Free, Starter and Pro
Create your service now at https://ulabase.com/new-srv and select your region during setup. The process takes less than a minute.
Enterprise
Choose Enterprise when you create a service, and tell us your preferred regions and use case in the form.
Build your app on Ulabase
Your backend is ready in minutes, and you spend your time on your app. The Free plan needs no credit card.