See the supported connectors for Application Integration.
Subscription entitlements
This page describes the subscription entitlement model for Application Integration, which is available as a stand-alone subscription.
Subscription entitlements 2024 (current plan)
The following table outlines the Application Integration subscription and add-on entitlements for the 2024 plan. For information on entitlements for the older plan, see the Subscription entitlements 2023 section.
Subscription | Entitlements |
---|---|
Base Subscription | |
Application Integration (Base) |
|
Add-on Packs | |
Application Integration 50M Call Pack |
|
Application Connector 50 Unit Pack |
|
All offerings and add-ons are subject to Application Integration product limits. You can add entitlements for Application Integration into multiple Google Cloud projects as you want without buying Org Packs. However, each project needs to have its own connection units, as a connection from one project cannot be used in another project.
Subscription entitlements 2023 (older plan)
The following table outlines the Application Integration subscription and add-on entitlements for the 2023 plan.
Subscription | Entitlements |
---|---|
Base Subscription | |
Application Integration (Base) |
|
Add-on Packs | |
Application Integration Call Pack |
|
Connector Unit Pack |
|
Concurrency Pack |
|
Org Pack |
|
(1) Integration call: A runtime execution of an Integration flow. Similar to Integration execution in the Pay-As-You-Go (PAYG) model. Every 100 task executions counts as another Integration call. The default quota is 50 concurrent Integrations (5).
(2) Data processing: The amount of data (in GiB) ingress or egress from an Integration execution or to and from a connection. This measures the data processed by Application Integration or by a connection and does not include any network egress charges from Google Cloud networking SKUs, which are billed separately. Additional call packs must be purchased for more data processing, even if the Integration calls are not fully consumed.
(3) Connector or Application Connection units: An abstraction of connection purchase units. Connectors are regional resources, and configuration deployed to 2 regions counts as 2 connections. There are two classes of connections: Google and technical connections (5 units per connection, including service targets like BigQuery and technical Connectors like HTTP/FTP) and Application/3p Application connections (10 units per connection, including all other connections). All connections in the subscription model include 2 nodes for a high-availability (HA) setup with autoscaling.
(4) Successful Integration call: The completion of an Integration workflow without errors due to the incorrect functioning of the Application Integration platform. Call failures not attributable to the platform (e.g., failures to connect to targets due to customer configuration errors) do not count against the SLA.
(5) Concurrent Integrations: The number of integrations that are executing concurrently. This is limited to 50 concurrent Integrations by default and can be increased upon request. Please contact sales for higher limits.
(6) Class: A class is a classification of Connectors based on the business value of the data used by the application or technology the Connector works with and/or the complexity of integrating with the Application. For example, SAP data is generally more valuable than MySQL data and is much more complex to integrate with. Please contact your Google representative for the full Connector class details.
Incidentals: The customer is charged for incidentals like Gemini Code Assist, Secret Manager, Cloud Key Management Service, Google Cloud networking (including ILBs, PSC, and other networking products), which are billed directly from those services.