OneConnect Subscription Types

OneConnect offers three distinct subscription types to meet integration needs. Each subscription tier determines the capabilities, scale, and automation options available for an integration.

Each integration is licensed independently, allowing you to choose the appropriate subscription level based on the complexity of the integration, data volume, and connectivity requirements.

Basic Subscription

This is the default subscription type for trial integrations.

Best suited for:

Simple integrations with limited data processing and manual execution.

Features

• Web-Based Administrative Portal: Manage and locate integrations with ease.
• Manual Execution: Integrations are run manually (no scheduled automation)
• Core Integration Capabilities: Supportes the creation and execution of standard integrations, including:
  • Field Mapping & Data Flow Management: Configure how data is mapped between systems and define the direction of data flow
  • Data Filtering: Filter data at various levels within an integration
    • Available filtering options depend on the selected integration strategy and may vary by configuration
  • Job Processing Logs & Statistics: Access detailed logs and execution statistics for each integration job
  • Job Completion Alerts: Receive notifications when integration jobs finish processing
    • Alert configuration is managed within the OneConnect Administration Settings
• Authentication and authorization integrated with OnePlan.
• Public Endpoint Connectivity: Designed for systems that are accessible over the public internet.
  • Connectivity to private / on-premise systems is not included at this tier.

Professional Subscription

Ideal for standard integrations with a processing volume of less than one million records per month.

Best suited for:

Integrations that require automation, higher data volumes, or connectivity to systems in private networks. 

Features

• Includes all Basic features
• Scheduled Execution: Automate integrations with configurable schedules
  • Delta Integration Strategies: Run up to two incremental (delta) strategies per day on a schedule
    • A "delta/incremental" strategy updates only the records that have changed since the last synchronization in either system, optimizing data transfer and processing
• Power Automate Integration: Trigger Power Automate flows when a scheduled integration strategy completes with a status of Success or Success with Exceptions
  • Flows are triggered based on scheduled execution outcomes only
  • Integration events do not trigger flows
• On-Premise / Private Network Connectivity (Optional): OneConnect can integration with systems hosted inside a private network (such as on-premise environments)
  • If the system is publicly accessible, no additional connectivity setup is required
  • If the system is not publicly accessible (e.g., behind a firewall or VPN), a relay can be used to securely enable communication
  • Use of a relay is optional and only required when direct access is not available 
  • For detailed information on relays, please visit our support article

Enterprise Subscription

Designed for high-volume integrations exceeding one million records per month or custom integration needs.

Best suited for:

Complex, large scale, or business-critical integrations that require flexibility and customization.

Features

• Includes all Professional features
• Custom integrations (Available as an Add-On): Custom integrations can be designed and implemented by the OneConnect team to support specific business requirements
  • Requires collaboration to define business use case, requirements and expected outcomes
  • Delivered as an additional service engagement (not included in the base subscription)
• Advanced Scheduling and Execution: Greater flexibility in execution frequency and orchestration
  • A strategy can run a maximum of 24 times a day
• Enhanced Performance and Scalability: Designed to support enterprise-level workloads and complex scenarios

Non-production Integrations

With the Premier Product Success package, each integration includes a non-production instance.

The non-production integration can be used to test configuration changes or custom integration updates in advance of deployment to the production instance.

All non-production integrations are limited to two scheduled integration jobs per day.