Airbyte Cloud limits
Understanding the following limitations will help you more effectively manage Airbyte Cloud.
Standard plan limitations
These limitations only apply to those using the Standard plan. Upgrading to a higher plan raises or removes them. See Airbyte's pricing page to compare plans.
-
Max number of workspaces per organization: 1. If you were a Cloud Standard customer before September 24, 2025, Airbyte has grandfathered you into its historical 3-workspace limit.
-
Scheduled or cron syncs can run at most every 60 minutes.
-
Single sign-on (SSO) isn't available. If your Standard organization already uses SSO, you keep it as long as you remain a paying customer.
-
Role-based access control (RBAC), user groups, and SCIM provisioning aren't available. Every user is a workspace admin or an organization admin, and you can't change their roles. See Manage users and permissions.
Plus plan limitations
These limitations only apply to those using the Plus plan. If you upgrade to Pro or Enterprise Flex, Airbyte removes these limitations.
-
Max number of workspaces per organization: 2.
-
Scheduled or cron syncs can run at most every 15 minutes.
-
SSO is available, but SCIM provisioning, user groups, and role-based access control aren't. Every user is a workspace admin or an organization admin. See Manage users and permissions.
Cloud limitations for all plans
-
Max number of streams that can be returned by a source in a discover call: 1,000
-
Max number of streams that can be configured to sync in a single connection: 1,000
-
Max number of fields that can be selected to sync in a single connection: 20,000
-
Size of a single record: 20MB**
Pro and Enterprise Flex plan considerations
Organizations on capacity-based plans (Pro, Enterprise Flex) have a contracted number of data workers. When all data workers are in use, additional syncs are queued until capacity becomes available. This is not a hard limit on the number of connections or syncs you can create, but a limit on concurrent sync execution.
You can enable on-demand capacity for critical connections so they run even when committed capacity is exhausted. See Manage and monitor data workers for details.
** The effective maximum size of the record may vary based per destination. Some destinations may
fail to sync if a record cannot be stored, but Destinations which support
typing and deduping will adjust your record so that
the sync does not fail, given the database/file constraints. For example, the maximum size of a
record in MongoDB is 16MB - records larger than that will need to be modified. At the very least,
primary keys and cursors will be maintained. Any modifications to the record will be stored within
airbyte_meta.changes for your review within the destination.