What's the difference between TestGen open source and Enterprise?

TestGen open source and Enterprise run the same engine, so profiling, generated tests, hygiene checks, monitors, and the MCP server are in both, as of TestGen 5.134.0 in October 2026. Enterprise adds unlimited users, connections, and projects, SSO, role-based access control, PII masking, the 12 Commercial Pharma test types, hiding source data from AI clients, and DataKitchen support.

Key points

  • As of TestGen 5.134.0 in October 2026, open-source and Enterprise TestGen share one engine: 55 profiled column characteristics, 32 hygiene detectors, 34 generated and 19 configured test types, four monitor types, and an MCP server with 96 tools.
  • Open-source TestGen is limited to one user, one database connection, and one project; Enterprise removes all three limits.
  • Enterprise-only security features in October 2026 are single sign-on, role-based access control, PII masking, and custom branding.
  • Two Enterprise-only TestGen capabilities target specific risks as of 5.134.0: the 12 Commercial Pharma test types released August 27, 2026, and the MCP option to hide source data from AI clients released October 14, 2026.
  • File and DuckDB connections and Table Comparison migration tests shipped in both TestGen editions in release 5.134.0 on October 14, 2026.

The engine is the same. The difference is who can use it, how many databases it can reach, and two capabilities that exist for specific risks: pharma identifiers and AI clients reading your data. Price is a separate question, and Is DataOps TestGen free? answers it.

Feature by feature, as of TestGen 5.134.0

Sources are the October 2026 pricing page, the TestGen product page, and the release posts linked in each row.

CapabilityOpen sourceEnterprise
Users1Unlimited, $100 per user per month
Database connections1Unlimited, $100 per connection per month
Projects1Unlimited
Tables and data volumeUnlimitedUnlimited
Profiling, 55 column characteristicsYesYes
Hygiene detection, 32 detectorsYesYes
Generated tests, 34 types, plus 19 configured typesYesYes
Commercial Pharma tests, 12 types (August 27, 2026)NoYes
Monitors: freshness, volume, schema, custom metricsYesYes
Quality scorecards and data catalogYesYes
Every supported database, plus files and DuckDBYesYes
Files and DuckDB (5.134.0)YesYes
Table Comparison migration tests (5.134.0)YesYes
MCP server, 96 toolsYesYes
Hide source data from AI clients (5.134.0)NoYes
Single sign-onNoYes
Role-based access controlNoYes
PII maskingNoYes
Custom brandingNoYes
Self-hosted, Docker or KubernetesYesYes
SupportCommunity, on GitHubDataKitchen support
ReleasesCommunityPriority
LicenseApache 2.0DataKitchen subscription

What both editions share

Everything that finds problems. The open-source edition profiles, generates tests, runs hygiene detectors and monitors, scores quality, and exposes all of it to an AI client over MCP. DataKitchen’s Periodic Table of Data Quality puts every check on one page and marks the only Enterprise tile, the pharma pack.

That design is deliberate. A free edition that holds back its best tests is a demo. You can’t judge a data quality tool on a demo, and you shouldn’t have to buy it to find out whether it catches anything in your data.

What only Enterprise adds

Room for a team

More users, more connections, more projects. Open source stops at one of each, and Enterprise removes the cap on all three.

Security and access

Single sign-on, role-based access, PII masking, and custom branding. These matter once a data steward, an analyst, and an engineer all look at the same results and shouldn’t all see the same columns.

Two risk-specific capabilities

The Commercial Pharma pack validates NPI, NDC, DEA, ICD, HCPCS, CMS Place of Service, and NCT numbers against their specifications, which a generic length or pattern check never does. And the hide-source-data option lets you connect Claude, Cursor, or Copilot to a regulated database without sending the values in it to the model.

Which edition fits you

Use open source if you are one engineer on one database, or if you are evaluating. Your tests and profiles carry over when you upgrade, according to the pricing page, so evaluating on open source costs you nothing later.

Move to Enterprise when a second person needs to review results, when you add a second database, when you work with commercial pharma identifiers, or when an AI client will touch data you can’t show it. Any one of those is enough.

Frequently asked questions

Short answers to the follow-up questions people ask next.

Does open-source TestGen have fewer tests than Enterprise?

Only in one domain. As of TestGen 5.134.0 in October 2026, every test type is in open source except the 12 Commercial Pharma types, which validate healthcare identifiers such as NPI, NDC, and DEA. Profiling, all 32 hygiene detectors, the 34 generated test types, and the four monitor types are in both editions, per DataKitchen's Periodic Table of Data Quality.

Does open-source TestGen support single sign-on?

No. As of October 2026, single sign-on and role-based access control are TestGen Enterprise features, along with PII masking and custom branding, per DataKitchen's pricing page. Open-source TestGen is built for one user, one database connection, and one project, so it has no team access model to control. Enterprise adds unlimited users at $100 per user per month.

Which TestGen edition do I need for NPI and NDC validation?

TestGen Enterprise. The Commercial Pharma generation set, released August 27, 2026, adds 12 healthcare-identifier test types: NPI, DEA, three levels of NDC, ICD-9 and ICD-10, HCPCS J-codes, CMS Place of Service, and NCT numbers. They generate from your profiling run when the column name and values agree. The release post explains each check.

What does hiding source data from AI clients do in TestGen?

It keeps the values in your tables out of everything the TestGen MCP server returns, while counts, structure, and configuration stay visible. An AI client can still read failures and write tests, while values such as a patient name never reach it. It is an Enterprise feature, released in TestGen 5.134.0 on October 14, 2026. The rest of the 96-tool MCP server is open source.

Can open-source TestGen read files and DuckDB?

Yes. Since TestGen 5.134.0, released October 14, 2026 in both editions, open-source TestGen profiles, tests, and monitors CSV, Parquet, and JSON files on a local path, in Amazon S3, or in Azure Blob Storage, plus DuckDB database files. An embedded DuckDB engine reads the files in place, so there is no warehouse to stand up and no load step.

Try it on your own data

DataOps TestGen is free and open source. Profile a table and generate its tests this afternoon.