What is the same everywhere.
The five-phase delivery system, the architecture register, the evaluation discipline and the security posture do not vary by region. A Swiss bank and a Jordanian ministry receive the same gates, the same evidence and the same written residency position. This is deliberate: a firm whose standard changes with the client's postcode has no standard.
What varies is language, operating context and the requirements of the engagement. Your proposal identifies the working language, time-zone overlap, currency and any local expertise required. The regional notes on industry pages explain the questions to resolve; they do not imply an office or a permanently staffed team in every market. You can add a region in the proposal form's optional details.
How a regional engagement is staffed.
Staffing follows the scope. The proposal names the accountable lead, the required disciplines and the responsibilities retained by your organisation. It also sets out which work is remote, which needs an on-site presence and whether a local specialist is required. Travel and additional coverage are identified as commercial items before the engagement begins.
Time-zone overlap is planned around the people who need to make decisions and operate the system. Meeting windows, escalation routes and response commitments are agreed for the engagement. The reference hours on this page help start that conversation; they are not a contractual support commitment or a guarantee of round-the-clock availability.
Where data may live.
Hosting is chosen for the system and recorded in its architecture documentation. The regions listed here are options to assess, not a promise that every product is already deployed there. On-premises or sovereign-cloud requirements need a compatibility review. Before data is processed, the parties agree the hosting location, access controls, sub-processors and any cross-border flows; the trust page explains the questions this review addresses.
Read the trust page