Paridity User Guide

What Paridity is

Paridity proves that data arriving in your analytical systems is complete and correct after replication — and produces the evidence an auditor can check independently.

It is not a data-quality tool and not an observability monitor. Those tell you about the data you have. Paridity answers a narrower, harder question: does the target match the source, right now, for a window both sides have finished delivering?

Three properties make that answer trustworthy:

1. It compares a deterministically aligned window. Most tools compare tables and then explain away the differences caused by replication still being in flight. Paridity uses the replication tool's own state to decide when a time window is safe to compare, and defers if it isn't. That is the difference between a real failure and a false alarm.
2. It proves equality before it explains inequality. A single aggregate fingerprint per side (hash_total) is a fast pass/fail. Only when that fails does the platform spend money identifying which rows differ, and then which columns within them.
3. It records immutable evidence. Every run pins the exact configuration it ran under, timestamps every phase, and writes append-only evidence. The comparison timestamp is never rewritten, even across retries.

If you are evaluating Paridity

Read in this order:

1. Getting started — from an empty tenant to a first successful reconciliation. Start here; it takes about 20 minutes and makes everything else concrete.
2. Glossary — the eight terms that carry the whole product. hash_total vs row_hash vs field_diff is the one distinction worth learning before anything else.
3. Configuration reference — every setting, which of the seven layers it lives at, how conflicts resolve, and whether you set it in the UI, the API, or at deployment.
4. The feature guide for whatever you are assessing.

A note on honesty. These guides mark each option with how you can reach it — UI, API, Ops (set at deployment), or Derived. Where the product does not yet have a control, the guide says so instead of implying a screen that does not exist. If you find a guide claiming something the application does not do, that is a bug in the guide and we want to hear about it.

The application, section by section

The left sidebar groups screens by what you are trying to do.

Monitor — is my data correct right now?

Screen	Path	What it answers
Dashboard	/	Overall reconciliation health across everything you own.
Mapping Performance	/observability	Throughput, duration and transfer-volume trends per mapping.
Runs	/runs	What executed, what it concluded, and why.
Anomalies	/anomalies	Statistical deviations the analyzers raised, tenant-wide; acknowledge and resolve.
Evidence	/evidence	The proof behind a conclusion — mismatched keys and field-level differences.
Recommendations	/recommendations	Suggested configuration and coverage improvements.

Setup — get started quickly

Screen	Path	What it does
Onboarding Wizard	/onboarding	Discovers tables, matches source to target, proposes mappings, and creates them after you confirm. The fastest path from nothing to a first run.

Configure — define what gets compared

Screen	Path	Guide
Systems	/systems	Systems and connections
Replication Profiles	/replication-profiles	Replication profiles
Mappings	/mappings	Mappings and Field configuration
Mapping Groups	/mapping-groups	Grouping for bulk operations.
Schedules	/schedules	Schedules and close mode
Notifications	/notifications	Where alerts go.

Governance — who did what, and under what authority

Screen	Path	Guide
Audit Log	/audit	Access, roles and audit
Elevations	/elevations	Break-glass requests and approvals.

Administration

Screen	Path	Notes
Users & Access	/administration/users	Access, roles and audit
Business Domains	/administration/business-domains	Organisational grouping for mappings.
Security Posture	/administration/posture	Access, roles and audit - every unsafe or unverified deployment setting, evaluated on any environment. platform_admin / tenant_admin.
Reconciliation Consumption	/administration/cost-usage	Reconciliation Consumption — provider units per run, mapping, system and period; no currency anywhere. platform_admin / tenant_admin.
Authentication	/settings/authentication	Identity provider configuration. platform_admin / tenant_admin; an OIDC provider's issuer, client secret reference and JWKS base URL are platform_admin only.
Subscription	/settings/subscription	Entitlements and tier.
Platform Defaults	/settings/platform	platform_admin only. See the configuration reference for what is settable here versus at deployment.
AI Settings	/settings/ai	platform_admin only.
Legal Holds	/settings/legal-holds	Freeze a tenant, mapping or bundle against the retention purge. Approval-gated and audited. See Evidence.
Retention Schedule	/settings/retention	The built-in retention purge: cadence, dry-run window, paused state, last fire — and where an admin pauses or resumes it.

Screens are role-gated: if a colleague cannot see something described here, the most likely reason is their role, not a missing feature. See Access, roles and audit.

Guides

Guide	Read it when you want to…
Getting started	Reach a first successful reconciliation.
Configuration reference	Understand any setting, its layer, and its resolution rule.
Systems and connections	Register a source or target and understand credential handling.
ClickHouse	Provision a ClickHouse read user, know the supported versions, and choose a read mode for ReplacingMergeTree and ClickPipes tables.
Replication profiles	Tell Paridity which replication tool moves your data, so readiness works.
Mappings	Define what is compared to what, and the run-level policy.
Field configuration	Control comparison semantics per column.
Key identity contract (exact-v1)	Know exactly when a source row and a target row are the same entity, and which engines have proven it live.
Watermarks and windows	Choose how incremental windows are bounded.
Lakehouse tables - Iceberg-aware reads	Reconcile Iceberg or Delta tables at a pinned commit through Trino, Databricks or Snowflake.
Delta Lake outside Databricks	Read a Delta table through Trino, Snowflake Delta Direct or the engine-less file dataset reader, and know each reader's pin and limits.
Schedules and close mode	Control when runs happen, including quarter-end.
Runs	Interpret a run's status and act on a failure.
Troubleshooting	Work back from a symptom - a held run, a refusal, a stale worker, a sign-out - to its cause, what to check, and when to report it.
Anomalies	Triage the deviations the analyzers raised; acknowledge and resolve.
Evidence	Read the proof, and export it for an auditor.
Access, roles and audit	Understand roles, grants, break-glass and the audit trail.
Report a problem	Send support a privacy-safe Diagnostic Bundle with your email, and know what it does and never contains.
Error codes	Every error code the API returns, with its HTTP status, message and what to do - generated from the code.
Known limitations	An index of the documented limitations, each linked to the guide section that describes it.
Glossary	Look up a term.
Float column handling	Handle floating-point columns correctly.
Repair posture	Answer "now fix it" — why Paridity generates remediation but never executes it, and where the evidence stops.