Deployment and data management
Validio provides two primary deployment options designed to offer complete flexibility over where your data is stored and processed. Both models allow you to select specific regions (GCP, AWS, or Azure) to ensure compliance with local data residency requirements. The following table compares the data management based on the deployment options:
For more information about Validio deployments, see Validio Managed Solution and Validio VPC Deployment. For more information about how Validio protects your data, see Security and Compliance.
How Validio handles data in push-down
For data warehouse and query engine sources, Validio uses query push-down: each check is compiled into a query that runs inside your warehouse, and only the computed result is returned. Validio does not copy your tables out, and for validators, Custom SQL validators, and data profiling, no raw rows are received or stored — Validio keeps only the resulting metric (for example, the value, the threshold bounds, and whether the check breached). The query travels to your warehouse over an encrypted connection when transport encryption is enabled on the connection; see Encryption in transit below. Validio’s datastore holds computed results, not source data. Two features intentionally store values derived from your data (listed here so you can decide which assets to use them on):- Data profiling stores a small, bounded set of statistics. Most are counts and percentages, but numeric minimum, maximum, median, and quartiles, and timestamp minimum and maximum are actual values present in the column. Text and boolean columns store no values. Assets too sensitive for even these boundary statistics need not be profiled. See Data Profiling.
- Segmentation stores the distinct values of any field you segment on, as grouping labels (for example,
region = Nordics). These are derived from your data, so segment on low-sensitivity fields. See About Segmentation.
- Data sampling returns real rows as a preview, held in memory for display only and discarded when you close or reload it. See Data Sampling.
- Debug generates a query that reproduces an incident and can load sample rows from the affected data. The query runs against your warehouse and the results are displayed for troubleshooting, but they are not retained. See Debugging an Incident.
- Filter preview shows sample rows that match a filter while you configure it, so you can confirm the filter behaves as intended. See About Filters.
- Custom SQL source preview shows sample rows returned by the query while you set up or edit a custom SQL source. See Custom SQL Sources.
- Custom SQL validator query testing shows the rows a validator query returns while you test it, so you can confirm it returns the expected single metric before saving. See Custom SQL Validators.
Encryption in transit
Connections to data warehouse and transactional database sources support authenticated TLS, validated against a certificate authority (CA) you supply. Transport encryption is configured per connection on the credential — for example, on the Oracle, SAP IQ, and Progress OpenEdge credentials. We recommend enabling TLS on every connection and supplying a CA certificate for validation. For an overview of Validio’s security controls, see Security and Compliance.Data retention policies
The level of data access and the applicable retention policies depend heavily on your setup:- Managed Solution: Validio manages the retention periods for the data types processed within the platform.
- VPC Deployment: Because Validio does not have access to your raw data or logs in a VPC environment, we do not provide a backup solution for your installation. Data retention in this model is opt-in only and applies exclusively if you choose to send performance metrics and error logs to Validio for troubleshooting and analysis.
1 For Validio VPC deployments, you can opt-out from sending performance metrics and error logs to Validio.