License registry data to power your own product
Primary, government-sourced company data from 400+ national registries, delivered with redistribution rights, worldwide territory, and a perpetual licence on every record we send you.
0+
Government registries sourced directly0+
Countries under one worldwide licence0M+
Company profiles with field-level provenanceDaily
Synced change feeds where registries publish themHow many of these have you heard from a data vendor?
Coverage is the easy part. These six clauses sit in the agreement underneath it, and between them they decide what you can build, who you can sell it to, and what happens on the day you change supplier. A data licence is a product decision.
What the licence actually gives you
Written to be built on. The rights below sit in the standard schedule rather than behind a surcharge, an amendment, or a conversation you reopen at every renewal.
| Right | Standard scheduleGlobal Database | Typical market terms |
|---|---|---|
| Redistribution to your end customers | Global DatabaseGranted in the base licence | Typical market termsInternal use only, or a per-seat surcharge |
| Territory | Global DatabaseWorldwide, every market you sell into | Typical market termsScoped by region and repriced as you expand |
| Sublicensing to your own resellers | Global DatabaseGranted where the channel is named | Typical market termsCase by case, vendor approval per partner |
| AI training and model development | Global DatabaseLicensed in writing, retrieval and evaluation included | Typical market termsProhibited by default, silent on retrieval and evaluation |
| Records after termination | Global DatabasePerpetual for records delivered in-term | Typical market termsDeletion within a fixed window, certified in writing |
| Source attribution | Global DatabaseRegistry named on every field | Typical market termsNormalised output, origin removed |
| Field-level dating | Global DatabaseFiling date and retrieval timestamp, per field | Typical market termsA single file-level refresh date, if any |
| Identifiers | Global DatabaseOpen registry identifiers alongside ours | Typical market termsProprietary keys, resolvable only by the vendor |
What travels with every record
Six properties that survive the handover into your product and reach the person using it.
Every field on the resolved record, sourced
Up to 40 fields per company, grouped into six categories. Each one is read from the registry it was filed with and carries that source through to you. Modelled values are labelled as modelled.
Company registry data
- Legal name and previous names
- Registration number, VAT and tax IDs
- Legal form and incorporation date
- Company status
- Registered and trading addresses
- Registry source and filing link
Financials
- Filed revenue and turnover
- Assets, liabilities and net worth
- Profit and loss figures
- Filing history and latest accounts
- Currency and reporting period
- Multi-year financial trend
Firmographics
- Industry codes: SIC, NACE, NAICS
- Employee counts and size bands
- Company age and trading status
- Websites and digital footprint
- Phone numbers
- Geographic and jurisdiction data
Shareholders and ownership
- Shareholders and shareholdings
- Share classes and percentages
- Beneficial owners (PSCs and UBOs)
- Ownership percentages
- Ultimate beneficial owner chain
Group structure
- Immediate parent
- Global ultimate owner
- Subsidiaries and branches
- Corporate linkage across registries
- Cross-registry entity resolution
Directors and officers
- Directors and active officers
- Officer role and position
- Appointment and resignation dates
- Nationality and country of residence
- Date of birth, where filed
- Occupation
Shipped the way your pipeline already expects it
The licence decides what you may do with the data. Delivery decides how fast you can ship it.
The full corpus, or a subset scoped by country, sector, size or entity type, written to storage you control.
Only what changed since the last file, on the same schema and the same keys, so the load is a diff rather than a rebuild.
Instant lookup by identifier, name or address for the paths that have to run live inside your product.
Written into infrastructure you already own, with no transfer layer for your team to build or monitor.
Exposes the licensed corpus as tools to Claude and any other Model Context Protocol client, on the same key and the same provenance fields.
One-click connectors for both assistants. Ask for a company in plain language and get the licensed record back.
Mapped to your field names, your types and your identifiers before the first delivery, so ingestion is a scheduled job rather than a project.
Train on it, with a licence that says so
Registry data suits model work: structured, jurisdictionally diverse, factual, and dated at source. Permission is the part that is normally missing.
Pretraining. Fine-tuning. Evaluation. Retrieval. Synthetic data. All five, granted in writing.
Four ways teams license it
The difference between the four is who the data reaches and what they may do once it gets there. The grant scales with what you are building.
- 01Internal use1 of 4ReachesYour own team and systemsMayEnrich internal systems
- 02Embedded2 of 4ReachesYour users, on screenMayDisplay inside your product
- 03Redistribution3 of 4ReachesYour users, in files they keepMayExport, download and retain
- 04AI & model development4 of 4ReachesYour models and retrieval indexesMayTrain, fine-tune, evaluate, ground
The questions procurement asks first
Can our customers export the data out of our product?
What happens to the data when the contract ends?
Are we licensed to use this to train a model?
Is the licence limited to certain regions?
Where does the data come from?
How do we know how fresh a record is?
Will we be locked into your identifiers?
Can we evaluate a sample before committing?
Send us the clause
that is blocking you
Most licensing conversations start with a redistribution restriction, a territory limit, or a deletion obligation someone found in week three of legal review. Send the clause. We tell you directly whether we can grant it.
You paste the clause, or describe the restriction in your own words.
Our licensing desk answers in writing within two business days, in plain language.
If it works, a scoped sample lands in your schema before anything is signed.
Every delivery is logged, encrypted in transit, and processed under a signed data processing agreement.
- GDPR aligned
- SOC 2 Type II
- ISO 27001
- Signed DPA on every contract