Hey, I’m building a B2B SaaS/Agency where we provide custom software to clients. We want to use Airbyte as our integration backbone, specifically focusing on the syncing data of clients to our data lakes to get higher rate limits while querying. We have a few specific requirements: Custom Handling: We plan to modify/extend the connector code for specific custom logic. Self-Hosting & Multi-tenancy: We intend to self-host a modified version of airbyte to power our platform for multiple clients. On-Prem Redistribution: Some of our enterprise clients require the full stack (including the modified airbyte instance) to be deployed on their own premises. My questions: How does this sit with your current licensing (ELv2), specifically regarding redistributing modified versions to our clients? Are the Enterprise Cloud features (like advanced logging, environment management, or specific security tools) available for self-hosting, or are they strictly locked to your managed cloud? Do you have a partnership model for agencies/platforms that want to offer airbyte as a self-hosted component of their own enterprise delivery? Would love to ensure we’re aligned before we dive deep into the fork @Mark Grivnin

Hi Konda, You can modify Airbyte and embed it as a backend in your SaaS. What you cannot do is host Airbyte and sell it as an ELT/ETL tool, sell a product that directly exposes Airbyte's UI or API to your customers, or remove/circumvent license key functionality. On-prem redistribution to clients follows the same rules. Full details here. We no longer offer self-managed Enterprise. Features like RBAC, mappings, and multiple workspaces are only on Cloud. No formal partner program at this time for agencies redistributing Airbyte.

Thank you, let me go through this and I will get back if I have more questions