MariaDB Anonymization - Compatible 10.5 to 11.x
Anonyx connects to your production MariaDB servers and produces anonymized copies for dev, test and analytics environments. The connector handles MariaDB-specific capabilities (sequences, system versioning, invisible columns, Aria and ColumnStore engines) while preserving InnoDB referential integrity.
- MariaDB 10.5, 10.6 LTS, 10.11 LTS and 11.x officially supported
- Automatic detection of MariaDB-specific features (Aria, ColumnStore, sequences)
- System-versioned tables: current versions anonymized, historic at your choice
- Galera Cluster: consistent reads, target writes adapted to quorum
- 80+ PII transformations for French, EU and international datasets
- EU sovereign hosting, GDPR compliance built-in
MariaDB-specific features supported
MariaDB increasingly diverges from MySQL on certain features. Anonyx detects the variant at startup (SELECT VERSION()) and adapts its behavior: JSON_VALUE / JSON_QUERY instead of MySQL JSON functions, support for sequences (CREATE SEQUENCE), invisible columns (INVISIBLE) and strict CHECK constraints.
The Aria engine (an improved MyISAM clone) is supported for reads, with the same referential integrity caveats as MyISAM. For ColumnStore tables (the analytical columnar engine), Anonyx favors wide batch reads to leverage the columnar nature.
System versioning and historized tables
MariaDB 10.3+ provides native system versioning that maintains historic versions of every row in an invisible temporal partition. Anonyx detects these tables (information_schema.TABLES.SYSTEM_VERSIONED = 'YES') and exposes a per-rule option: anonymize only the current version (default, fastest), anonymize all versions (audit use case), or extract only the current version while disabling versioning on the target.
Galera Cluster and high availability
For MariaDB deployments on Galera Cluster, Anonyx connects to a healthy node and reads in strict consistency (wsrep_sync_wait = 7). When writing to a Galera target, insertion pace is adapted to avoid saturating the replication quorum - especially useful on geographically distributed three-node clusters.
For architectures with a proxy (MaxScale, ProxySQL), you can point Anonyx directly at a specific node for massive reads (avoids penalizing application traffic) while still using the proxy for target writes.
Performance, observability, operations
On an 80 GB MariaDB database with a typical e-commerce schema, full anonymization takes about 25 to 35 minutes with four workers. Incremental mode, based on tracking columns or on native system versioning, lets you refresh a target database daily in just a few minutes once the first full pass is complete.
All runs are audited and expose Prometheus-format metrics. Job-completion webhooks let you automatically trigger integration test suites or downstream environment refreshes.