shouldiuse.io

VERDICT

Should I use Project Nessie?

Transactional catalog for data lakes with Git-like semantics, built on Apache Iceberg. - projectnessie.org

Depends. Worth adopting if you run a multi-pipeline Iceberg lakehouse and need cross-table transactions plus branch/merge workflows on your data. Skip it if you have simple or single-writer analytics — it's self-hosted infrastructure you will have to operate for no benefit.

Confidence

Medium. Based on ~25 public sources, almost all official docs and release notes. No independent review ratings found, so user-sentiment conclusions are weak.

Ratings

  • Value for money
  • Ease of use
  • Feature depth
  • Support qualityNo support evidence in sources.
  • Security posture

Pricing

$0

Open source (self-hosted)

ModelNot disclosed
Monthly feesNot disclosed
HardwareNot disclosed
Free tierYes

Best for

  • Data platform teams on Apache Iceberg
  • Multi-pipeline lakehouses needing cross-table transactions
  • Teams wanting branch/test/merge workflows on data
  • Dremio Arctic users wanting the OSS equivalent

Not for

  • Small teams without a lakehouse — a plain Glue or Hive catalog is enough
  • Single-writer pipelines that never need branches or cross-table commits
  • Orgs wanting SLA-backed vendor support without going through Dremio
  • Analysts expecting a UI — this is self-hosted backend infrastructure

Gotchas - check before you buy

medium

Export/import and admin tooling requires direct database access — plan operations around this.

medium

0.x versioning: configs and APIs shift between releases. Pin versions and test upgrades.

medium

CVE-2023-44487 (HTTP/2 rapid reset) hit its Netty dependency; patched via Quarkus bump. Stay current.

low

No support SLAs from the project; the managed route is Dremio Arctic, which is paid.

Pros and cons

Pros

  • Free and fully open source under Apache-2.0
  • Git-like branches and cross-table transactions for Iceberg lakes
  • Powers Dremio's managed Arctic service in production
  • Pluggable version-store backends including DynamoDB
  • Documented authentication and fine-grained authorization

Cons

  • You host and operate it; no managed offering from the project
  • Pre-1.0 releases mean API and config churn
  • Admin tooling requires direct access to its database
  • Few independent reviews; community evidence is thin
  • Iceberg-first; other table formats are secondary

Sources & method

Analyzed 9/25/2026 - 10 sources - No Nessie-specific vulnerabilities found; one dependency CVE (HTTP/2 rapid reset) was patched in releases, and authn/authz are documented.

official x5review x2security x1news x2
  • CVE-2023-44487 (dependency), HTTP/2 rapid reset in Netty via Quarkus; addressed by a version bump in Nessie releases.

Key stats

  • Value for money: 5/5

    Rating

  • $0

    Starting price

  • 10

    Sources

  • Analyzed

  • Value for money: 5/5. Free, Apache-2.0, full feature set.
  • Ease of use: 2/5. Self-run service; admin tool needs direct DB access.
  • Feature depth: 4/5. Branches, merges, cross-table transactions, pluggable backends.
  • Support quality. No support evidence in sources.
  • Security posture: 3/5. Authn/authz documented; dependency CVE patched promptly.
  • $0 Starting price Open source, self-hosted
  • Apache-2.0 License Fully open source
  • 0.108.x Release line Pre-1.0 versioning
  • Yes Free tier Entire project is free

Pricing

Open source (self-hosted)

$0

  • Full catalog: branches, tags, cross-table commits
  • You provide the database, hosting, and operations
  • Managed commercial route exists via Dremio Arctic

Security

No Nessie-specific vulnerabilities found; one dependency CVE (HTTP/2 rapid reset) was patched in releases, and authn/authz are documented.

  • CVE-2023-44487 (dependency)HTTP/2 rapid reset in Netty via Quarkus; addressed by a version bump in Nessie releases.³

What users say

Independent user feedback is sparse; available commentary is positive but largely from the Dremio ecosystem.

“Project Nessie also powers Dremio's Arctic service”
Hacker News
“Project Nessie: Git-inspired data version control for Delta Lake and Iceberg. I totally like”
LinkedIn post

Alternatives

Compare Project Nessie with each alternative.

  • Dremio Arctic

    Managed Nessie; pay Dremio instead of self-operating.

  • AWS Glue Catalog + Iceberg

    Simpler managed catalog; enough for single-writer pipelines.

  • lakeFS

    Git-like versioning over object storage; different architecture.

    Project Nessie vs lakeFS

  • Hive Metastore / JDBC catalog

    Baseline Iceberg catalog if you don't need branches.

Companies that use it

Full analysis

Based on ~25 public sources, almost all official docs and release notes. No independent review ratings found, so user-sentiment conclusions are weak.

Free OSS 'git for data lakes' catalog. Strong fit for Iceberg lakehouses; overkill if you're not operating one.

Methodology

Based on ~25 public sources, almost all official docs and release notes. No independent review ratings found, so user-sentiment conclusions are weak.

Sources

  1. Project Nessie homepageprojectnessie.org
    official
  2. Nessie GitHub repositorygithub.com
    official
  3. Nessie release notesprojectnessie.org
    security
  4. Authorization (Access Control) docsprojectnessie.org
    official
  5. Nessie Server Admin Tool / export-importprojectnessie.org
    official
  6. DynamoDB version store configprojectnessie.org
    official
  7. Hacker News discussionnews.ycombinator.com
    review
  8. Dremio blog: Nessie catalog for lakesdremio.com
    news
  9. AWS Glue + Nessie/Arctic + Iceberg walkthroughmedium.com
    review
  10. Interoperable ACID transactions for open table formats (paper)dl.acm.org
    news

Rate this review

Anonymous. You can change your vote.

Loading votes…

Comments

One queue. No nested comments. Give a display name first. Limit: 200 words per comment and 7 comments per day. You can edit or delete yours.

Save a name to write a comment.

0 / 200 words

No comments yet.