The national registry tells you a company exists. It won't tell you who really controls it, which ownership layers sit behind it — or that your new supplier shares an owner with a sanctioned firm. dbr-org resolves the people behind the entities and draws the links the registry won't draw for you.
The foundation
We anchor on Receita Federal's open company data and cross-link the procurement, sanctions and identity sources that turn a flat list into a graph of relationships.
The full national registry — companies, establishments, partners, Simples. Monthly snapshots, diffed and reconciled at every layout change.
Portal da Transparência and PNCP — contracts, transfers and the supplier–government relationships that turn control into money flows.
CEIS, CNEP and CEPIM — the firms and people barred from public dealings, joined straight onto the ownership graph.
Global legal-entity identifiers and commercial-registry records that disambiguate and enrich who is who.
The derived layer — what you actually buy
Onboarding a supplier, vetting a counterparty, mapping a market, defending a procurement decision — these are the entity products that sit between you and an avoidable loss.
Trace control past the nominees to the people who actually own the entity — the ultimate-owner graph the registry won't draw for you.
Surface the patterns that mark a structure built to hide: shared addresses, circular ownership, dormant fronts.
The supplier–government graph: who wins what, from whom, and which relationships should never have cleared.
Business openings and closings, and how concentrated a sector or region really is — market structure as a queryable number.
One call screens a counterparty against ownership, sanctions and risk — due diligence that finishes before the meeting does.
Subscribe to a CNPJ or a node and get notified when ownership, status or risk shifts — diligence that doesn't expire the day after you run it.
The dominant challenge — and why it's our moat
what breaks naïvely
CPF comes masked, partner names are free text, identifiers change format, and the whole thing arrives as monthly snapshots that must be diffed. Join on the obvious fields and you merge two different people — or miss that they're the same one.
how dbr-org solves it
dbr-core's record-linkage engine assigns one resolved node_id to a person — whether they appear as a partner here, a donor elsewhere or a candidate — with calibrated confidence, not a brittle string match. That resolution, run on the hardest data in the country, is the asset competitors can't quickly copy.
API surface
Behind the shared dbr-core gateway. Every entity carries a resolved node_id; addresses geocode through dbr-geo.
Part of a bigger machine
Once a company resolves to a node, it can be placed on the map and connected to its obligations and money flows. The graph reaches across the whole platform.
Request access
Beneficial ownership, sanctions exposure and public-sector links — screened in one call, monitored from then on.