Match people across CRM lists and imports, clean messy addresses, resolve them to real places, and return locality-aware details your data workflows can trust.
Use Splink to compare primary CRM records with imports, API records, or CRM-supplied candidate blocks.
Parse free text or structured fields into consistent address components for downstream systems.
Resolve addresses to OpenStreetMap features with coordinates, OSM IDs, locality details, and postcode checks.
Linksync can hold matching records in the cloud when you want managed batch processing, but it also supports runtime matching where your system sends candidate blocks only when a match is requested.
Upload person and address files, train matching behavior, run matching jobs, and download results. When the job is done, users can remove source data, results, and matching inputs while retaining only training insight.
If you do not want PII persisted, your CRM can send candidate records and block ids at runtime. These are matching cohorts, such as records grouped by postcode or last-name initial. Linksync scores those candidates without needing to store the underlying person file.
Uploaded files and generated outputs are stored in AWS S3-backed object storage, isolated by account paths and encrypted at rest by S3 server-side encryption.
The web application handles authentication and workflow control, while background workers process address and matching jobs separately from the public request path.
Paste any US address. Linksync will parse it, normalize the components, and attempt a building match when possible.
The normalized JSON response appears here after you run the demo.