Aiven for Kafka is very easy to set-up and getting started, however, it comes at quite a steep pricing. Don't want to worry about setting up and managing Kafka, then this is great. No direct Zookeeper access is available though, which in some scenarios could be a downside. Schema registry with Karapace is a big plus, which allows for compatibility with Confluent's registry.
However, for bootstrapping a Kafka project, I'd recommend starting with open source first, to build your project and only start using this for a production scenario.
What is nice, is that all the complex logic of Kafka regarding SASL and jaas config is abstracted away. It just works. Review collected by and hosted on G2.com.
Like mentioned before, using a managed service such as Aiven for Kafka is a trade-off between ease of use and customizability. You cannot tweak Zookeeper unfortunately.
Furthermore, web console often lags behind and is eventually consistent. The interaction speed with the cluster is slow and provisioning new resources in the cluster (i.e. topics, users, etc). Review collected by and hosted on G2.com.
