Data integration support

Airbyte Support for Cloud, Enterprise Flex and Self-Hosted Core

Last reviewed by Tyler Eastridge

AceMQ supports Airbyte 24/7 across Americas, EMEA and APAC: Airbyte Cloud, Enterprise Flex, and self-hosted Airbyte Core on Kubernetes or Docker. Most calls start with one of three problems: a sync marked succeeded while the warehouse table is wrong, an incremental stream that re-pulled everything after a cursor reset, or source and destination pods killed for memory.

24/7 Airbyte support with response targets from 15 minutes, by plan. Quote replies within 1 hour.

Support quotes answered within 1 hour, by a senior engineer.

Planning a build, upgrade or migration instead? See AceMQ Airbyte consulting and services.

160+
Customers supported
10+
Years in production support
40+
Sev 1 incidents handled a year
24/7
Americas, EMEA and APAC
1hour
Quote reply

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

Incident Triage

Problems we fix every week

Sync problems that look fine on the dashboard but are wrong in the warehouse, with the stream state, job log or pod event we check for each.

Common Airbyte production problems and how AceMQ resolves them
Symptom you're seeingWhat we check first
Green sync, wrong dataA successful job means extract and load finished. With the current destinations, raw records land in an airbyte_internal schema and typed final tables are built from them. We query the _airbyte_meta column on the final table for rows with recorded errors or changes, compare _airbyte_extracted_at with the last real source change, and check whether a downstream dbt run is the real cause of a stale table.
An incremental stream pulls the full table againWe read the stream state JSON for the connection, check the cursor field against the source, and look at connector version history for a change that reset state. Then we explain the difference between refreshing a stream (re-pull without deleting) and clearing it (which deletes destination data on destinations that support it) before anyone presses either button.
Schema drift reaches productionWe check the connection's non-breaking change preference (ignore, disable the connection, propagate columns, propagate fully) against what the downstream models can absorb. A new column that propagates into a table feeding a report is a change request, not an accident, and should be handled like one.
Self-hosted pods are OOMKilled or sync jobs hangSource and destination run as separate job pods with their own limits (JOB_MAIN_CONTAINER_MEMORY_REQUEST and JOB_MAIN_CONTAINER_MEMORY_LIMIT and the CPU equivalents). We read kubectl describe pod for the exit reason, kubectl logs for the last record batch, and size limits to the widest JSON payload in the stream, not the average. We also check Temporal and the platform database when jobs stay pending.
429 errors from a source APIWe compare the connector's retry and backoff behaviour with the source's published rate limit, then change sync frequency, stream concurrency or page size. Some connectors need a version change, not a setting.
A custom connector breaks after an upgradeWe compare the pinned CDK version with what the platform expects, replay the failing stream against a recorded sample, and decide whether to fix a Connector Builder manifest, patch the Python connector, or pin the connector version while the fix is tested.
Cloud spend jumpsAirbyte Cloud bills in credits tied to volume synced. We identify the streams moving the most data, then move them to incremental mode or lengthen their schedule, and remove streams nobody queries.
Destination rejects or truncatesWe read the destination's own error log for permission failures, type narrowing and column-name collisions, since the Airbyte job log may show only a summary.

Each P1 ends with a written cause that names the connector, stream or job.

Sync shows green but the data is wrong? Request a quote and an Airbyte engineer responds within the hour.

Contact Us

Deployment coverage

Which Airbyte deployments does AceMQ support, and who covers what?

DeploymentWhat AceMQ coversWhat the vendor coversExcluded
Airbyte CloudConnection design, sync modes, schema change policy, destination behaviour, dbt interplay, credit reviewAirbyte runs the platform, hosting and upgrades on paid plans (Airbyte pricing page, read 17 Nov 2026)Airbyte platform faults
Airbyte Enterprise Flex (hybrid, in your VPC or on premises)Data plane operations on your infrastructure, job pod sizing, connector issues, escalation with AirbyteAirbyte provides the control plane and a dedicated Solutions Architect on that planControl-plane faults
Airbyte Core on Kubernetes (Helm) or Docker (abctl)Everything: installs, upgrades, worker sizing, Temporal and database health, connector troubleshooting, backups, incident responseNothing: Airbyte's docs state Core users have no paid support (Airbyte support docs, read 17 Nov 2026)Hardware and OS faults outside the agreed scope
Custom and Connector Builder connectorsDebugging, CDK and manifest changes, version pinning, test streamsAirbyte supports connectors it publishesThird-party APIs and their rate limits

Support options

Who provides enterprise support for Airbyte? Airbyte plans and independent support compared

Airbyte sells support with its paid plans. Core, the free self-hosted edition, has no paid support from Airbyte. Independent support covers Core, and covers the parts of a paid plan that fall outside Airbyte's scope.

Airbyte Core / Airbyte paid plans
AceMQ independent support
SupportAirbyte Core: Community Slack and GitHub; no paid supportAirbyte paid plans: Standard and Plus: first response SLA of 24 hours, support 7 am to 7 pm Eastern. Pro: 24/5 support, 12 hours for critical issues, 24 hours for general. Enterprise Flex: premium support with a 12-hour critical response and a Solutions Architect. An enterprise support add-on is listed at 6 hours critical, 12 hours general (Airbyte pricing page, read 17 Nov 2026; the page does not map every value to a plan, so confirm with Airbyte sales)
SupportResponse targets from 15 minutes, by plan, 24/7
ScopeAirbyte Core: You run itAirbyte paid plans: Airbyte platform and connectors it ships
ScopeYour pipelines end to end: platform, connectors, destination and the models downstream
Sync frequency limitsAirbyte Core: Your scheduleAirbyte paid plans: Standard hourly, Plus every 15 minutes, Pro every 5 minutes (pricing page)
Sync frequency limitsNot a limit we set
PriceAirbyte Core: FreeAirbyte paid plans: Standard from $20 a month; Plus from $189 a month; Pro and Enterprise Flex by quote (pricing page, read 17 Nov 2026)
Price$24,000 to $72,000 a year (USD), set by SLA, scope and deployment

What's Included

Everything in your Airbyte support contract

Connectors, sync modes, schema changes, worker capacity and custom connectors are all within scope, on Cloud, Enterprise or self-hosted OSS.

  • 01

    Emergency Incident Response

    A sync pipeline feeding production reporting or ML training data goes dark. With response targets from 15 minutes, by plan, a senior engineer joins a live bridge with access to diagnose — not a ticket acknowledgement.

  • 02

    Root Cause Analysis

    Every P1 closes with a written RCA: which connector or step failed, why it failed silently, and the monitoring or config change that prevents it recurring. Delivered as standard, not on request.

  • 03

    Connector & Sync Tuning

    Sync mode selection, cursor field configuration, worker resource sizing, and rate-limit handling tuned against your actual source volume and API quotas.

  • 04

    Schema Drift Monitoring

    Alerting on source schema changes and normalization/dbt step failures — the two categories of failure that Airbyte's own sync status will not surface as an error.

  • 05

    Cost & Capacity Reviews

    Quarterly reviews of sync frequency, warehouse compute burned on unnecessary full refreshes, and worker resource headroom so you size ahead of pipeline growth.

  • 06

    Custom Connector & Upgrade Support

    CDK-based custom connector maintenance, platform upgrade validation, and migration support for teams moving off Pentaho or hand-rolled ETL onto Airbyte.

Why AceMQ

What Airbyte teams get from AceMQ

  • Named Engineers, Zero Cold Start

    The same senior engineers stay on your account. They know your source systems, your sync schedules, and which connectors are flaky — so a P1 starts with diagnosis, not twenty minutes of explaining your pipeline.

  • No Tier-1 Triage Layer

    You reach a senior Airbyte engineer directly by phone, email, or Slack. No help desk collecting information to pass along, no escalation approval process between you and someone who can actually fix it.

  • Full Pipeline, Not Just the Sync

    We diagnose across the connector, the normalization/dbt layer, and the destination warehouse — because 'sync succeeded' and 'data is correct' are two different claims, and most incidents live in the gap between them.

  • Genuine Follow-the-Sun Coverage

    Round-the-clock coverage for customers in 26+ countries. Your 3am pipeline failure is someone's mid-afternoon — no overnight skeleton crew, no waiting for a region to wake up.

  • Proactive, Not Just Reactive

    Quarterly health checks on your deployment plus shared intelligence across our support base. When a connector-specific bug surfaces on one customer's pipeline, every affected customer hears about it before it hits their production sync.

  • Honest About the ETL/ELT Landscape

    If Airbyte is the wrong fit for a specific source, or a legacy Pentaho job would migrate more cheaply than it would be replatformed, we say so. Our job is a working pipeline, not defending a tool choice.

Airbyte deployments we cover

Airbyte on Kubernetes or Docker Compose, Airbyte Cloud workspaces, and destinations such as Snowflake, BigQuery and Redshift.

  • Airbyte Cloud
  • Airbyte Enterprise (self-managed)
  • Airbyte OSS (self-hosted)
  • AWS (EC2, EKS, ECS)
  • Google Cloud (GKE)
  • Microsoft Azure (AKS)
  • Kubernetes & OpenShift
  • Docker Compose deployments
  • Snowflake & Databricks destinations
  • BigQuery & Redshift destinations
  • Air-gapped / no outbound access

Version coverage

Versions we support

Versions we support
EditionVersion listedNote
Airbyte Core and Enterprise (self-managed)2.5 (6 Nov 2026), 2.4 (9 Oct 2026), 2.3 (15 Sep 2026), 2.2 (10 Aug 2026)Airbyte release notes, read 17 Nov 2026. The notes state no supported-versions policy, so we plan upgrades from the version you run
Airbyte CloudAlways currentAirbyte says Cloud customers always have the latest enhancements
ConnectorsAny pinned versionWe review connector changelogs for breaking changes before an upgrade

Escalation Path

Your first hour of an Airbyte outage

A sync that reports success while the table goes stale is hard to spot. The engineer you reach knows to compare cursor state with the destination first.

  1. From 15 min (by plan)first responseEmergencyProduction impact: no syncs are running, the platform will not start, or a destination is receiving corrupt data
  2. 1 hourfirst responseCriticalSerious degradation: incremental streams re-pulling whole tables, worker pods killed for memory, jobs hung midway
  3. 4 hoursfirst responseHighSource API rate limits, schema drift reaching downstream models, custom connectors failing after an upgrade
  4. Next Dayfirst responseStandardSync mode and cursor choice, refresh versus clear behavior, connector selection, capacity sizing and cost questions

Response clocks follow your plan, so a halted pipeline outranks a connector configuration question.

Want a named engineer who already knows your connectors and destinations? Ask for a quote or write to us.

Contact Us

Pricing

What does AceMQ Airbyte support cost?

Airbyte support generally costs $24,000 to $72,000 a year. The size of the engagement tracks connector count, whether you self-host or use Cloud, how many custom connectors you maintain, and the response plan.

Amounts are in US dollars (USD). Response targets begin at 15 minutes by plan, 24/7, and quote requests get an answer within 1 hour. A shared contract covering other tools can reduce the price.

Support In Practice

Airbyte pipeline fixes we have delivered

Airbyte support work from AceMQ. Each card links to the full write-up: the pipeline estate, what AceMQ diagnosed or changed, and the result.

1 / 6 case studies

  • Remediation

    Airbyte Connector Schema Drift Remediation

    Retail Analytics Organization

    Diagnosing an Airbyte connection that kept reporting success while the destination table quietly went stale after an upstream schema change.

    AirbytePostgreSQLSnowflakeKubernetesdbt
  • Assessment

    Airbyte Pipeline and Connector Estate Assessment

    Insurance Services Group

    A structured review of an Airbyte estate that had grown organically — auditing connector versions, sync modes, state handling, and failure visibility.

    AirbyteKubernetesPostgreSQLdbtKafka
  • Support

    Docker Disk Exhaustion and Build Cache Support

    Media Streaming Company

    Stopping recurring build agent and node outages caused by unpruned Docker build cache, dangling images, and orphaned volumes filling the filesystem.

    DockerKubernetesAirbytePostgreSQL
  • Consulting

    Pentaho to Modern ELT Stack Migration

    Healthcare Payer Organization

    Planning and executing a staged move off Pentaho Data Integration onto a modern ELT stack, without a big-bang cutover of hundreds of transformations.

    PentahoAirbytedbtPostgreSQLKubernetes
All use cases

Support options

Four tiers of Airbyte support.

AceMQ offers Airbyte support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for pipelines your team runs, proactive monitoring that finds schema drift and cost spikes first, managed Airbyte on your own infrastructure, and fully managed Airbyte on AceMQ infrastructure. Cloud, Enterprise and self-hosted open source estates are covered, with Cloud under the first two.

  • Tier 1

    Airbyte 24/7 Support & Incident Management

    Your data team owns pipelines, we handle failures

    Best for: Data engineers who run Airbyte themselves and want an expert for stale tables, stuck jobs and connector breaks.

  • Tier 2

    Airbyte 24/7 Support with Proactive Monitoring

    Periodic health checks on connectors and cost

    Best for: Teams who want drift, rate limits and worker sizing reviewed on a schedule instead of after a bad report.

  • Tier 3

    Managed Airbyte on Your Infrastructure

    We operate Airbyte inside your cluster

    Best for: Organizations that need Airbyte and its data in their own Kubernetes environment, with someone else watching it.

  • Tier 4

    Fully Managed Airbyte on AceMQ Infrastructure

    AceMQ runs your Airbyte pipelines for you

    Best for: Analytics groups that want data landing reliably in the warehouse without a team to operate the platform.

FAQ

Airbyte support questions

Still have questions about Airbyte? Email an Expert

Who provides enterprise support for Airbyte?

Airbyte provides support on its paid plans, with response times that depend on the plan. Airbyte Core has no paid support. AceMQ supports Core and the parts of Cloud and Enterprise Flex that sit outside Airbyte's scope, 24/7 with response targets from 15 minutes, by plan.

Why does Airbyte show success when the table is stale or wrong?

Success covers extraction and load. Check _airbyte_meta on the final table, the extraction timestamp, and any dbt model that builds on it.

What is the difference between refreshing and clearing a stream?

A refresh re-pulls data without deleting what is in the destination; a clear removes destination data first on destinations that support it. Decide before you run either, and check state afterward.

Why did our incremental sync pull everything again?

A cursor reset: a connector upgrade, a changed cursor field, or lost state. We read the stream state and the connector changelog to find which.

Why are Airbyte worker pods OOMKilled?

Source and destination pods have their own memory limits, and a wide JSON record can exceed a limit sized for the average row. We size limits from the widest payload and set batch sizes.

Can you help with schema changes breaking our reports?

Yes. We set the non-breaking change preference per connection and add a review step for propagation into tables that feed reports.

Do you support custom connectors?

Yes, Connector Builder manifests and Python CDK connectors, including pinning and upgrade testing.

What does an Airbyte health check include?

Connection inventory, sync duration and freshness trends, state and cursor review, schema change policy, worker sizing, Temporal and database health on Core, Cloud credit drivers, and a ranked list of fixes.

Can you move us from Pentaho or another ETL tool to Airbyte?

Yes, and we will say where a job is cheaper to leave where it is. See /pentaho/support/.

Is Airbyte support available without a long commitment?

Yes. A health check, a custom connector fix or an upgrade of a self-hosted install can be bought as one engagement. If pipelines fail often enough to justify ongoing cover, an annual agreement adds 24/7 response and keeps the same engineers on your account.

What determines the price of Airbyte support?

Typical annual contracts are $24,000 to $72,000 (USD). Drivers include the number of connections and connectors, self-hosted versus Cloud, any custom connectors you built, how often you upgrade, and the response plan. Share your deployment details and a quote comes back within 1 hour.

Let's talk

Your Airbyte Pipeline Shouldn't Fail Silently

Send us the connection ID of the sync you cannot trust. We reply within 1 business hour with what we would check first.

A senior Airbyte engineer, not a sales queueQuote requests answered within 1 hourAd hoc engagements or an annual partnership

Production incident right now?Email an Airbyte Architect