How suited is Airbyte for multi-tennant use-cases?
I might have a project coming up to build a semi-analytics solution where you would obviously want to allow the users to easily connect to their data sources, and Airbyte looks like it might be a good fit for that (for now my rough idea was to build some plumbing around Singer taps). Are you aware of any users that use it for such purposes and are there any specific pitfalls too look out for there?
We do support separate workspaces but we don't have auth yet. However because there is an API available, you can always build the account segmentation and permissionning at your app level and only interact with Airbyte using the API.
Comments
How suited is Airbyte for multi-tennant use-cases?
I might have a project coming up to build a semi-analytics solution where you would obviously want to allow the users to easily connect to their data sources, and Airbyte looks like it might be a good fit for that (for now my rough idea was to build some plumbing around Singer taps). Are you aware of any users that use it for such purposes and are there any specific pitfalls too look out for there?
We do support separate workspaces but we don't have auth yet. However because there is an API available, you can always build the account segmentation and permissionning at your app level and only interact with Airbyte using the API.