Pricing at a glance
Scroll sideways to see all columns. With a keyboard, focus this table and use the arrow keys.
| Decision point | What Foundational states |
|---|---|
What you pay for | The number of tracked objects in the lineage graph, not seats. Cost grows with the overall complexity of the systems represented in that graph, not with team size. |
What every plan includes | The full data and AI governance platform: cross-platform lineage, impact analysis, data quality, data contracts and AI governance. |
Setup and services | Setup takes under an hour and works by authenticating Foundational to the relevant code repositories and to any BI tools, with no code changes or integration work, and no additional custom engineering or professional services. |
How to get a price | A form on the pricing page that asks for first name, last name, company email, company name and phone number. |
What the platform covers
Show full plan details
Scroll sideways to see all columns. With a keyboard, focus this table and use the arrow keys.
| Item | Detail |
|---|---|
Systems covered | Source control (GitHub, GitLab, Azure DevOps and Repos, Bitbucket); languages from SQL and Python to COBOL; ETL, ELT and query engines; BI platforms; databases and warehouses; and CRM systems including Salesforce, HubSpot and Workday. |
Mainframe lineage | COBOL, JCL, copybooks, Db2 and BMC, read from source code with read-only repository access; Foundational states it does not connect to the mainframe or to production Db2. |
Data access | Metadata only by default: schemas, table names, descriptions and dashboard names. Customer data is accessed only if you choose to activate data observability checks that validate the underlying data, such as null counts or distinct values; governance, lineage and CI checks stay fully functional without that access. |
Authentication and compliance | SOC 2 Type II compliant, with SSO and SAML configuration supported. |
How you use it | A web interface, a public API for programmatic access to real-time lineage, and an MCP remote server that gives AI tools lineage, usage and ownership context. |
- Vendor source · Observed · Stored official documentation capture for foundational. Claim-focused literal span 0:3209 of 3209 characters; omitted text is not evidence. Review retained billing conditions against these excerpts.
- Vendor source · Observed · Stored official documentation capture for foundational. Claim-focused literal span 4000:6719 of 6719 characters; omitted text is not evidence. Review retained billing conditions against these excerpts.
- Vendor source · Observed · Stored official documentation capture for foundational. Claim-focused literal span 2000:5871 of 5871 characters; omitted text is not evidence. Review retained billing conditions against these excerpts.
- Vendor source · Observed · Stored official documentation capture for foundational. Claim-focused literal span 0:4000 of 6719 characters; omitted text is not evidence. Review retained billing conditions against these excerpts.
Rollout timing
Foundational says organisations often start by governing high-risk pipelines first and typically see value within two to four weeks.
What drives the bill
Each system you connect adds to the graph: code repositories such as dbt, Spark and ORMs, warehouses and databases such as Snowflake and BigQuery, and BI and consumption platforms such as Tableau and Looker. Assets that are not defined in code arrive through scheduled scans of metadata, query logs and schema information, merged into the same graph, so warehouse views and dashboards sit alongside your code. A mainframe estate adds COBOL programs, JCL jobs, copybooks and Db2 tables from source code alone. When you ask for a quote, list the repositories, warehouses, BI tools and mainframe code you would connect, and ask what counts as a tracked object.
Costs that sit on your side
Exporting Foundational's computed lineage into a Collibra catalog requires a new or existing S3 bucket in your AWS account, with an optional prefix, and a cross-account IAM role. It also requires a Collibra Edge site in Healthy status with the Technical Lineage global permission; this may be self-hosted or a Collibra-managed Cloud site. Foundational re-exports on an interval set in days, with a minimum and default of 14, and the Collibra synchronization should run at least as often so no export goes un-ingested. Budget for that AWS storage and configuration and the Collibra-side setup alongside Foundational.
Our take
If your headcount grows faster than your systems, a price tied to the lineage graph keeps what you pay attached to systems rather than people. If you plan to connect many warehouses and BI tools at once, or bring a mainframe estate into the same graph, compare a quote for the first phase with one for the full estate.