Google Cloud: infrastructure, data and AI for financial firms

Google Cloud supplies infrastructure, data platforms, AI and security services used by financial institutions and market operators. Its capital-markets proposition includes quantitative research, portfolio and risk analysis, operational automation and exchange infrastructure. These are technology components that firms assemble around their own applications, data arrangements and market access.[1]

Gemini Enterprise for Financial Services was announced in preview on 25 August 2026. The offering combines a Google-managed Financial Research agent, reusable financial skills, source citations and financial-data connectors. It can be used in the Gemini Enterprise application or connected through Agent-to-Agent APIs. The launch identifies Deutsche Bank as a design partner; that relationship does not establish completed deployment of every described workflow.[6]

BigQuery supports structured and unstructured information and open table formats including Apache Iceberg, Delta and Hudi. SQL/Python analytical workflows therefore sit alongside ingestion and governance choices; the same data model must support both human analysis and downstream applications. The documentation’s current catalogue name is Knowledge Catalog.[3]

Cloud Interconnect provides dedicated, partner-operated and cross-cloud network routes. Traffic avoids the public internet, but the service does not encrypt it by default. Supported MACsec circuits or HA VPN over Interconnect add encryption. Published 99.99% and 99.9% uptime options depend on the prescribed critical-production or non-critical-production connection configuration; an unqualified connection group can have no SLA. These are network-service terms, not an end-to-end trading latency commitment.[7]

The financial-services Gemini connectors use Model Context Protocol and retain the customer’s existing source entitlements. The announcement names financial-data providers such as FactSet, LSEG and S&P Global. Their inclusion supplies a connection path, while the licensed information remains subject to its existing access rights. Google also states that this offering’s customer data and model outputs are not used to train or fine-tune its foundation models.[6]

Eligible new customers can receive US$300 of trial credit for 90 days. Eligibility excludes customers who have previously paid for the specified Google services or taken the trial. Upgrading enables paid usage; remaining trial credit keeps its original expiry. Without upgrade, exhaustion of the credit or the trial period closes the trial billing account and stops its resources. This evaluation offer is separate from a negotiated production commitment.[12]

Cloud Billing distinguishes alerts-only budgets from spend-cap budgets. Alerts-only budgets notify on configured thresholds and do not automatically stop consumption. Spend caps are available for supported services and have their own configuration. BigQuery adds workload-level controls: maximum bytes billed can reject an excessive query, while reservation limits and maximum slots constrain allocated analytical capacity.[13][9]

Google Cloud Setup defines an initial resource and governance foundation. Its proof-of-concept option covers organisation, billing and resource hierarchy; production adds logging, monitoring and Security Command Center settings; advanced production adds networking and Cloud KMS with Autokey. Administrator groups, management projects, application folders and organisation policies establish who can provision and operate workloads before application migration begins.[14]

Location selection is product-specific. Google publishes region, zone and multi-region availability and identifies services with varying functionality by region. A presence in one country does not establish that every analytics, AI or specialized-compute feature is available there. Compute Engine also differentiates durable disks from Local SSD; local storage has different persistence behaviour and is not a substitute for a retained operational record.[15][2]

U4 has a particularly narrow current deployment footprint. The documentation updated on 20 October 2026 lists us-south1-d and us-south1-e. U4P and U4C use dedicated bare-metal hosts, whereas U4S is virtual-machine only. Secure Boot, Confidential VM and Spot VMs are unsupported in the documented family. Its driver, operating-system and quota requirements therefore need explicit treatment in the deployment architecture; generic Compute Engine settings cannot simply be assumed to carry over.[5]

BigQuery has documented extraction routes through the console, command-line tool and API. Table exports can use CSV, newline-delimited JSON, Avro or Parquet; the formats differ in their handling of nested values and logical types. A usable migration or exit therefore includes schema reconciliation and a destination copy that the receiving system can read, alongside the exported values.[16]

Basic support includes documentation, community resources and billing help. Paid Cloud Customer Care fees use eligible monthly Google Cloud charges at list price before discounts or credits, with the documented treatment of commitments. The following USD figures describe the published support fee, separate from workload consumption. Response times are initial-response targets for the stated priority, rather than repair deadlines.[17]

Acquired-product support has moved into Cloud Customer Care. The transition guide records the end of legacy new-case routes for Looker in October 2024, Apigee in January 2025 and Mandiant in March 2025. Eligible SaaS purchases can include Comprehensive Support at no extra fee, but it requires onboarding and provisioning. That package offers a one-business-day P2 target and no P1 case submission; paid support entitlements can supersede it.[21]

The European Supervisory Authorities’ published DORA list names Google Cloud EMEA Limited as a critical ICT third-party provider. The FCA separately records the same entity’s UK critical-third-party designation from 13 July 2026. Those regimes concern the resilience and systemic importance of supplied technology services; they do not confer a brokerage, banking or investment-management permission on customers using the cloud.[26][27]

Google’s DORA explanation includes specified French, Italian and Polish subsidiaries within the EMEA designation and states that oversight does not reduce a financial customer’s own responsibilities. The designation also does not automatically rewrite its contract. Entity and service scope therefore remain relevant even where a group-wide product name appears in procurement materials.[25]

The Cloud Data Processing Addendum describes Google as processor of Customer Personal Data, with the customer acting as controller or processor. It limits processing to the documented instructions and service purposes. This allocates personal-data responsibilities; it does not transfer ownership of the institution’s financial-service obligations to Google.[24]

The contracting entity depends on the service and billing address. For the listed cloud-platform agreements, the United States and otherwise unlisted locations use Google LLC; most EMEA addresses use Google Cloud EMEA Limited; and most APAC addresses use Google Asia Pacific Pte. Ltd. The entity table specifies exceptions including Canada, France, Italy, Poland and several Asian markets. Google LLC’s listed address is in Mountain View, California.[28]

The security portfolio includes acquired businesses. Google completed the Mandiant acquisition in September 2022. On 11 March 2026 it completed the acquisition of Wiz, which joined Google Cloud while retaining its brand and multicloud commitment. These are ownership and product-context statements; they do not make all of those products part of every Google Cloud subscription.[31][30]

The online terms allow for an overriding offline agreement. Customer termination for convenience remains subject to financial commitments in applicable order forms or addenda, and termination ends the relevant access while amounts due remain payable. Deleting a workload is therefore a different action from discharging a contracted minimum commitment.[29]

For exit, the data-processing addendum permits the customer to request return of data during the term. After the term ends it instructs deletion of remaining data, subject to the stated exceptions and any continuing agreement. Following a recovery period of up to 30 days, Google must act as soon as reasonably practicable and within the specified maximum 180-day period. Those deletion provisions do not supply an indefinite post-termination export window.[24]

Operator

Google LLC and applicable regional Google Cloud contracting entities

Service scope

Cloud infrastructure, data analytics, AI and security services for financial-industry applications.

Customer types

Banks; Brokerages; Asset managers; Market operators; Financial data providers; Financial technology firms

Delivery

Hosted; SaaS; API; Hybrid

Pricing publication

Public and quoted pricing

Headquarters

Google LLC listed address: Mountain View, California, United States

Platforms

Compute Engine; BigQuery; Looker; Gemini Enterprise for Financial Services (preview); Ultra Low Latency Solution; Cloud Interconnect

Integrations

REST APIs and Cloud Client Libraries; SQL and Python; MCP financial-data connectors; Agent-to-Agent APIs; Dedicated, Partner and Cross-Cloud Interconnect

Pricing scope

Published consumption and support prices; product-specific commitments and negotiated enterprise agreements also apply.

Implementation

Configure organisation, billing, access, networking and monitoring; choose service locations and data-exit formats.

Support

Basic resources and paid Cloud Customer Care; acquired-product routes and entitlements vary.

Permissions and regulatory scope

Cloud and ICT services. Google Cloud EMEA Limited has EU and UK critical-provider designations; these do not grant customer financial-service permissions.

Provider metadata checked 21 Oct 2026Source 15Source 7Source 1Source 6Source 25Source 18Source 13Source 23Source 28Source 27Source 3Source 19Source 17Source 30Source 11Source 12Source 21Source 2Source 14Source 20Source 26Source 8Source 24Source 4Source 10Source 16Source 29Source 32Source 31Source 5Source 22Source 9

The October 2026 U4 announcement describes CME Group’s listed-derivatives migration as ongoing. Google attributes colocation-style latency and hardware-multicast capabilities to the joint architecture, but the announcement does not say that every CME market had completed its move. Infrastructure general availability and completion of an exchange’s migration are separate milestones.[4]

A current operational event is relevant to the regional footprint. Google’s incident page records a London outage from 07:08 to 15:00 on 20 October 2026, converted to Europe/London time (BST). It reports a power event in europe-west2-b and wider regional errors affecting multiple products. The incident is closed; the last update says most customers were mitigated, a small remainder should use support, and an incident analysis would follow. As checked on 21 October, that page did not yet provide the completed analysis.[32]