Customize a new Region

If existing Regions such as EU, NA, and Global cannot meet your business compliance requirements, Geelab supports evaluating and customizing new Regions based on customer needs.

Which situations are suitable for applying for customized Regions?

You can contact Geelab in the following scenarios:

• Relevant data must be stored and processed in designated countries or regions.
• Enterprises need to meet specific industry or internal data residency policies.
• The existing Region cannot meet the regional requirements in the customer contract.
• It is hoped that Geelab services will be deployed in the same area as the enterprise's existing business systems.
• Different countries or business lines need to use independent data areas.
• Have clear requirements for network latency, disaster recovery areas or service deployment.

What information do you need to provide when applying?

To complete the assessment faster, it is recommended to prepare:

• The country or region you wish to open.
• The main regions where business users are located.
• The type of data that needs to be processed.
• Data residency and cross-border transfer requirements.
• Deployment area for client server, database and Webhooks.
• Estimated monthly request volume and peak traffic.
• Platforms that require access: Web, iOS, Android.
• Required server-side API, Webhooks and risk signal capabilities.
• Data retention, deletion, backup and disaster recovery requirements.
• The desired opening time.

How to activate customized Region

Customizing a Region usually includes the following stages:

1. Submit a requirement: Explain the target area and compliance requirements to your Geelab account manager or support team.
2. Proposal Assessment: Geelab evaluates regional deployment, product capabilities, network, capacity and data processing requirements.
3. Scope Confirmation: Both parties confirm the supported platforms, APIs, Webhooks, data retention and service scope.
4. Business and Agreement: Confirm delivery time, service level and related agreements.
5. Deployment and Acceptance: Complete regional deployment, and verify access, data isolation and business links by both parties.
6. Officially activated: The Region appears in the agreed organization or account, and customers can create applications and start accessing.

Custom Region Description

Customizing a Region requires evaluation of the target region's infrastructure, product capabilities, traffic scale, and compliance requirements, so it is not an instant self-service operation in the console. The final support scope, deployment area, delivery schedule, service level, and price are subject to Geelab's formal plan and the agreement between both parties.

Customizing Regions can help enterprises meet regional deployment and data residency requirements, but it does not replace customers' own legal and compliance judgments. It is recommended that customers complete an internal review by a legal, security or privacy team prior to activation.