Overview
Protect sensitive data for development, testing, analytics and AI/ML ops without compromising on data quality and innovation with DataMasque. Automatically discover and mask sensitive data - including PII, PHI and PCI - to generate privacy compliant, realistic and irreversible synthetically identical data. No matter where your data lives - in databases, files, the cloud, on-prem or across environments - DataMasque ensures it is masked consistently. DataMasque supports masking of primary and unique keys and automatically maintains referential integrity of foreign keys.
Highlights
- Drives consistency across tables, databases, and database engines, whether in the cloud or on-premises, regardless of the environment.
- Cryptographically secure SHA-512 salted hash to drive irreversibility.
- Optimised for self-service automation - integrates seamlessly into existing IT management services.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
Dimension | Description | Cost/12 months |
|---|---|---|
enterprise_lic | DataMasque Enterprise License | $132,000.00 |
business_lic | DataMasque Business License | $96,000.00 |
enterprise_sup | DataMasque Enterprise License + Enhanced Support | $168,000.00 |
business_sup | DataMasque Business License + Enhanced Support | $132,000.00 |
enterprise_add | DataMasque Enterprise License - Additional Deployment | $132,000.00 |
business_add | DataMasque Business License - Additional Deployment | $96,000.00 |
prof_service | DataMasque Professional Service– Prepaid Hours ($250/hour) | $250.00 |
Vendor refund policy
Refunds and cancellations are not available.
Custom pricing options
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Major Update: Subsetting
DataMasque now supports subsetting, retaining a specified percentage of production data for dev and test environments to reduce data volume for cheaper, faster early-stage testing. PostgreSQL, Oracle, and MS SQL Server are supported, with foreign key relationships preserved.
Locality Interpolation in Rulesets
Locality settings (such as country code) can now be used as variables inside rulesets, making rulesets portable across regions and automatically applied at run time.
Toggle ID Columns in Ruleset Generator
A new checkbox controls whether ID columns appear in the ruleset generator, making it easier to identify sensitive fields and generate more accurate rulesets.
Faster Ruleset Loading and Search
Ruleset lists load faster, and search now works inside ruleset content. Advanced API queries support additional filters such as created date and validation status.
Custom sentinel_years in retain_age Mask
Custom sentinel years other than 0 and 9999 can now be defined, ensuring domain-specific date values remain unmasked.
Backwards Join Detection
DataMasque now detects likely reversed join directions in mask_table tasks, reducing configuration errors.
Malaysian Seed Files
New Malaysian seed files are available for names, addresses, companies, and banks.
More Precise Ruleset Validation
Improved validation now flags subtle syntax issues earlier and provides clear guidance in the editor.
Additional details
Usage instructions
Please follow the steps below to complete setting up your DataMasque instance:
-
Access the application via a web browser at https://<instance-ip-or-hostname>. The application may take a few minutes to start. Please refresh the page if you encounter the "Unexpected Error" message.
-
Complete the first-time installation page by providing the following information:
-
Email address of the DataMasque admin user. This email address is stored on the DataMasque EC2 instance and is used for the purposes of providing 'Forgotten Password' account recovery and critical system notifications. DataMasque will not have access to this information.
-
Password for the admin user.
-
Hostnames or IP addresses to access the DataMasque instance.
-
The SMTP settings specific to your organisation.
-
The instance ID of your EC2 instance.
- You will be re-directed to the DataMasque login screen. Please proceed to login with the admin password you have just configured.
Note:
- When you use our software we may receive and store usage data and information relating to the performance and use of the Software. We will not disclose any system information which identifies the user or the user environment to third parties.
- To upgrade your DataMasque version, contact the DataMasque team via https://datamasque.com/contact/?source=support_ticket or support@datamasque.com to request your access to the DataMasque Customer Portal and download the new DataMasque software version.
Support
Vendor support
DataMasque provides full product and installation support within 72 hours of making an enquiry. Contact the support team at support@datamasque.com for any enquiries you may have.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.

Standard contract
Customer reviews
Masking sensitive test data has improved compliance and now enables safe, realistic debugging
What is our primary use case?
My main use case for DataMasque is masking PHI data to use in a staging environment for production testing.
I decided to start masking PHI data specifically for staging due to a compliance requirement and to have better end-to-end testing with real production loads.
What is most valuable?
The best features DataMasque offers that stand out to me are the flexibility to create rule sets and mask UUIDs, which have been really beneficial. Additionally, their customer service and technical support have been very helpful in getting this set up.
The flexibility in creating rule sets has helped my team specifically because we have lots of dependencies on different databases and different database types. We have an RDS instance and an OpenSearch instance. Having those rule sets really allowed us to connect data between the two because the same data can be across multiple datasets. Creating these rules enabled us to not think too much about which ones need to be unique or which ones need to be the same across different tables. Whenever we run into issues or questions, we are able to talk to the DataMasque team, and they give us a reasonable technical response within a good timeframe that allows us to solve our issues pretty quickly. We have not had huge delays or blockers because of the communication between us and DataMasque.
I appreciate the consistency to continue to improve the application, and there are new features coming out this year that will be tools we use. DataMasque is doing a great job of adding new features, and we will definitely be using them in the future.
DataMasque has positively impacted our organization by already showing visible benefits in security and reduced risks for compliance, even though we are still in the process of setting up production and using it to the full extent. It will allow our developers to troubleshoot issues easily without the risk of viewing PHI or anything similar. We are seeing the benefits already of that, but we still need to complete the full integration and incorporate it into our workflows to see the full benefits, which we are currently in the process of. So far, it has been really good.
By just masking production data, we can go into this masked database set to understand edge cases and issues as they come up from support without the developers having to look at any production data. They can go into this masked dataset and see the problem firsthand, something we would not have caught with our dev dataset because it is such a smaller amount of data, whereas production has a vast amount of data that we can look through.
What needs improvement?
It is too early to tell how DataMasque can be improved since we are still in the implementation phase. We do like everything that the company offers, and they perform check-ins monthly to see if we have any issues. Right now there is not anything we would like to improve.
For how long have I used the solution?
I have been using DataMasque for about eight months.
What do I think about the stability of the solution?
DataMasque is stable.
What do I think about the scalability of the solution?
DataMasque's scalability is pretty good; we have not had any issues, and we have a pretty large dataset that it has handled well.
How are customer service and support?
Customer support from DataMasque is excellent.
Which solution did I use previously and why did I switch?
I did not previously use a different solution.
How was the initial setup?
It was quite easy to deploy DataMasque in my environment.
My experience with the configuration process was good; it was a smooth process with no issues.
What was our ROI?
We have not seen a return on investment yet, but we expect to save money on testing.
What's my experience with pricing, setup cost, and licensing?
My experience with the procurement process was easy.
My experience with pricing, setup cost, and licensing was easy. They gave us a trial license that we used, and when it expired, they extended it for us so we could finish our implementation and testing. The contracting was done with our CTO, and he signed off on it, so that part seemed to be a smooth transaction because everything was done through AWS , with no issues at all.
Which other solutions did I evaluate?
I did not evaluate other options before choosing DataMasque, as we had a referral to DataMasque.
What other advice do I have?
I suggest trying DataMasque out and seeing how it fits your needs. Ask questions because DataMasque is great at responding to questions and making sure it fits your requirements. I give DataMasque a rating of five out of five.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Creating realistic staging data has improved testing quality and supports flexible masking rules
What is our primary use case?
I created a staging environment with production-like data.
How has it helped my organization?
We can now have a staging environment very much like a production environment, which improves our testing and product quality.
What is most valuable?
The auto-generation of masking rules, integration with Git , support for supplementary masking files, the ability to run raw SQL, and partition support all make it easier to create and maintain a masking configuration. Additionally, worker settings are needed as they help improve performance.
What needs improvement?
UUID generation could be improved. Although UUIDs were masked correctly, some validation rules were not supported, requiring a switch from validators to pattern matching. Expanding native UUID validation support would be beneficial.
For how long have I used the solution?
I have used the solution for about 3-4 months.
Which solution did I use previously and why did I switch?
This is my first time using a masking tool.
What's my experience with pricing, setup cost, and licensing?
As we are still in the early stages, I can't say anything definitive about pricing yet, but I believe it will be usage-based, which should work well.
What other advice do I have?
Thank you for the product and the great support throughout this journey. The team has been responsive and helpful, and it has been a positive experience overall.
Data masking has improved QA testing coverage and protects all discovered sensitive fields
What is our primary use case?
How has it helped my organization?
The testing scenarios are more complete.
What is most valuable?
Being able to generate the masking rules directly from the tool based on what it finds during the data discovery helps ensure that all sensitive fields are identified and masked.
For how long have I used the solution?
I have used the solution for one year.
Which solution did I use previously and why did I switch?
This is the first time I am using this tool.
What's my experience with pricing, setup cost, and licensing?
The DM team was very happy to work with us when we were determining the pricing and licensing model we wanted to use.
What other advice do I have?
The tech support is top notch!
Data masking has protected sensitive test data and enables accurate, large-scale QA testing
What is our primary use case?
My main use case for DataMasque is cleaning personal, personally identifiable information out of a production environment to use in our test and QA environments.
A quick, specific example of how I use DataMasque in those environments is that we take production data, we clean it and mask it, and we give it to our developers and our UI.
The whole idea of DataMasque allows me to do exactly what I just explained.
What is most valuable?
The best features that DataMasque offers are the speed and accuracy, which are by far the best of any of the masking products.
The speed and accuracy help my team because, since it's our test, our UI and test boxes, we don't want to introduce data errors and bugs or have any data leakage, so it's incredibly important to have accuracy. Speed is key because we have terabytes worth of data to process. If it was slower, it would take probably a week to be able to process and mask the whole thing, which is incredibly helpful.
DataMasque has positively impacted our organization by absolutely allowing us to more rigorously test our products within a safe environment without leaking personally identifiable information.
What needs improvement?
I think it would be great if the user experience was upgraded because it can be quite technical at times.
The user interface could benefit from an upgrade as it can be quite technical at times. I do not have a specific example of where it felt too technical or where the user experience could be smoother.
For how long have I used the solution?
I have been using DataMasque for the last couple of years.
What other advice do I have?
There are no improvements needed for DataMasque that we haven't already discussed.
My advice to others looking into using DataMasque is that it's an extremely good product that's getting better all the time.
My company does not have a business relationship with this vendor other than being a customer. I would rate this product an 8 out of 10.