Get the whitepaper!
The Test Data Imperative: Towards SAP Autonomous Enterprise

Fixed scope · Fixed feeCredited when you go ahead

Prove it on 50 of your documents in 48 hours

One document type, inside your environment. You get a masked set, or a synthetic set with the true values behind every field, plus an entity report and a 30-minute readout. The 48 hours start once access is ready.

Book the proofHow the 48 hours run
Proof · KYC packs · 50 documentsHour 46 of 48Illustration
Documents
50 of 50
Values found
1,286
Categories
9
Policy
KYC starter
Found, by category
Names412
Addresses188
Free-text identifiers179
Account numbers140
Dates of birth96
Emails83
Phone numbers77
ID numbers61
Signatures50
You getMasked setSynthetic set + true valuesEntity report (CSV)30-min readout
Illustration. Your document type, your checks.
The platform underneath, in production

Documents run on the same platform banks and insurers already trust with their test data.

Documents and text use the same policies, the same engine and the same deployment as these results.

Banking · test data80%less time to provision test data, with compliant data generated through the API inside CI/CD.Deutsche BankCase study
Insurance · security0security waivers across 14 priority applications: 28M+ rows secured, 100% referential integrity, test data 60% faster.Global specialty insurerCase study

Published results from database and synthetic data work on the Synthesized platform.

How the 48 hours run

Enough to see what's in your files, what a masked or synthetic set looks like, and whether it's ready for your team.

  1. Before hour 0We send the security pack first. Your team approves one machine and read access to one folder. The clock starts when both are ready.
  2. Hour 030-minute kickoff. We install in your environment and agree the checks that matter to you.
  3. Hours 1–24Find the personal data in all 50 documents and treat it to a starter policy.
  4. Hours 24–46Build the masked set, or the synthetic set with the true values, and check a labelled sample.
  5. Hour 4830-minute readout: what was found, the result of each check, and the next step.

You'll need: a machine in your environment we can install on, read access to one folder of 50 documents of one type, and someone who can approve access.

Book the proof
Readout · KYC packs · hour 48CompleteIllustration
Access readyFind, treatBuild, checkReadout
CheckTargetResult
Find
Names, DOBs, addresses, IDs
Your threshold
Met
Pass
Protect
Re-scan for original values
None left
None left
Pass
Preserve
Files open in your app
All 50
All 50
Pass
Use
Extraction scored on the set
Your threshold
Met
Pass
Saved job, policy and run record handed overNext step: subscription
Illustration. You choose the checks and the thresholds on the kickoff call.

What the readout checks

You choose the checks that matter on the kickoff call. At hour 48, each one is a yes or a no.

01
Find
Every entity type you name is found in a labelled sample of your documents, at the rate you set.
02
Protect
Every named category is replaced, tokenized or redacted to your rules, and a re-scan finds no original values.
03
Preserve
Documents still open and work in your application, and one person keeps one replacement across the set.
04
Use
Your testers, models or reviewers can work with the set: extraction scored, scenarios run, pages reviewed.
05
Repeat
The job is saved, so the next batch runs with the same policy and no code changes.
06
Evidence
A run record and re-scan results you can hand to security or privacy.

One proof, three kinds of team

Same platform, same rules, same 48 hours. What you bring decides what we prove.

Test data and SAP teams
Documents beside your databases
The PDFs, scans and notes that ride along with a test refresh, masked with the same rules as the tables.
Bring: 50 documents from the store behind one application
Dev and test environments
AI and ML teams
Documents you can test and train on
Masked source documents for retrieval and fine-tuning, or synthetic documents with the true values for scoring extraction.
Bring: 50 documents of one type, such as statements or claim forms
Document AI testing
Privacy, legal and data teams
Archives you need to share or sell
Mailboxes, workspace exports and file shares, de-identified under one policy, with evidence for every batch.
Bring: 50 files from the archive; the full archive follows as a fixed-fee project
Data licensing

Book your 48-hour proof

It starts with a 30-minute kickoff call. Your work email and company are all we need to book it.

Thanks, you're booked in. We'll email you a link to choose a slot for the kickoff, with the security pack.
That didn't go through. Try again, or email team@synthesized.io and we'll book you in.

Two fields. We ask everything else on the call.

What happens next
  1. 1Pick a timeWe email you a link to choose a slot for the kickoff.
  2. 2Security packSent with the invite, so access can be approved before the call.
  3. 3Kickoff, then 48 hoursWe agree the checks, install, and the clock starts once access is ready.

Fixed fee, credited in full when you go ahead. Your documents stay where they are.

How it's priced

A fixed fee to start, credited when you go ahead, then the same subscription as the rest of the platform.

Start here
48-hour proof
  • Fixed fee, agreed up front
  • 50 documents of one type, in your environment
  • Masked or synthetic set, entity report and readout
  • Credited in full to your subscription
Then
Platform subscription
  • A document store counts as a source, like any database
  • Sized by production data in scope and number of sources
  • Scans and image-heavy files count at a fraction of their stored size
  • Unlimited non-production copies, no usage or token charges
When you need it
Engineer-led projects
  • Archive de-identification and data-sale preparation
  • Scoped after the proof, fixed fee
  • Policy and evidence handed over for re-use

Buy direct or through a systems integrator.

You leave with

  • A masked set, or a synthetic set with the true values behind every field.
  • An entity report: what was found, by category and by document.
  • A policy for the categories in scope, yours to keep.
  • A saved job your team can run on the next batch.
  • A 30-minute readout with re-scan results and a recommended next step.
Good fit
  • Personal data in documents reaches test, AI or third parties today.
  • You can name one document type that matters most.
  • There's a date that matters: an audit, a release, a regulation or a deal.
You'll need
  • A machine in your environment we can install on
  • Read access to one folder of 50 documents
  • Someone who can approve access and join the readout

Questions about the 48-hour proof

What does it cost?

A fixed fee, agreed before we start and the same for every proof of the same scope. It is credited in full against your subscription when you go ahead.

When do the 48 hours start?

When access is ready. We send the security pack with the calendar invite, so your team can approve one machine and one folder before the kickoff. The clock starts once both are in place.

Is 50 documents enough?

Enough to see what is in your files, how each category is treated and whether the output works in your application. The saved job then runs on the rest with the same policy.

What if our security team needs more?

We can extend the proof into a longer pilot on your own criteria, scoped on the call. Most teams go straight from the readout to a subscription.

Do our documents leave our environment?

No. Synthesized is deployed in your environment, on-premises or in your cloud, and connects read-only with the access you approve.

Can a systems integrator run it with you?

Yes. Your integrator can join the proof and run the job afterwards.