// the take
Qualitis is a Java/Spring Boot data quality platform built by WeBank that runs validation rules (single-table, multi-table, or custom) against datasources by submitting jobs to Linkis. It's aimed at large organizations already running the WeBank/Linkis/DataSphereStudio stack who need data quality checks with enterprise access control and audit trails, not standalone teams looking for a lightweight checker.
Preset templates for the common checks (null, blank, number range, enum) mean you're not writing boilerplate rule logic for every table. It delegates actual execution to Linkis rather than reimplementing engine support, so it inherits Spark/Hive execution instead of maintaining its own runners. Abnormal-data storage is built in, so a failed check gives you the offending rows directly instead of just a pass/fail flag. Access control and resource isolation are treated as first-class features, which matters if multiple teams share one instance.
It's not really a standalone tool - adopting it means also running Linkis (and DataSphereStudio if you want workflow support), which is a lot of infrastructure to take on just for data quality checks. Documentation is clearly Chinese-first; the English docs read as translations and community support is via WeChat/QQ group, which will be a real barrier for teams outside that ecosystem. The roadmap still lists cross-storage verification (Kafka, HDFS-to-MySQL) and 'intelligent discovery of data quality problems' as future work, so if your checks span multiple storage types today, this doesn't cover you yet. It's effectively a single-vendor project (WeBank) with no visible outside contributor base, so longevity depends entirely on WeBank's continued investment.
We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →