Address Tokenizer Core vs. Pro: A Decision Guide
Core is free and open source under Apache 2.0. Pro is a commercial upgrade for harder country coverage and deeper review tooling. Here is a straightforward way to decide which one fits your project today.
Core and Pro are not "free trial" versus "real product." Core is a fully usable, production-ready Apache 2.0 library on its own. Pro is an additive commercial package for teams that hit a specific coverage, confidence, or support requirement Core does not address. The decision usually comes down to a small number of concrete questions rather than a general "which is better" comparison.
Decision snapshot
Choose Core if
Your target countries are Australia, Canada (including Quebec/French), France, Germany, the UK, or the US, and an overall confidence score is enough for your review process.
Choose Pro if
You need Brazil, Hong Kong, Japan, or Singapore coverage, field-level confidence, trace logs, data healing, or ISO 20022-oriented field mapping.
Many teams reasonably start with Core to evaluate the parsing approach on their own data, then move to Pro once a specific gap becomes clear.
When Core is enough
- Your address volume is concentrated in Core-covered countries. Australia, Canada (English and Quebec/French), France, Germany, the UK, and the US have dedicated Core parsers; other countries fall back to the universal parser.
- An overall confidence score fits your review process. If your workflow just needs to know "is this address probably fine or does it need a look," Core's overall confidence is designed for that.
- You are evaluating the approach before committing budget. Because Core is Apache 2.0 and free for production use, it is a reasonable way to test parsing quality against your own data before any commercial conversation.
- You do not currently need ISO 20022-oriented field mapping, data healing, or trace logs. These are Pro-only capabilities.
When Pro makes sense
- You need Brazil, Hong Kong, Japan, or Singapore coverage. These are Pro-tier dedicated parsers layered on top of everything in Core.
- You need field-level confidence, not just an overall score. Review teams that want to know exactly which field is uncertain — not just that the address overall is uncertain — need Pro's field-level confidence output.
- You need explainability for audit or enterprise review. Pro's trace logs record how a parsing decision was reached (country detection, fallback behavior, enrichment steps), which regulated environments often require.
- You are preparing address data for ISO 20022 messaging. Pro maps parsed results toward ISO 20022-oriented fields such as
strtNm,bldgNb,pstCd,twnNm, andctry. - Your input data is incomplete or inconsistent enough to benefit from data healing. Pro's curated reference-data enrichment can repair and normalize records that Core would otherwise leave partially structured.
- You need commercial support or private distribution terms. Enterprise and OEM arrangements build on Pro for regulated, air-gapped, or redistribution scenarios.
Country coverage differences
| Package | Dedicated parser coverage | Fallback |
|---|---|---|
| Core | Australia, Canada (English), Canada Quebec/French, France, Germany, United Kingdom, United States | Universal fallback parser for all other countries |
| Pro Team | Everything in Core, plus Brazil, Hong Kong, Japan, and Singapore | Curated reference-data enrichment plus universal fallback where no dedicated parser exists |
| Enterprise / OEM | Licensed countries plus custom expansion by agreement | Deployment, support, and country-expansion terms by agreement |
See the full country support matrix for details.
Confidence and explainability differences
A five-question checklist
- What countries dominate your address volume?If they are outside Core's dedicated coverage, Pro's additional parsers are the most direct upgrade reason.
- Does your review process need field-level detail?If "this address is uncertain" is not specific enough, you need Pro's field-level confidence.
- Do you need to explain parsing decisions to an auditor or reviewer?Pro's trace logs exist for exactly this requirement.
- Are you preparing data for ISO 20022 messaging?Pro's field mapping is built for that specific downstream use case.
- Do you need private distribution, OEM redistribution, or air-gapped deployment terms?Those are Enterprise/OEM conversations that build on top of Pro.
Frequently asked questions
Can Core be used in production, or is it just for evaluation?
Core can be used in both development and production under the Apache License 2.0. There is no separate paid tier of Core itself — Pro is an additive commercial package, not a requirement to run Core in production.
What is the single biggest reason teams upgrade from Core to Pro?
Two reasons come up most often: needing dedicated parsing for a country outside Core coverage (currently Brazil, Hong Kong, Japan, or Singapore), or needing field-level confidence and trace logs to support a review or audit workflow that an overall confidence score cannot support on its own.
Can we start with Core and move to Pro later without rewriting our integration?
That is the intended path for most teams: evaluate and integrate with the free Core library first, then add Pro when a specific country, confidence-detail, or enrichment requirement appears. Exact upgrade mechanics should be confirmed with PassionCore for your deployment.
Tell us your target countries and review requirements.
We will help you work out whether Core is sufficient or whether Pro, Enterprise, or OEM terms fit better.