---
title: OLake Reviews
meta_title: 'OLake Reviews 2026: Details, Pricing, & Features | G2'
meta_description: Filter reviews by the users' company size, role or industry to find
  out how OLake works for a business like yours.
aggregate_rating:
  rating_value: 4.5
  review_count: 1
  scale: '5'
date_modified: '2026-07-13'
parent_category:
  name: Backup
  url: https://www.g2.com/categories/backup
---


# OLake Reviews
**Vendor:** Datazip, Inc.  
**Category:** [Data Replication Software](https://www.g2.com/categories/data-replication)  
**Average Rating:** 4.5/5.0  
**Total Reviews:** 1
## About OLake
OLake is an open source EL engine built for Apache Iceberg, Parquet & S3. Using the catalog your platform already runs, OLake writes tables that your engines can read consistently and seamlessly connects with a wide range of query engines to analyze your data wherever it lives. Integrations available with: Postgres, MongoDB, MySQL, Oracle, Kafka, DB2 LUW, S3, MSSQL OLake is available as a UI or a CLI




## OLake Reviews
  ### 1. Reliable open-source ingestion for lakehouse pipelines

**Rating:** 4.5/5.0 stars

**Reviewed by:** Siddhant R. | Software Engineer, Small-Business (50 or fewer emp.)

**Current User:** The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.

**Validated Reviewer:** Validated through LinkedIn

**Incentivized:** This reviewer was offered a nominal gift card as thank you for completing this review.

**Source: G2 invite:** Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review.

**Reviewed Date:** July 07, 2026

**What do you like best about OLake?**

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.

**What do you dislike about OLake?**

The main downside is that OLake still feels like a fast-moving open-source project, so in a few areas you end up needing to read the docs, GitHub issues, or even the codebase to fully understand the expected behavior. For example, more advanced topics like CDC state handling, retries, destination recovery, and object-storage behavior can be difficult to reason about at first.

I’d like to see more end-to-end examples, architecture diagrams, and troubleshooting guides that cover common production scenarios. The overall direction feels strong, but clearer onboarding and practical reference material would make it easier for new users and contributors to adopt OLake more quickly.

**What problems is OLake solving and how is that benefiting you?**

OLake is solving the problem of moving data from operational sources into open lakehouse destinations in a reliable and repeatable way. For me, the biggest value is around understanding and testing ingestion flows like Postgres full refresh, incremental sync, and CDC into Parquet/Iceberg-style destinations.

Instead of treating ingestion as a black box, OLake gives a clearer structure around sources, destinations, state, retries, and recovery. That helps when reasoning about real production concerns like avoiding duplicate data, resuming failed syncs, and keeping destination state consistent with source progress. The benefit is that teams can build more flexible pipelines on open formats and object storage without depending entirely on closed warehouse-native ingestion tools, which can improve both performance control and long-term cost flexibility.



- [View OLake pricing details and edition comparison](https://www.g2.com/products/olake/reviews?section=pricing&secure%5Bexpires_at%5D=2026-08-26+01%3A26%3A54+-0500&secure%5Bsession_id%5D=ca9468c0-90f1-4831-8297-28503b8449a7&secure%5Btoken%5D=924c7b05d440377e0edcef6cfccaadeed371d50bf4b6da3f0ad24e9e2687b496&format=llm_user)

## OLake Features
**Management**
- Real-Time Analytics
- Solution Integration
- Infrastructure Compatibility
- Monitoring

**Management**
- Disaster Recovery
- Remote Backup
- Storage Formats
- Scheduled Backups
- On-Demand Restoration

**Solution Provision**
- System Failover
- Pay by Usage
- Service Provision

**Reporting**
- Activity Monitoring
- Documentation
- Alerts/Notifications

**Security**
- Data Encryption
- Security and Compliance
- Deduplication 

## Top OLake Alternatives
  - [Fivetran](https://www.g2.com/products/fivetran/reviews) - 4.3/5.0 (811 reviews)
  - [Workato](https://www.g2.com/products/workato/reviews) - 4.7/5.0 (748 reviews)
  - [Veeam Data Platform](https://www.g2.com/products/veeam-data-platform/reviews) - 4.6/5.0 (708 reviews)