For operations & migration teams
Clean your exports.
Keep every row in view.
One schema. A record of what changed.
A place for what needs a person.
Eight fictional rows. No account or file upload required.
Open the full workbenchWhat you get
Clean data, plus a record of every row.
$0 demo
Offline and API licenses are priced by quote
Try the free demoRequest a license quoteCompare licensed editions- Included
- The free CSV/Excel demo accepts up to 2 MB and 2,000 rows per file. Review the mapping, inspect clean / needs-review / set-aside rows, then download clean CSV and the complete audit bundle. No account or license needed.
- How payment works
- The offline edition and API need a Normalize license. Scope, row limits and payment terms are agreed before purchase. Licensed runs default to 100,000 rows, subject to the license; API requests allow up to 25 MB.
- Know the limits
- The demo uses server processing and fixed rules, without AI. Offline processing stays on your computer; activation and renewal go online. AI suggestions and document extraction require the applicable API entitlement. Human mapping review is still required.
Use the free demo first. Read the edition guide before requesting a license.
A messy export, reconciled.
Customers / Riverbend Mailing
Fictional sample data
The working eight-row sample. Inspect all three result buckets below.
Processed on our server without AI. Usage metadata is logged. Data handling and limits.
Every bucket is part of the result
Clean is useful.
Accounted for is better.
Three rows pass. Three need review. Two are set aside, including an exact duplicate and a summary row. Inspect why each landed there.
- Clean CSV
- The rows that meet the reviewed mapping and schema.
- Review & exceptions
- Original values, reasons, duplicate references and every non-clean row.
- Complete audit bundle
- Original bytes, source tables, mapping, transformations, hashes and all result buckets.
Review the mapping.
Resolve the exceptions.
Keep the receipt.
- 01
Inspect the sample
Run the eight-row customer export without uploading your own file.
- 02
Review the mapping
See which source columns feed each target field, then inspect clean and exception rows.
- 03
Export and resolve
Download the audit bundle. Correct exceptions in your source tool, record the reviewer and rerun validation.
Row accounting does not establish that every mapping is semantically correct. Review the destination fields and exception reasons before importing.
Choose where your files are processed.
The public one-file demo processes uploads on our server with fixed rules and no AI calls; it does not persist the file or result in application storage. Operational usage metadata is logged. Row accounting proves assignment, not that every mapping is semantically correct. Review the mapping and exceptions before importing into a destination system.
Processing, limits and API guideChoose a way to run it
Same accounting.
Different workflows.
The public demo needs no account or license: up to 2 MB and 2,000 rows per file. The offline edition and API require an active license. API limits depend on your license (default 100,000 rows per run). Contact Lattice for license pricing; no unverified price is shown here.
Start with one file.
Free demo: up to 2 MB and 2,000 rows. Server-processed, fixed rules, no AI calls.
Inspect the sampleKeep file processing local.
Active license required. Activation and renewal contact the server. Current installers are unsigned/ad-hoc signed.
Request a licenseSetup and grace periodsBuild it into the handoff.
Licensed server runs with a license-specific row cap. Authentication, schemas and error examples are documented.
Read the API guideWhat happens to the difficult rows?
Will data be dropped?
Every parsed source row is assigned to clean, needs review or set aside. Download the full audit bundle to keep all buckets, original file bytes, source tables and extra fields. Row conservation alone does not validate the meaning of a mapping.
What happens to uncertain values?
They remain visible with their original values and reasons in Needs a human. The demo does not silently guess a replacement. Correct the source externally, log who approved it and rerun.
Can I reuse mappings?
Yes. The audit bundle contains the mapping. Replay with identical source bytes, reviewed mapping and engine version is intended to produce the same output hash; changing those inputs can change the output.
Where are files processed?
The browser demo uploads files to Lattice’s server. The offline edition processes files on your computer; license activation and renewal contact the server. API requests are server-processed. See the data-handling notes for each edition.
What are the limits?
The demo accepts a 2 MB file and up to 2,000 rows. Licensed API runs have a license-specific cap, defaulting to 100,000 rows. Offline installers are currently unsigned/ad-hoc signed; subscription grace defaults to 7 days and managed-license grace to 14.