Summary Google Cloud Dataplex now surfaces as Knowledge Catalog, Google's governed metadata and data-to-AI context layer. See pricing, features, and free tier limits. Databricks Unity Catalog is a unified data and AI governance layer for access control, discovery, lineage, auditing, data quality, and secure sharing. Microsoft Purview review: features, pricing, pros, cons, best use cases, and how it fits AI data governance workflows. Pricing Model Freemium Freemium Paid Starting Price Free + from $0.06/per DCU-hour Free + Premium Paid Current Version — — — Category Rankings Strengths Real free tier makes it possible to evaluate metadata discovery before committing meaningful spend Unified catalog, lineage, quality, and profiling can reduce tool sprawl for teams that prefer a Google-native governance stack Strong fit for teams already using BigQuery, BigLake, and broader Google Cloud data infrastructure Policy application and basic data organization features are included without separate Dataplex processing charges Deeply integrated with Databricks workspaces, SQL warehouses, notebooks, jobs, models, and feature workflows Centralized permissions and metadata reduce workspace-by-workspace governance drift Automated lineage is valuable for impact analysis and compliance Supports data, files, functions, models, and AI assets, not only tables Focused fit for data, security, privacy, compliance, and analytics teams. Public site clearly positions the product around AI data governance rather than a vague all-purpose AI workflow. Can reduce repetitive manual work when the first use case is scoped well. Works as part of a broader ToolWorthy stack because it connects naturally to adjacent categories and workflows. Limitations Pricing is usage-based and more complex than a simple SaaS per-seat model Biggest value appears inside Google Cloud; it is not the most neutral choice for mixed-cloud estates Some workflows create secondary charges in other Google Cloud services, which makes total cost harder to predict Gemini-powered features are not bundled into ordinary Dataplex pricing, so AI-related value can feel split across products Best fit is Databricks-centric environments Teams outside Databricks may still need a broader cross-platform catalog Setup requires understanding metastores, catalogs, schemas, external locations, and compute access modes Some functionality depends on Databricks Runtime and workspace configuration Pricing may require a sales conversation or careful plan comparison before procurement. The public homepage does not replace hands-on testing with your own data, assets, forms, audio, or business process. Teams still need ownership for templates, approvals, access control, and output review. Advanced integrations, compliance, or enterprise deployment details may require vendor confirmation.