What I like most about OLake is its focus on reliable data ingestion into modern lakehouse destinations, rather than trying to be yet another generic ETL wrapper. I’ve mainly used it for Postgres ingestion, CDC/incremental sync behavior, and testing Parquet destinations, and those workflows made it clear to me that OLake is addressing a real infrastructure problem. For my use cases, the Postgres integration, CDC support, and the project’s direction around Parquet/Iceberg destinations are the most valuable parts. They help teams move data into open formats on object storage without getting locked into a single warehouse. I also appreciate how approachable the project feels for open-source contributors: the separation between sources, destinations, state, and recovery logic makes the codebase easier to understand, and the maintainers are active and helpful when it comes to guiding implementation details.

I don't need to open ten different tabs or ask a developer to write queries and give me a report at the end of the day. Everything is on my screen and in real-time, anytime, anywhere I want.

Team Support, All in One Nature, Good Pricing, Use of clickhouse making queries very very fast, can host on your servers so no privacy issue.