Comparison

Mage Data vs Perforce Delphix: Test Data Management Comparison

Both deliver protected test data, and they came at the problem from opposite directions. That difference decides where each one fits.

By the Mage Data Team · November 2026

On this page

Mage Data and Perforce Delphix both deliver protected test data, and they came at the problem from opposite directions. Delphix started with database virtualization and added masking. Mage Data started with data discovery and protection, and added delivery. That difference decides where each one fits.

How does Perforce Delphix approach test data management?

Perforce Delphix is a DevOps data platform built around database virtualization. It creates virtual copies of databases from shared data blocks, so teams get full-size working environments in minutes instead of waiting for physical copies. Perforce reports support for more than 170 data sources.

The platform has two main products. Continuous Data handles virtualization, with refresh, rewind, bookmark and branch operations that let teams move an environment to a known data state. Continuous Compliance handles masking, using discovery templates built for specific applications and regulations, then applying irreversible masking algorithms or tokenization.

Perforce completed its acquisition of Delphix on 25 March 2024.

How does Mage Data approach test data management?

Mage Data is a data security platform. Test data management is one capability within it, alongside production data protection and compliance automation. The platform starts with discovery: a patented, score-based engine classifies sensitive data across databases, files, data lakes, warehouses, logs and packaged applications, including content inside free-text fields.

A policy maps each classification to a protection method, and that policy then governs every way data is delivered. Test data management covers in-place masking of an existing copy, extract-mask-load pipelines that protect data in transit, file gateways that mask files as they land in object storage, and database virtualization serving writable copies from one masked golden snapshot. Masking is deterministic across systems, so the same customer looks the same everywhere and joins still work.

Is Delphix a test data management tool or a database virtualization tool?

Both, and the order it was built in still matters. Delphix began as database virtualization and added masking later, which is why the two ship as separate products within the platform rather than as one.

For an evaluation this has two practical consequences. First, check which product carries the capability you need and whether both are licensed. Second, when a capability sits in a separate product, it brings its own configuration and its own audit trail, so the number of places a protection rule has to be defined goes up.

Mage Data takes the opposite approach by design. Classification and protection are defined once, and virtualization is one of several delivery paths that enforce the same policy.

Key differences at a glance

Perforce Delphix

  • Virtualizes databases and serves virtual copies from shared blocks, with refresh, rewind, bookmark and branch.
  • Masking ships as a separate product within the platform, Continuous Compliance.
  • Discovery works from templates built for specific applications and regulations.
  • Subsetting is not central to the approach, because virtualization makes full copies cheap.
  • Strongest where the estate is relational and environment lead time is the constraint.

Mage Data

  • Discovery runs first, across databases, files, lakes, warehouses, logs and packaged applications, including free text.
  • One policy maps each classification to a protection method, and every delivery path enforces it.
  • Four delivery paths plus virtualization: in-place, extract-mask-load, file gateways, self-service.
  • Intelligent Subsetting from a single driver condition, with referential integrity resolved automatically.
  • Strongest where sensitive data is spread beyond databases and the control has to be provable.

How do Delphix and Mage Data differ?

Mage Data Perforce Delphix
Origin Data security platform Database virtualization
Database virtualization Yes, masked at snapshot creation Yes, with refresh, rewind, bookmark and branch
Sensitive data discovery Score-based across structured, free-text and unstructured content Discovery templates for specific applications and regulations
Static masking Irreversible, method selected per classification Irreversible algorithms and tokenization
Data subsetting Intelligent Subsetting from one driver condition Not central to the approach
Delivery paths under one policy In-place, extract-mask-load, file gateways, virtualization Virtualization and masking as separate products
Synthetic data Not yet generally available Synthetic values via Delphix AI
Scope Test data as one capability of a data security platform Test data and DevOps data management
Ownership MENTIS Inc, independent Perforce Software, since March 2024

Both platforms virtualize databases, both mask irreversibly, and both preserve referential integrity so joins survive. The differences are in discovery breadth, subsetting, and how many delivery paths one policy reaches.

See it on your own data

Discovery is the part of this comparison you can test in an afternoon. Send us one source system and we will show you what classification finds in it, including the false positives. Book a demo →

Does Delphix do data subsetting?

Not as a central part of its approach, and that is a design choice rather than a gap. The logic is that virtualization makes full-size copies cheap enough that shrinking them becomes less necessary. Bloor Research has made the same observation in its test data management research.

The logic holds until a team needs a small targeted dataset for a specific test, or a third party can only receive the minimum necessary records, or a data minimisation obligation applies to what leaves production at all.

Mage Data's Intelligent Subsetting takes one driver condition, such as customers in a single region, and resolves upstream and downstream referential integrity automatically. Subsetting can also run in transit, as part of an extract-mask-load pipeline, so the smaller dataset is produced on the way to its destination rather than afterwards.

How does Delphix handle files and unstructured data?

Virtualization operates on databases, so for data that sits outside a database the question is what governs it and whether the same policy applies. This matters more than it used to, because a growing share of sensitive content in non-production environments is in files, extracts and documents rather than in tables.

Delphix's masking product, Continuous Compliance, identifies sensitive data using discovery templates and masks it. For a file estate, ask specifically which formats are covered, how files arriving continuously are handled, and whether that path shares a policy with the database masking.

Mage Data runs file gateways that detect files landing in object storage or a directory, mask their contents and forward them, under the same policy that governs database masking. Discovery also reads inside free-text fields, which is where account numbers and identifiers often end up after a support call.

What changed after Perforce acquired Delphix?

Perforce completed the acquisition on 25 March 2024, and has continued to develop the platform alongside its wider DevOps portfolio. The products and their names have carried over.

For a customer the useful check is the same as for any ownership change, and it does not depend on anyone's prediction. Compare release notes for the twelve months before and after. Check whether support lifecycle announcements have changed in tone or cadence. Look at what moved in your renewal terms. If none of those have shifted against you, the acquisition is not a reason to move.

One thing worth confirming directly: whether virtualization and masking are still licensed as separate products or have been bundled. Licensing structures often change quietly after an acquisition.

When should you choose Delphix, and when should you choose Mage Data?

Both platforms deliver protected test data. The decision usually comes down to where your sensitive data actually sits and what is slowing your teams down.

Choose Perforce Delphix when Choose Mage Data when
Your estate is mostly relational databases and the pressing problem is how long a full-size environment takes to arrive. Sensitive data also sits in files, extracts, documents and free-text fields, and you need one policy to cover all of it.
Teams need to bookmark a data state, reproduce a defect against it, then rewind. Data versioning is part of how they work. You need to prove what was in a named environment on a named date, with an exportable record per copy.
You have standardised on Perforce for the rest of the DevOps toolchain. You are consolidating discovery, masking and provisioning rather than buying another point tool.
Full copies are what testing needs, and subsetting is not a requirement. You need small, referentially intact subsets, or a third party can only receive the minimum necessary records.
Virtualization performance across a defined list of database platforms is the main technical constraint. Discovery has to find sensitive data nobody labelled, including inside free text and key-value structures.

If you already run Delphix, the question is usually not replacement. It is what sits outside the virtualized databases, and who governs that today. Where that list is short, Delphix covers the problem. Where it is long, the gap is worth measuring before the next renewal.

What should you test before choosing?

Both vendors will demo well. Every platform works on data it has been tuned against, which is why the only useful test is one run on your own schema, with your own awkward cases in it. Six tests, and what each one tells you.

Put an account number inside a free-text field, then run discovery.

You are testing whether classification reads content or only column names and patterns. Ask for the false positives too. A platform that finds everything by flagging everything has not solved the problem.

Mask one customer identifier and trace it.

Show the same value in a database table, a file in object storage, and an extract landing in your warehouse. If it matches in all three, cross-system testing still works after protection. If it only matches inside the database, every join that crosses a boundary becomes your problem.

Generalize a numeric field, then check the arithmetic.

Round a quantity into a band so it cannot be matched against public data, and see whether the fields derived from it move with it. This separates the field fastest. If the answer involves a services engagement or a custom script, you have your answer.

Count the places one rule has to be defined.

Take a single protection rule and ask how many times it must be configured to cover every delivery path you actually use. One is a platform. Four is four tools with a shared logo.

Time a provisioning run, including the approval.

Use a database of your size, not a reference dataset, and start the clock where a requester would start it. The number that matters is request to usable environment, not job runtime.

Ask for the audit record, not the dashboard.

Name an environment and a date, and ask what the platform can produce about what was in it and how it was protected. An assessor needs an exportable artefact. A screen is not one.

Frequently asked questions

What is test data management?

Test data management is the practice of finding sensitive data, protecting it, and delivering realistic, referentially intact copies to the teams and systems that build and test software. It now covers more than developers and QA. The same production-shaped data feeds performance testing, analytics, AI training pipelines, third-party processors and auditors, and each needs a different shape of it.

What is data virtualization in test data management?

Data virtualization creates lightweight, writable copies of a database that share storage with one master copy, so each team gets what behaves like a full database without storing a full copy. It reduces storage cost and provisioning time. It does not, on its own, decide what in the copy is sensitive or whether it has been protected, which is why virtualization and masking are usually separate capabilities.

What are the main alternatives to Perforce Delphix?

The alternatives most often evaluated for test data management are Mage Data, K2view, Informatica, IBM InfoSphere Optim, Broadcom Test Data Manager and Tonic.ai. They differ mainly in whether they provision whole databases or targeted subsets, how broadly they discover sensitive data, and how many delivery paths run from a single policy.

When should you look at a Delphix alternative?

When sensitive data sits outside relational databases, in files, extracts, documents or free-text fields. When testers need targeted subsets rather than full copies. When a third party can only receive the minimum necessary records. Or when you need one exportable record showing what was in a named environment on a named date, covering every delivery path rather than the virtualized databases alone.

Can Delphix and Mage Data be used together?

Yes, and some organizations do run virtualization for relational environments alongside a separate control for files and extracts. It works. It also means two policy definitions and two audit trails to reconcile, so the cost worth quantifying is the reconciliation effort, not the licences. Where that cost is low, coexistence is reasonable. Where it is high, it is usually a stage rather than a destination.

How does test data management support PCI DSS and GDPR compliance?

PCI DSS v4.0.1 Requirement 6.5.5 bars live primary account numbers from pre-production environments, unless that environment is included in the cardholder data environment and protected under all applicable PCI DSS requirements. Under GDPR, the EDPB’s Guidelines 01/2025 on Pseudonymisation confirm that pseudonymized data which can still be attributed to a person using additional information remains personal data. In practice, both point to the same requirement: protection applied before the copy exists, and a record that shows it.

What about data used to train AI models?

Training and evaluation sets are copies of production like any other, and they tend to be the least governed because they are created by engineering activity rather than by a business process. The control point is extraction, before the data reaches the pipeline, because a model cannot be made to unlearn what it was trained on without retraining. Treat an AI training set as another consumer of test data, governed by the same policy.

Does masking slow down provisioning?

It depends on where masking happens. If a copy is created and then masked, masking is an extra step in the critical path, and there is an interval during which real production data sits in a non-production environment. If masking is applied when the golden snapshot is created, copies taken from it are protected on arrival and provisioning is unaffected. Ask which of the two the architecture does, because it is a design property rather than a setting.

The bottom line

Delphix solved a real problem and solved it first. If your sensitive data lives in relational databases and your teams are waiting on environments, that is still the problem it solves best.

The question is whether it is still the problem you have. For most enterprises the sensitive data that causes trouble has spread — into files in object storage, extracts feeding analytics, free-text fields nobody classified, training sets nobody logged. Virtualization does not reach those. Something else governs them, usually a script and the person who wrote it.

So the comparison comes down to one thing: how much of your non-production estate sits outside what virtualization covers, and who is accountable for it.

You can work that out without us. List your non-production environments. Mark which hold data from production. Mark which are covered by a policy you could show an auditor. If the second number is much larger than the third, that gap is your actual problem, and it is worth sizing before your next renewal.

Book a demo

Thirty minutes. We will show you discovery running against free-text fields and unlabelled columns, one policy applied across a database, a file and a warehouse extract, and the audit record it produces.

Last updated November 2026 · This comparison is based on public product documentation as of November 2026. Perforce and Delphix are trademarks of Perforce Software, Inc. Mage Data is not affiliated with Perforce. Mage Data offers a competing product in the test data management category.