Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

We are launching our <https://discuss.airbyte.io/c/connector-marketplace/10/none|Connector Marketplace> :tada: <!channel>! (along with our Discourse forum). What does this mean? It's a *place for people to commission the construction of Airbyte connectors*. Community members that are skilled at building connectors can meet with teams and companies that need connectors built to form a mutually beneficial relationship. Check the thread for more details!

If you *build connectors*:
• Create a profile <https://discuss.airbyte.io/c/connector-marketplace/connnector-builder-profiles/9|here> with your skills and expectations.
• Check out the current requests <https://discuss.airbyte.io/c/connector-marketplace/connector-jobs-listing/8|here>.
If you *want connectors built*:
• Create a posting <https://discuss.airbyte.io/c/connector-marketplace/connector-jobs-listing/8|here> with your expectations and compensation.
• Check out the current builder profiles <https://discuss.airbyte.io/c/connector-marketplace/connnector-builder-profiles/9|here>.
Please let us know if you have any other questions about this. Finally, if the connector built is contributed back to open source, we'll give $500 in Airbyte Cloud (soon:tm:) credits to the commissioner.

<@U01RW78A2LE> may you clarify few questions:
1. May such connectors be closed source?
2. How such connectors will be maintained in case of errors or API changes?

<@U01RW78A2LE> thanks.
I’m wondering about the price range for creating connectors? Maybe you have some understanding/recommendation for the price range depending on the types of connectors?

Re: <@U01V8JGB996>!

1. You may keep the connectors you commission closed source, and there are many teams today that have created connectors that they haven't contributed back to OSS (usually because the connector is too specific to the company's data architecture).
2. It does naturally follow though, that we can't maintain closed-source connectors and we <https://discuss.airbyte.io/t/terms-of-use-of-the-connector-marketplace/34|aren't responsible> for the connectors created. You'll have to either maintain it on your own or commission the connector builder to maintain it. 
Re: <@U02EL5PSMUN>!

It really depends on the complexity. A simple HTTP API connector would take an experienced connector dev half a day or less, so that may place it in the $200 - $800 range. This may be even less if you only want the Full Refresh sync mode completed.

A destination, or an API with a complex schema and many streams to implement, incremental sync, pagination, and more can take potentially up to a week, where you would be likely paying at least $2000. Of course, this is just an estimate and people all value their time differently. There are <https://discuss.airbyte.io/c/connector-marketplace/connnector-builder-profiles/9|three builder profiles> already, so you can check them out if you're interested!

<@U01RW78A2LE> thank you!

```It does naturally follow though, that we can't maintain closed-source connectors and we aren't responsible for the connectors created. You'll have to either maintain it on your own or commission the connector builder to maintain it.```
Contribution back to OSS is a good choice in order to receive maintenance from Airbyte company and community, do I understand right?

<@U01V8JGB996> Yep, that's the idea! We (and community members) can help maintain connectors that are contributed back and can add features you want developed for them to our roadmap.