Syntho Engine connectors

How to connect to the source data and target environment

Book a demo

Supported connectors

Connect to the source data and target environment
with our out-of-the-box connectors.

Syntho can connect with every leading database & filesystem and supports 20+ database connectors and 5+ filesystem connectors.

As we support various out-of-the-box connectors that are included in our Syntho Engine, you will be able to easily configure your synthetic data generation job and connect the Syntho Engine to the source environment and the target environment.
As a result, Syntho colleagues will never see your original data and will not require access to your Syntho Engine and your save environment.

My required connector is not listed?

Note that the illustration shows only some connectors that we support as examples. The full list of supported connectors contains more connectors.

In the case that Syntho doesn’t have a native (built-in) connector for your data, you can request it with your Syntho contact person. Syntho regularly reviews requests by customers to help determine and prioritize what features should be added to the product. Required connectors can be built for customers who are on a yearly license with no additional costs.

Save your synthetic data guide now

What is synthetic data?

How does it work?

Why do organizations use it?

How to start?

Privacy Policy

How to connect to data?

01
Connect to source data

Syntho enables you to easily connect with the source data that is stored in your source environment. The source data is the data that you would like to synthesize and the Source Environment is the location where the source data is stored, which could be a database or filesystem.

02
Connect to target environment

Syntho enables you to easily connect with the target environment. The target environment is the environment where you would like to write the generated synthetic data to, which could be a database or filesystem.

Frequently Asked Questions

Why do organizations use mockers?

PII, PHI, and other direct identifiers are sensitive and can be spotted manually or automatically with our PII scanner to save time and minimize manual work. Then, one can apply Mockers to substitute real values with mock values to de-identify data and enhance privacy.

What are examples of PII, PHI, and identifiers?
  • First name
  • Last name
  • Phone number
  • Social Security Number, SSN
  • Bank number, etc.
What is PII, PHI and what are identifiers?

PII stands for Personal Identifiable Information. PHI stands for Personal Health Information and is an extended version of PII dedicated to health information. Both PII and PHI are identifiers and relate to any information that can be used to distinguish or trace an individual’s identity directly. Here, with identifiers, only one person shares this trait.

Why do organizations use Test Data Management?

Production data is privacy-sensitive
Testing and development with representative test data is essential to deliver state-of-the-art software solutions. Using original production data seems obvious, but is not allowed due to (privacy) regulations according to the GDPR and the Dutch Data Protection Authority. This introduces challenges for many organizations in getting the test data right.

 

Production data does not cover all test scenarios
Test data management is essential because production data often lacks the diversity required for comprehensive testing (or does not (yet) exist at all), leaving out edge cases and potential future scenarios. By creating and managing diverse test data sets, it ensures thorough testing coverage and helps identify potential issues before deployment, mitigating risks and bugs in production to enhance software quality.

 

Optimize testing and development
Let your testers and developers focus on testing and development, instead of test data creation. Test data management optimizes testing and development by maintaining and updating test data, saving developers and testers time typically spent on data preparation. Automation of test data provisioning and refreshing ensures data relevance and accuracy, allowing teams to focus on analyzing results and enhancing software quality efficiently. This streamlined process improves overall testing speed, agility, and productivity in the development lifecycle.