Foundational vs Solidatus

    By Ari Bajo - data engineer turned writer.

    Updated on November 19, 2026

    Summary

    Both serve regulated teams that must prove where data flows, but they build lineage differently: Foundational parses source code, including COBOL, automatically and checks each pull request, while Solidatus maps lineage as visual models, partly by hand, and keeps version history to show lineage as of a past date. Neither has access policies; both sell by quote.

    Foundational and Solidatus differ on 22 of the 70 features in my data governance feature matrix and share 22.

    Foundational vs Solidatus at a glance

    CriterionFoundationalSolidatus
    What it isFoundational is a data control plane that builds a knowledge graph of code and data movement, with column-level lineage from source code, pull request impact analysis, and data contracts.Solidatus is a data lineage platform that maps data from source systems, including mainframes, through every transformation to reports at column level, links it to glossary terms and regulations, and keeps version history so you can show lineage as of a past date.
    Best forData and engineering teams that want to see the downstream impact of code changes in Git pull requests and govern data across repositories, databases, and BI.Compliance, risk, and governance teams in financial services that need lineage mapped as visual, explorable dependency graphs — not just lineage tables — to trace impact across complex, interconnected systems for audits.
    CategoryEnterprise data governanceEnterprise data governance
    Core strengthColumn-level lineage from source code (Python, Java, Scala, .NET, COBOL, SQL), with pull request impact checks and data contracts in GitLineage with version history — show regulators lineage as of a past date, from mainframes to reports
    PricingNot in my data yetQuote from sales
    Free optionNoneNone
    DeploymentSaaS, hybridSaaS, self-hosted, hybrid
    Features45 of 70 tracked44 of 70 tracked
    Notable caveatA lineage and change-control tool, not a full catalog: no glossary, access policies or marketplaceLineage only: no PII scanning, policy enforcement or data quality, and no public prices

    Key differences between Foundational and Solidatus

    The 22 features where only one of them is confirmed, by feature group. Each line says how the tool does it and links the source.

    Data Catalog

    • AI-Powered Search

      Foundational: not confirmed.

      Solidatus: Domain AI answers natural-language questions across a Data Domain and returns matching entities, assets, charts, and metrics in the conversation (docs).

    • Usage & Popularity Statistics

      Foundational: Tracks query frequency, access patterns and user activity per asset, with historical trends, to find unused tables and dashboards (docs).

      Solidatus: not supported.

    • Custom Fields & Templates

      Foundational: not confirmed.

      Solidatus: Models carry user-defined properties with typed definitions (text, number, date, choice lists, and more) on any entity or transition, organised into property folders (docs).

    • Asset Certification

      Foundational: Owners can set a certification status on assets, such as certified or deprecated, and filter by it (docs).

      Solidatus: not supported.

    • Business Glossary

      Foundational: not supported.

      Solidatus: Reference models hold business glossary terms in hierarchies and link them to lineage entities through labelled reference relationships; changes go through pull requests with an approvals workflow, and Purview glossaries sync both ways (docs).

    • Metadata Propagation

      Foundational: not confirmed.

      Solidatus: Reference relationships set on a parent entity are inherited by its descendants, so a term or classification applied to a table applies to its columns in queries and Data Maps (docs).

    Data Stewardship

    • Critical Data Elements

      Foundational: not supported.

      Solidatus: CDEs are modelled as reference terms and linked to the fields that feed regulatory reports, then queried and traced in domains (docs).

    • Metadata Automation

      Foundational: Workflows and Alerts automate notifications and reviewer assignment when specific changes or events occur (docs).

      Solidatus: not supported.

    Data Compliance

    • Compliance Reporting

      Foundational: not supported.

      Solidatus: Analytics reports count and chart entities by property or relationship (for example lineage coverage of regulated reports), and regulatory overlays generate versioned audit packs (docs).

    • Regulatory Framework Mapping

      Foundational: not supported.

      Solidatus: Regulations such as GDPR and BCBS 239 are held as reference models and linked to tables, columns, and reports through reference relationships (docs).

    Collaboration

    • Alert Notifications

      Foundational: Alerts to Slack, Microsoft Teams and email when changes affect downstream assets or contracts are violated (docs).

      Solidatus: not supported.

    • Discussions & Annotations

      Foundational: not supported.

      Solidatus: Users open discussion, question, or issue threads on a model and comment on them, though threads attach to the model rather than to a single column (docs).

    Data Marketplace

    • Subscription Management

      Foundational: Workflows notify chosen people when changes affect specific tables or dashboards (docs).

      Solidatus: not supported.

    Data Quality

    • SQL Table Tests

      Foundational: Contract business rules check required fields, value ranges and key uniqueness (docs).

      Solidatus: not supported.

    • Anomaly Detection

      Foundational: Observability monitors catch freshness and volume problems, with anomaly rules and custom thresholds (docs).

      Solidatus: not supported.

    • Data Profiling

      Foundational: Table statistics such as null counts, zero counts and distinct values per column, with custom thresholds; lighter than dedicated profilers (docs).

      Solidatus: not supported.

    • Data Contracts

      Foundational: YAML contracts (.fd.yml) next to the code, with schema, business, anomaly and SLA rules, checked on pull requests and continuously (docs).

      Solidatus: not supported.

    AI Governance

    • AI Regulatory Compliance

      Foundational: not supported.

      Solidatus: An EU AI Act overlay produces the training data provenance record required by Article 10 for high-risk AI systems (website).

    Workflows

    • dbt Integration

      Foundational: Parses dbt and dbt Fusion projects for column-level lineage and checks dbt changes on pull requests (docs).

      Solidatus: not confirmed.

    • Webhooks

      Foundational: not confirmed.

      Solidatus: Webhooks send signed HTTP POST payloads on the NewModelRevision event, the only event type, subject to a monthly licence limit (docs).

    Security

    • SCIM Provisioning

      Foundational: SCIM provisioning from Okta, Azure and other identity providers (docs).

      Solidatus: not supported.

    Deployment

    • Self-Hosted Deployment

      Foundational: not supported.

      Solidatus: Can be installed on-premises in the customer's data centre, including air-gapped setups, or in a private cloud tenancy (website).

    Foundational or Solidatus: which to choose

    Choose Foundational if

    Lineage should come from the code itself and stay current with every merged change.

    Foundational profile Foundational alternatives

    Choose Solidatus if

    Auditors need curated lineage models linked to regulations and glossary terms, as they stood on a past date.

    Solidatus profile Solidatus alternatives

    What both Foundational and Solidatus do

    22 features supported by both
    • Data Catalog: Automated Metadata Harvesting, Search & Discovery
    • Data Lineage: Table-Level Lineage, Column-Level Lineage, End-to-End Lineage, Impact Analysis, Automated Lineage Extraction, OpenLineage Support
    • Data Stewardship: Review & Approval Workflows
    • AI Features: AI Chat Assistant, AI Documentation Generation
    • Data Compliance: Audit Trail
    • AI Governance: AI Lineage
    • Workflows: REST / GraphQL API
    • Data Context Layer: MCP Server, Knowledge Graph
    • Security: SSO, RBAC, Audit Log, Compliance Certifications
    • Deployment: SaaS Deployment, Hybrid Deployment

    Foundational vs Solidatus integrations

    Foundational lists 95 integrations and Solidatus 30; 18 are on both lists. See the integrations matrix for all tools.

    Foundational vs Solidatus FAQ

    What is the difference between Foundational and Solidatus?

    Both serve regulated teams that must prove where data flows, but they build lineage differently: Foundational parses source code, including COBOL, automatically and checks each pull request, while Solidatus maps lineage as visual models, partly by hand, and keeps version history to show lineage as of a past date. Neither has access policies; both sell by quote.

    Is Foundational or Solidatus cheaper?

    Foundational: Not in my data yet. Solidatus: Quote from sales. Prices come from each vendor's pricing page.

    Which has more features, Foundational or Solidatus?

    Foundational supports 45 and Solidatus 44 of the 70 features in my data governance feature matrix. They share 22 and differ on 22; only Foundational has usage & popularity statistics, asset certification and metadata automation; only Solidatus has AI-Powered search, custom fields & templates and business glossary.

    Can Foundational and Solidatus be self-hosted?

    Foundational: SaaS, hybrid. Solidatus: SaaS, self-hosted, hybrid.

    Data from my data governance feature matrix, checked against each vendor's docs, and pricing pages. For more options, see the best data governance tools.

    Evaluating data tools in 2026?

    I curate the most comprehensive lists of data tools, up-to-date comparison tables, and actionable market guides for data teams. More useful than a Gartner report. More reliable than asking AI. Next up: Data FinOps.