Exalate launches Australian hosting for cloud connector

Exalate has launched Australian hosting for Exalate Cloud on Google Cloud in Sydney. The option is available across all its cloud connectors.

The move was prompted by an Australian enterprise migration project that required the integration layer to be hosted locally before work could proceed. The Sydney deployment is already supporting that migration, which connects ServiceNow and Jira Cloud.

The launch gives organisations in Australia the option to run Exalate's integration service in-country while linking systems such as Jira, ServiceNow, Azure DevOps, Salesforce and Freshdesk. The hosting location applies to Exalate Cloud itself, rather than to every system connected through it.

That distinction matters for companies assessing data location and operational risk across their technology estates. If one connected system sits outside Australia, the information exchanged with it will still leave the country, even if the integration is hosted in Sydney.

Migration need

The immediate trigger was a migration introduced through an implementation partner. Australian hosting was a prerequisite for the customer, and without it the migration could not proceed.

In phased technology changes, organisations often keep old and new platforms running in parallel while teams move in stages. Exalate is used to synchronise selected records and updates between those systems so staff can continue working in their existing tools during the transition.

This approach is particularly relevant in projects spanning several departments, suppliers or separate organisations. Each party may use different workflows, labels and rules for the information it shares, which can complicate a migration or long-running integration.

Exalate said its service supports bidirectional synchronisation while allowing each side to decide what information is shared and how it is mapped into the receiving system. It argues that the location of the integration service has become a separate point of scrutiny, even where the linked applications already meet local hosting requirements.

Regulatory context

Exalate pointed to growing attention on Australian privacy obligations and operational resilience requirements. It cited APRA's CPS 230 standard, which places greater weight on operational risks tied to service providers and offshore arrangements.

For regulated companies, that can broaden the review beyond the main business applications to include the infrastructure that moves data between them. In practice, a project may satisfy hosting rules for the systems at either end, but still face questions about the integration layer carrying information across environments.

Jira Cloud already offers Australian data residency for eligible data, according to Exalate. But local hosting for a core application does not automatically address where the integrations connected to it are running.

This issue can become more visible in large migrations, where teams need to maintain a shared view of work across old and new systems for an extended period. Service management, engineering and external providers may all remain in separate environments while records continue to move between them.

Local option

The Australian region expands Exalate's deployment choices for cloud customers of any size. Existing users can request a move to the Sydney region, while new users can choose the local hosting option when they start using the service.

Francis Martens, Co-founder at Exalate, said the company acted after a customer project made local hosting non-negotiable. "Hosting location is often the deciding factor in whether a platform can be used at all," Martens said. "A migration that couldn't proceed without local hosting settled it for us. Australian teams needed the integration itself to run in-country. Now it can."