Know which data you can trust
Developers, analysts and data teams use DQaaS to profile datasets, check them against rules, score their quality and keep a governed catalogue, from a web console, a REST API, a CLI or an AI assistant.
Four ways to use it
CLI
A single native command-line program that profiles and checks files on your own machine with no server and nothing uploaded. It also works as a client for the hosted API.
dqaas run customers.csv -o report.htmlAPI
REST with a generated OpenAPI document: register sources, run jobs, manage rules and read the catalogue and reports.
GET /v1/datasets/{id}/report?format=mdMCP
Give an AI assistant the same access: a local MCP server that can also profile a file on your machine, and a hosted MCP endpoint that uses your access token.
POST /mcp (Authorization: Bearer dqat_...)In the browser
Attach a file and profile it on your own device. Nothing is uploaded.
Open Attach locally in the console
All four share the same checks and report format. Browser results are computed on the device.
How it works
Connect or upload
Upload a file or register a URL or table in a project.
Profile and check
DQaaS profiles every column, suggests rules, runs them and scores the dataset.
Catalogue and report
Add owners, descriptions and classifications, track lineage and export a report.
CLI
export DQAAS_URL=https://your-dqaas-host
dqaas login --token dqat_...
dqaas upload orders.csv --project PROJECT_ID --wait
dqaas analyze DATASET_ID --wait
dqaas rules DATASET_ID --suggest
dqaas report DATASET_ID --format html -o report.htmlREST API
POST /v1/datasets/upload
POST /v1/datasets/{id}/analyze
GET /v1/datasets/{id}/rules/suggestions
GET /v1/datasets/{id}/report?format=md
GET /v1/catalogue/search?q=customer
Authorization: Bearer dqat_...Capabilities
Ingest files and sources
IncludedStart from what you already have.
Upload CSV, TSV, JSON, JSONL, Parquet, Avro, Arrow, XLSX or embedded database files, or register an HTTPS URL or a read-only Postgres table. The format is detected from content and name.
Profiling
IncludedSee what is really in a column.
Types, null and distinct counts, value statistics, placeholder detection, and schema and statistical drift between profiles.
Quality rules and scoring
IncludedOne score per dataset, with the failing rows counted.
Suggested rules from the profile, rule packs and your own checks. Each rule reports failed over total rows; scores are weighted by severity and grouped by quality dimension.
Sensitive-column detection
IncludedFind likely personal data early.
Name and pattern heuristics flag columns such as email, phone or date of birth. Findings are labelled inferred, and sensitive sample values are redacted.
Profile on your own device
IncludedCheck a file without sending it anywhere.
Attach a CSV, TSV, JSON, JSONL or Parquet file and profile it on your own device; the file never leaves it. Optionally publish only the profile and rule results to the catalogue. Browser results are computed locally and are not verified by the server.
Catalogue and governance
IncludedEveryone finds the right table and who owns it.
Full-text search, glossary, column descriptions and classifications, policies and violations, stewardship tasks and coverage indicators.
Lineage and impact analysis
IncludedKnow what breaks downstream.
Lineage edges are inferred or verified (verified requires evidence). Impact analysis runs upstream or downstream, optionally on verified edges only.
Reports
IncludedShare results with people who never log in.
Dataset and project reports as JSON, Markdown, HTML or PDF.
REST API, OpenAPI, CLI and MCP
IncludedFit it into pipelines and assistants.
A bearer-token REST API with a generated OpenAPI 3.1 document, a command-line client, and an MCP server with 16 tools.
Roles, tokens and audit log
IncludedControl and trace access.
Viewer, editor, admin and owner roles, scoped and revocable access tokens, and a hash-chained audit log with a verify endpoint.
Quotas and usage metering
IncludedSee what you use.
Monthly quotas with usage shown in the console and API.
Interval schedules
IncludedRe-check data on a rhythm.
Recurring jobs on a fixed interval from 5 minutes to 1 year.
Who it is for
Developers and data engineers
Add checks to pipelines through the CLI or REST API.
Analysts
See which tables are trustworthy before building on them.
Data teams and stewards
Track ownership, classification and open stewardship tasks.
AI-assistant users
Query quality and catalogue data through MCP.
Data handling principles
- Source rows are transient: they are processed for the job and deleted at its end. Uploads are kept only if you ask.
- Metadata is persisted: profiles, rule results, scores, catalogue entries and an audit log.
- Sensitive values are redacted: sensitive columns store no top values, no min/max and no failing examples.
- Strict privacy mode stores no sample values at all.
- Remote sources are checked against SSRF: only HTTPS, no embedded credentials, and hosts resolving to private or loopback addresses are blocked on every redirect.
- Findings are labelled inferred or verified. Sensitive-column detection and relationships are inferred; lineage is verified only with evidence.
- No accuracy claim without reference data: DQaaS reports completeness, validity, uniqueness and similar checks, not accuracy.
- In-browser mode: files are profiled on your own device and never leave it.
See the security page for controls and their limits.
Pricing
Free during launch. All accounts are free, with these limits per month:
- 1 GB of data scanned
- 10 minutes of compute
- 2 scheduled jobs
- 50 MB of stored metadata
Pricing will be announced before any charge.
Roadmap
- Roadmap
Payment processor integration
- Roadmap
Single sign-on beyond GitHub
- Roadmap
Cron-expression schedules
- Roadmap
Column-level lineage extraction from SQL
- Roadmap
OpenLineage and ODCS import and export
Frequently asked questions
Does DQaaS store my data?
Not your rows, unless you ask. On upload, source rows are processed for the job and deleted when it ends; an upload is kept only if you choose to retain it. Metadata is persisted: profiles, rule results, scores, catalogue entries and audit records. Sensitive values are redacted, and strict privacy mode stores no sample values at all.
Can I check a file without uploading it?
Yes. Attach a CSV, TSV, JSON, JSONL or Parquet file and it is profiled on your own device; the file never leaves it. Those results are computed locally and are not verified by the server. You can publish just the profile and rule results to the catalogue.
Which formats are supported?
Upload: CSV, TSV, JSON, JSONL, Parquet, Avro, Arrow, XLSX and embedded database files, plus HTTPS URLs and read-only Postgres tables. On your own device: CSV, TSV, JSON, JSONL and Parquet.
How is quality scored?
Each rule counts failed rows against total rows, giving a score from 0 to 1 that passes at its threshold. Rule scores are weighted by severity and grouped by quality dimension into an overall dataset score.
Is accuracy measured?
No. Accuracy needs trusted reference data, which DQaaS does not have. It reports completeness, validity, uniqueness and similar checks, and makes no accuracy claim without reference data.
How reliable is sensitive-data detection?
It is heuristic, based on column names and value patterns, so it can miss or misflag columns. Findings are labelled inferred. Use strict privacy mode if a miss is unacceptable.
What does it cost?
Nothing during launch. All accounts are free with monthly limits (1 GB scanned, 10 minutes of compute, 2 scheduled jobs, 50 MB of stored metadata). Pricing will be announced before any charge.
How do I sign in?
Sign in with GitHub on the sign-in page. Access can also be by an access token for automation.
How do I connect an AI assistant?
The CLI includes an MCP server exposing 16 tools such as dataset listing, profiling, rule suggestion, reports and impact analysis.
Is DQaaS certified or compliant with a standard?
No certification or compliance attestation is claimed. See the security page for the controls that exist and their limits.