Dev, QA, UAT, Staging.
All fresh. All safe.
Non-production databases go stale in days. Manual reconfiguration is error-prone. PII ends up where it shouldn't. DataTamed standardises environment provisioning across your entire non-prod estate.
Three ways non-prod environments
become a liability.
Dev, QA, UAT, and staging each have their own quirks — but they all share the same underlying problems.
Stale Data, Stale Tests
Non-production databases go stale within days of provisioning. Your QA team is testing against data from three months ago. Your staging environment doesn't have the new customer segments that broke production last week. Bugs slip through.
Manual Reconfiguration After Every Restore
Each environment needs different connection strings, email settings, payment endpoints, and feature flags. After every restore, someone has to find the configuration runbook — if it exists — and run through it manually. Steps get skipped. Environments diverge.
PII Across Every Environment
Production data copied to dev, then QA, then UAT, then staging. Each hop is another opportunity for real customer data to be accessed by people who shouldn't see it, or to end up in a log file, a test report, or a support ticket.
One platform for the full
non-prod environment pipeline.
DataTamed gives you a single, repeatable provisioning workflow from production backup all the way through to staging — with PII safety and environment config handled automatically at every step.
One Image, Many Environments
Import a production backup once — DataTamed masks the PII and creates a reusable database image. That single masked image is the source for clones across dev, QA, UAT, and staging. Refresh the image when you want fresh data.
Per-Environment SQL Script Sets
Create a separate SQL Script Set for each environment type. Dev gets one set of connection strings and feature flags; QA gets another; staging gets production-equivalent config with test payment providers. Attach each set to clones as needed — zero manual steps.
PII Safe Across the Entire Estate
Personal data is masked at the image level — before storage, before any clone. Every environment that uses the image gets clean data. You don't need separate scrubbing scripts per environment or per team.
Agents Deployed Where You Need Them
Deploy DataTamed agents alongside SQL Server wherever your environments live — dev workstations, a QA lab, a cloud-based UAT server, or an on-prem staging rack. One central server coordinates provisioning across all of them.
Version Compatibility Across Environments
Your dev SQL Server might be 2022 and your UAT server 2019. The Clone Wizard validates compatibility before each clone and warns you if a backup version won't restore to the target. No more failed clones discovered at the wrong moment.
Full Visibility Across All Environments
The Database Management dashboard shows every active image, every live clone, and every agent. The Backup History Report records every provisioning event. Know exactly what's running where, and when it was last refreshed, from one screen.
What DataTamed does for each
environment in your pipeline.
Each environment has different needs — DataTamed handles them all from the same platform and the same database image.
Fresh data, fast iteration
Developers need a database that reflects production structure without containing real customer data. DataTamed provides a fresh, masked clone in seconds — typically just 60–70 MB, not a days-old backup with manually removed columns.
Production-realistic test data
QA teams need data that exercises real edge cases — the kind of data only production generates. Cloning from a recent production backup (with PII masked) gives QA a realistic dataset without compliance risk.
Business-representative scenarios
UAT needs data that stakeholders and business users can recognise — realistic in structure, shape, and volume, but not containing real personal data. A masked production clone, configured with a UAT script set, is exactly that.
Production parity, safely
Staging should match production as closely as possible — same data volume, same schema, same structure — but with masked PII and test payment/email providers. SQL Script Sets swap those endpoints automatically post-clone.
One image. Four environments.
Zero manual steps.
Create a SQL Script Set for each environment type and attach them to clones. DataTamed runs them automatically after every clone — consistent, documented, and zero-touch.
Connection Strings
Point each clone at the right endpoints — internal APIs, message queues, storage accounts — for its target environment.
Email & Integration Overrides
Disable outbound email, redirect to test inboxes, or swap real payment providers for test equivalents — specific to each environment.
Reference Data & Feature Flags
Insert environment-specific lookup values, test accounts, and feature flag overrides that are required for that environment to function correctly.
Script Set per Environment
| Environment | Payments | API Base | |
|---|---|---|---|
| Dev | Disabled | Mock | localhost |
| QA | Test inbox | Sandbox | qa.internal |
| UAT | Test inbox | Sandbox | uat.internal |
| Staging | Test inbox | Test provider | staging.internal |
Each row is a separate SQL Script Set attached to clones for that environment. The same masked database image underpins all four — refreshed from production whenever you need fresh data.
One workflow for every
environment in your pipeline.
Set it up once for each environment type. Repeat on demand.
Import & Mask
Import a production .bak file. DataTamed masks PII across all six categories automatically during import. The masked image is stored and ready to clone into any environment.
Create Script Sets
Write one SQL Script Set per environment: Dev, QA, UAT, Staging. Each handles the connection strings, email redirects, feature flags, and seed data specific to that environment.
Clone as Needed
Use the Clone Wizard to create an environment-specific clone: pick the masked image, the target server, and the matching script set. DataTamed provisions and configures the clone in seconds — clones are typically just 60–70 MB.
Refresh on Demand
When data goes stale, re-import from a new production backup and re-run the masking. The new image replaces the old one. All subsequent clones use the freshened data automatically.
Everything needed to manage
a multi-environment SQL Server estate.
All features are included in every plan — no upgrades needed to unlock the non-prod provisioning workflow.
Database Import
Turn any .bak file into a reusable, masked database image. The masked image is the single source of truth for all clones — refresh it at any time without disrupting active clones.
SQL Script Sets
Named collections of SQL that run automatically after every clone. Create one per environment type and attach them at clone time. No runbooks. No manual steps. No configuration drift.
Clone Wizard
A four-step guided flow: select image, select agent and server, configure clone name and script set. SQL Server version compatibility is validated before anything runs.
Automatic PII Masking
Six PII categories detected and masked at import time. Every clone across every environment inherits the masking — no need to re-run scrubbing per environment or per team.
Database Management
Mount, unmount, lock, and track all database images and active clones from one dashboard. See every environment, every agent, every active database at a glance.
Agent Management
Deploy agents wherever your environments live. Each agent connects back to the central DataTamed server over HTTPS. Heartbeat monitoring alerts you if any agent goes offline.
Standardise your
environment provisioning.
Start a 14-day free trial — no credit card required. A member of our team will be in touch within one business day to help you get started.
- 14-day free trial, all features included
- Agent installed in under 10 minutes
- First cross-environment clone in seconds — typically just 60–70 MB
- Works with your existing .bak backup files