Hey team, We are planning to use Airbyte for our data ingestion pipeline. We are currently evaluating if it is a good fit. To make it useful for our customers, we need to add a "Field33" destination. The plan is to use it to ingest data into our Ontology-powered graph database. Two quick questions: • I'm trying to figure out how best to build our Destination Connector. Since all of our internal tooling is written in Rust, and we like small Docker containers, we would like to write a custom destination in Rust+Docker and create a PR to add it to Airbyte. Is it allowed to use Rust for this? Is there some policy around it? I'm on the hook if I build it and it gets rejected, so this would be useful to know 😛 • I saw that you guys have a connector builder. Am I right in my understanding that this builder is only for custom sources, and not custom destinations? If building a connector is not an option, I could add some routes to our backend to support an existing protocol. Cheers!

A message from kapa.ai