Project Nessie
Open-source transactional catalog for data lakes with Git-like semantics, branching, merging and versioning for Apache Iceberg and Delta Lake.
Our Verdict
Genuinely novel catalog for lakehouse workflows; adoption still early outside Dremio circles.
Pros
- Git-like branching for data lake tables
- Native Iceberg and Delta Lake support
- Enables safe experimentation via branches
- Open source under Apache 2.0
Cons
- Concept new to most data engineers
- Ecosystem tooling still maturing
- Operating Nessie yourself is non-trivial
- Dremio-adjacent branding limits neutrality perception
Best for: Data platform teams wanting Git-style branching for Iceberg or Delta tables
Not for: Teams on traditional warehouses without a lakehouse catalog strategy
When to Use Project Nessie
Good fit if you need
- Git-like branching and versioning for Apache Iceberg tables
- Data CI/CD: branch, test, and merge lakehouse table changes
- Transactional catalog enabling zero-copy data lake experiments
- Time-travel queries across Iceberg and Delta Lake tables
- Reproducible ML experiments with versioned data lake snapshots
Lock-in Assessment
Low 5/5
Lock-in Score 5/5
Pricing
Price wrong?Project Nessie Pricing
- Pricing Model
- free
- Free Tier
- Yes
- Entry Price
- —
- Enterprise Available
- No
- Transparency Score
- —
Beta — estimates may differ from actual pricing
1,000
1001K10K100K1M
Estimated Monthly Cost
$25
Estimated Annual Cost
$300
Estimates are approximate and may not reflect current pricing. Always check the official pricing page.
Project Health
A
Health Score
1.4k 174
Bus Factor
10
Last Commit
today
Release Freq
10d
Open Issues
157
Issue Response
N/A
License
Apache-2.0
Last checked: 2026-04-21
Community Discussion
Comments powered by Giscus (GitHub Discussions). You need a GitHub account to comment.