SECURITY

Move your data on your terms.

Airbyte connects 700+ systems to your analytics and AI agents. Replicated records pass through Airbyte and are purged after each sync. Airbyte stores your data only when you turn on semantic search, and only for the connections you choose. Independent auditors check our work every year.

  • SOC 2 Type II
  • ISO/IEC 27001:2022
  • GDPR
  • Annual third-party penetration testing

Secure by architecture, not by promise.

  • Replicated data passes through. It doesn't stay.

    Records exist in Airbyte only while a sync is running, then they're purged. Your sources and destinations stay the systems of record. The one exception is semantic search for AI agents, and only if you turn it on.

  • Every sync runs alone.

    Each sync runs in its own isolated environment, never shared with another customer.

  • Secrets stay secret.

    Connector credentials live in a dedicated secrets manager, never in our application database. Higher plans can also reference credentials kept in your own secrets manager.

Your data runs where you decide.

Choose where each workspace runs: Airbyte-managed regions in the United States or the European Union, each spread across multiple availability zones, or your own infrastructure with Enterprise Flex. Every connection in a workspace runs in its region.

Built for regulated data.

With Enterprise Flex, your records move through a data plane in your own infrastructure, and only metadata reaches Airbyte's control plane.

Learn about data residency

AI agent security.

Agent access is off by default and controlled by your admins.

  • Admin-controlled. Agent access stays off until an organization admin turns it on. Workspace editors can then turn it off for any source or destination.
  • Direct reads are read-only. When agents read directly from your sources and destinations, they can list and get records and run read-only SQL. Direct reads can't create, update, or delete records.
  • Credentials never exposed. Agents work through the connectors you've already configured and never see their credentials.
  • Your permissions apply. Every agent request is authenticated and limited to what the person or application behind it can access in Airbyte.

Controls you set.

Every plan includes encryption in transit and at rest, an IP allow list, and admin controls for agent access. Higher plans add:

  • Single sign-on, SCIM, and role-based access control
  • Audit logging
  • Field hashing, encryption, and row filtering
  • External secret references and private connectivity
  • In-boundary deployment with Enterprise Flex
See what each plan includes

Controls we run.

Good architecture needs good habits. Ours are independently audited.

  • Least privilege. Production access is limited to the people who need it, protected by multi-factor authentication, and regularly reviewed.
  • Monitored and patched. Intrusion detection, centralized logging, and vulnerability scanning, with critical findings tracked to remediation.
  • Tested by outsiders. Independent penetration testers attack the platform at least once a year.
  • Every change reviewed. Code and infrastructure changes are reviewed and approved before they reach production.
  • Ready for the bad day. Incident response and disaster recovery plans, tested every year.
  • Resilient by design. Multi-zone infrastructure and encrypted, point-in-time backups.

Independently verified.

Airbyte attestations and where to request each one
SOC 2 Type IIRequest the report in the Trust Center.
ISO/IEC 27001:2022Download the certificate from the Trust Center.
Penetration testingRequest the summary in the Trust Center.

Policies, business continuity documentation, and answers to common security questions are in the Airbyte Trust Center too.

Questions, answered.

Yes. Data moves over encrypted connections, and what Airbyte stores, such as your configuration and any search data you turn on, is encrypted at rest.

Connector credentials live in a dedicated secrets manager, never in our application database, and AI agents never see them. Higher plans can also reference credentials kept in your own secrets manager.

In the region you choose for each workspace. The Airbyte Cloud control plane runs in the United States. Read the details.

Yes, in SPDX JSON for every public container. The Trust Center shows how to pull them.

At status.airbyte.com, where you can also subscribe to incident updates.

Open source, secured in the open.

Airbyte open source is built to run inside a network you control.

  • SBOMs in SPDX format for every public container.
  • A published security model for each in-scope repository.
  • GitHub Security Advisories for confirmed vulnerabilities, naming the release that fixes them.
  • Hardening guidance in our security documentation.

Found a vulnerability? We want to hear from you.

Review our vulnerability disclosure policy and report privately at airbyte.com/security/vdp. Please don't use public issues, pull requests, or discussions.

Your security review, minus the back-and-forth.

Visit the Trust CenterTalk to us