Skip to content

Three regions. One standard.

Altuon’s registered address is in Turin, Italy. These regions describe the markets in which we discuss proposed work; they are not office locations. Availability, working hours, language support and delivery arrangements are confirmed for each engagement.

Where Altuon works: the registered office in Turin and the cities of its three regions, at their true coordinates, with the three working time zones

Service regions

Europe and DACH

Registered office

Turin, Italy

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.

Regions

Europe and DACH

For organisations in Switzerland, Germany, Austria and the wider European market, the initial discussion covers data location, language, procurement and the operating environment. A regulated mandate also needs a documented view of the applicable supervisory requirements. Hosting options, sub-processors and responsibilities are assessed for the specific system. Our registered office is in Turin; additional locations are published only when confirmed.

Working languages
German, French, Italian, English
Working hours
Central European Time, 08:00 to 18:00
Hosted in
Switzerland (Zürich), European Union (Frankfurt)

Middle East and North Africa

For organisations in the Middle East and North Africa, the discussion starts with Arabic readiness, decision-making responsibilities and data requirements. A voice system may need evaluation in several dialects; a public-sector programme may require a specific hosting model. These are questions for the proposed architecture and delivery team. On-site work, travel and local partners are agreed in the proposal, without implying a permanent regional office.

Working languages
Arabic, English
Working hours
Eastern European Time in Amman, Sunday to Thursday, 09:00 to 18:00
Hosted in
Bahrain, United Arab Emirates, On-premises in Jordan

North America

For North American organisations, the discussion covers integration, scale, procurement and the relevant federal, state or sector requirements. The system's data flows and control owners are documented before implementation. Working hours and support coverage need an explicit agreement, particularly when several time zones are involved. The regional contact route supports that discussion; it is not a claim of a New York office.

Working languages
English
Working hours
Eastern Time, 09:00 to 18:00
Hosted in
United States (Virginia), United States (Oregon)

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

Tell us which region, and we will answer in its language.

Add your region, working language and time-zone requirements to a short proposal request. We can then discuss the appropriate delivery arrangement and commercial terms.