Find Open-Source Alternatives
Discover powerful open-source replacements for popular commercial software. Save on costs, gain transparency, and join a community of developers.
Discover powerful open-source replacements for popular commercial software. Save on costs, gain transparency, and join a community of developers.
Compare community-driven replacements for AWS Glue Data Catalog in data catalogs & governance workflows. We curate active, self-hostable options with transparent licensing so you can evaluate the right fit quickly.
These projects match the most common migration paths for teams replacing AWS Glue Data Catalog.
Why teams pick it
Organizations with data spread across multiple clouds, regions, or on-premises systems
Run on infrastructure you control
Recent commits in the last 6 months
MIT, Apache, and similar licenses
Counts reflect projects currently indexed as alternatives to AWS Glue Data Catalog.
Why teams pick it
Organizations adopting data mesh or decentralized data ownership
Powerful platform for publishing, sharing, and managing open data
Why teams choose it
Watch for
Requires Python and PostgreSQL expertise to deploy
Migration highlight
National open data portal
Provides a centralized catalog, public API, and searchable interface for all government datasets, improving transparency and citizen engagement.
Unified data discovery, lineage, and observability platform
Geo-distributed federated metadata lake for unified data governance
Unified metadata governance for Hadoop and enterprise data ecosystems
Unified platform for data discovery, governance, and observability
Google‑style search engine for data assets across your organization
Federated data catalog with scalable search and Kubernetes‑native deployment
Centralized metadata service for data lineage and lifecycle
Unified metadata platform for modern data discovery and governance
Teams replacing AWS Glue Data Catalog in data catalogs & governance workflows typically weigh self-hosting needs, integration coverage, and licensing obligations.
Tip: shortlist one hosted and one self-hosted option so stakeholders can compare trade-offs before migrating away from AWS Glue Data Catalog.
Why teams choose it
Watch for
Requires a PostgreSQL backend to store metadata
Migration highlight
Accelerate dashboard creation
Analysts quickly locate source tables and understand lineage, reducing time to build reliable BI reports.
Why teams choose it
Watch for
Windows builds are not currently supported
Migration highlight
Multi-Cloud Data Lake Federation
Unified metadata access across AWS S3, Azure Data Lake, and on-premises HDFS, enabling cross-cloud analytics without data migration.
Why teams choose it
Watch for
Primarily focused on Hadoop ecosystems
Migration highlight
Regulatory compliance reporting
Generate audit‑ready lineage reports to demonstrate data handling compliance.
Why teams choose it
Watch for
Self‑hosting requires operational expertise and resources
Migration highlight
Centralized Data Catalog
Teams locate tables, dashboards, and pipelines from a single searchable UI, reducing time spent searching for assets.
Why teams choose it
Watch for
Requires multiple services (frontend, search, metadata) to run
Migration highlight
Find frequently queried tables for ad‑hoc analysis
Analysts locate high‑usage tables instantly, cutting discovery time from days to minutes.
Why teams choose it
Watch for
Requires Kubernetes expertise for installation and upgrades
Migration highlight
Cross‑agency open data portal
Aggregates datasets from multiple government portals, providing citizens a single searchable interface.
Why teams choose it
Watch for
No built‑in authentication or authorization
Migration highlight
Data pipeline debugging
Visual lineage graphs let engineers pinpoint failing jobs and understand upstream dataset impacts.
Why teams choose it
Watch for
Initial setup can require infrastructure expertise
Migration highlight
Cross‑source Data Discovery
Analysts can search across databases, dashboards, and pipelines from a single UI, reducing time to find relevant assets.