When should you consider it?
Best for engineering teams that want workflow-driven database masking, synthetic test-data generation, and relational subsetting integrated into development pipelines.
Editorial fit assessment based on the sources below.What are the limits?
TDK is the current platform documented for these test-data operations; Synthesized also publishes a distinct Python SDK, so confirm which product and workflow a comparison names.
Which capabilities are documented?
Documented means a cited vendor source describes this scoped capability. Not verified means the reviewed evidence cannot establish it. Neither is a hands-on test result.
How is it deployed and licensed?
The current TDK documentation describes Docker Compose and Kubernetes Helm deployment, plus CLI and API workflows.
The reviewed documentation describes platform licensing and administration but does not publish current prices or a complete license schedule.
Sources and scope
- Synthesized Platform Documentation (TDK)
Current version, masking, generation, subsetting, deployment methods, and current TDK product identity.
Source checked: 2026-10-01 - Synthesized SDK documentation
A separate Python SDK product exists; it should not be conflated with the TDK platform.
Source checked: 2026-10-01
What should you verify in a proof of concept?
- Your database version, schema constraints and target formats.
- The exact product, edition, deployment and license entitlements.
- Your business assertions and the meaning of repeatability for your output.
- A failed run, cleanup and a repeat run on controlled inputs.