Paridity Documentation¶
Paridity proves that data arriving in your analytical systems is complete and correct after replication — and produces evidence an auditor can check independently.
This site is the rendered form of the customer-facing documentation set. Every page here is generated from the same Markdown the engineering team maintains, so it cannot drift from the source it was written against.
Start here¶
| If you want to… | Go to |
|---|---|
| Reach a first successful reconciliation | Getting started |
| Understand what the product does | Capability overview |
| Look up a term | Glossary |
| Find a specific setting | Configuration reference |
The four sections¶
User guide — how to operate the platform, screen by screen: systems, replication profiles, mappings, field configuration, watermarks, schedules, runs and evidence.
Proof & credibility — how the platform's central claims are substantiated, and how to check them yourself rather than take them on trust: accuracy, performance, audit & compliance, architecture, how we compare, and a proof-of-value guide.
Deployment — what gets deployed into your cloud account, what your team owns versus what Paridity owns, and the prerequisites to collect before implementation begins.
Security & trust — the security whitepaper, data-flow descriptions, continuity posture, open-source bill of materials, and standing answers to vendor-risk questionnaires.
A note on honesty. These documents mark each capability with how you can reach it — UI, API, Ops (set at deployment), or Derived — and say plainly where the product does not yet have a control rather than implying a screen that does not exist. If you find a page claiming something the application does not do, that is a bug in the page and we want to hear about it.