Kafka Connect is part of Apache Kafka, so the odds of that becoming closed source are basically nil. At worst, you could imagine a Confluent-owned fork. Kafka S

Kafka Connect is part of Apache Kafka, so the odds of that becoming closed source are basically nil. At worst, you could imagine a Confluent-owned fork. Kafka Streams (another Kafka extension that Confluent has spearheaded) is also part of Apache Kafka. The Schema Registry and Kafka REST Proxy are confluent projects but are Apache licensed. I'd imagine the reason for this is less "Confluent might want to lock it down" and more "getting these projects adopted into the Apache Kafka project is more trouble than it is worth." Either way, worst case, just fork it. The schema registry is simple enough that it's hard to imagine it really needing much feature work from here anyway. The REST proxy I could imagine having enterprise features down the road though. It's hard to know how exactly Confluent could walk back the OSS nature of these projects though without a major backlash (not to mention the Apache license may actually prevent this? I am not sure.)