01
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
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 directly
0+Countries under one worldwide licence
0M+Company profiles with field-level provenance
DailySynced change feeds where registries publish them
Connected directly to 400+ national registries
Companies HouseUnited KingdomHandelsregisterGermanyRegistre du Commerce et des SociétésFranceKVK HandelsregisterNetherlandsSEC EDGARUnited StatesRegistro ImpreseItalyRegistro MercantilSpainBolagsverketSwedenACRASingaporeCorporations CanadaCanadaKrajowy Rejestr SądowyPolandASICAustraliaZefixSwitzerlandBrønnøysundregistreneNorwayMinistry of Corporate AffairsIndiaKruispuntbank van OndernemingenBelgiumNational Tax AgencyJapanErhvervsstyrelsen CVRDenmarkCompanies Registration OfficeIrelandReceita Federal CNPJBrazilFirmenbuchAustriaCompanies RegistryHong KongPatentti- ja rekisterihallitusFinlandCIPCSouth AfricaObchodní rejstříkCzechiaRegisto ComercialPortugalCompanies OfficeNew ZealandRCS LuxembourgLuxembourgGEMIGreeceRegistro Público de ComercioMexicoCompanies HouseUnited KingdomHandelsregisterGermanyRegistre du Commerce et des SociétésFranceKVK HandelsregisterNetherlandsSEC EDGARUnited StatesRegistro ImpreseItalyRegistro MercantilSpainBolagsverketSwedenACRASingaporeCorporations CanadaCanadaKrajowy Rejestr SądowyPolandASICAustraliaZefixSwitzerlandBrønnøysundregistreneNorwayMinistry of Corporate AffairsIndiaKruispuntbank van OndernemingenBelgiumNational Tax AgencyJapanErhvervsstyrelsen CVRDenmarkCompanies Registration OfficeIrelandReceita Federal CNPJBrazilFirmenbuchAustriaCompanies RegistryHong KongPatentti- ja rekisterihallitusFinlandCIPCSouth AfricaObchodní rejstříkCzechiaRegisto ComercialPortugalCompanies OfficeNew ZealandRCS LuxembourgLuxembourgGEMIGreeceRegistro Público de ComercioMexico
How 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.
01“You can use it internally, but you can’t pass it to your customers.”
02“That licence covers Europe. Asia would be a separate deal.”
03“You can’t use it to train or improve a model.”
04“When the contract ends, you delete everything.”
05“We can’t tell you which registry that came from.”
06“There are no timestamps. We refresh the whole file quarterly.”
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 | Global 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.
01Every record is read from a government registry.400+ national registries, gazettes and filing authorities, connected at source.
02Every field names the registry it came from.Attribution sits on the field itself, rather than once on the file.
03Every record links back to the filing.A deep link to the source record, which you can pass through to your own users.
04Every field carries two dates.The date the registry recorded it, and the date we retrieved it.
05The filed document comes with it.The official filing itself, wherever the registry publishes one.
06Your customers keep what they export.Download and retention rights, under your commercial terms and your brand.
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.
02
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
03
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
04
Shareholders and ownership
- Shareholders and shareholdings
- Share classes and percentages
- Beneficial owners (PSCs and UBOs)
- Ownership percentages
- Ultimate beneficial owner chain
05
Group structure
- Immediate parent
- Global ultimate owner
- Subsidiaries and branches
- Corporate linkage across registries
- Cross-registry entity resolution
06
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
Up to 40 fields per record. See the full data dictionary.
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.
Bulk snapshotParquet · CSV · JSONL
The full corpus, or a subset scoped by country, sector, size or entity type, written to storage you control.
Daily deltasChanged records only
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.
APIREST · JSON
Instant lookup by identifier, name or address for the paths that have to run live inside your product.
Cloud and warehouseS3 · GCS · Azure · Snowflake · BigQuery
Written into infrastructure you already own, with no transfer layer for your team to build or monitor.
MCP serverEndpoint
Exposes the licensed corpus as tools to Claude and any other Model Context Protocol client, on the same key and the same provenance fields.
Claude & ChatGPTConnector
One-click connectors for both assistants. Ask for a company in plain language and get the licensed record back.
Your schemaField mapping
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.
| Model | Who the data reaches | What they may do |
|---|---|---|
| 01Internal use1 of 4 | ReachesYour own team and systems | MayEnrich internal systems |
| 02Embedded2 of 4 | ReachesYour users, on screen | MayDisplay inside your product |
| 03Redistribution3 of 4 | ReachesYour users, in files they keep | MayExport, download and retain |
| 04AI & model development4 of 4 | ReachesYour models and retrieval indexes | MayTrain, fine-tune, evaluate, ground |
The questions procurement asks first
Can our customers export the data out of our product?
Yes, under a redistribution licence. Your users can view, export, download and retain the records you surface, and you set the commercial terms they see. That right sits in the base schedule rather than behind a per-seat surcharge.
What happens to the data when the contract ends?
Records delivered during the term stay with you. There is no deletion obligation on data already supplied and no certificate to sign. What ends is the flow of new records and updates, which makes the switching decision a commercial one rather than a product outage.
Are we licensed to use this to train a model?
Under a separate written grant, yes. It covers pretraining, fine-tuning, evaluation sets, retrieval indexes and synthetic data generation, scoped so your legal team is not reading silence and guessing. Provenance is retained through the pipeline, so a model output can be traced back to a specific filing.
Is the licence limited to certain regions?
The territory is worldwide. Coverage is priced by what you take rather than by where your users happen to sit, so opening a new market does not reopen the contract.
Where does the data come from?
Directly from government company registries, gazettes and filing authorities across 200+ countries. We have been building those source connections for twelve years. Each field carries the name of the registry it came from, so the chain from your customer’s screen back to the original filing stays unbroken.
How do we know how fresh a record is?
Two dates travel with every field: the date the registry recorded the information, and the date we last retrieved it. Change feeds are synced daily against the registries that publish on a daily cycle, and the retrieval date makes the actual cadence visible per field rather than asserted at file level.
Will we be locked into your identifiers?
No. Every record ships with its native registry identifiers alongside our own keys. If you move, your joins survive, because they were never built on something only we can resolve.
Can we evaluate a sample before committing?
Yes. We scope a representative sample to the jurisdictions and fields you care about, in the format you intend to ingest, so your team tests the real schema rather than a marketing extract.
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.
01
You paste the clause, or describe the restriction in your own words.
02
Our licensing desk answers in writing within two business days, in plain language.
03
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