20 lines
1.3 KiB
Markdown
20 lines
1.3 KiB
Markdown
# Examples
|
||
|
||
We chose ELv2 because it is very permissive with what you can do with the software.
|
||
We are still being asked whether one's project are concerned by the ELv2 license. So we decided to list some projects to make this very explicit.
|
||
|
||
Don't hesitate to ask us about this or to do a pull request to add your project here. If we merge it, it means you're good to go.
|
||
|
||
Let's start with the list of projects that falls under ELv2 and for which you can't leverage Airbyte's technology that is under Elv2, because there aren't actually many projects.
|
||
|
||
## Examples of projects that can't leverage the technology under ELv2 without a contract
|
||
|
||
- Hosting Airbyte yourself and selling it as an ELT/ETL tool. That means selling a competitive alternative to Airbyte Cloud or the future Airbyte Enterprise.
|
||
- Selling a product that directly exposes Airbyte’s UI or API.
|
||
|
||
## Examples of projects for which you can leverage Airbyte fully
|
||
|
||
- Creating an analytics or attribution platform for which you want to use Airbyte to bring data in on behalf of your customers.
|
||
- Creating any kind of platform on which you offer Airbyte's connectors to your customers to bring their data in, unless you're selling some ELT / ETL solution.
|
||
- Building your internal data stack and configuring pipelines through Airbyte's UI or API.
|