The country publishes oceans of open data — fragmented, mis-keyed, revised without notice. dbr crawls the official sources, resolves the same company, place and person across every base, and derives the indices the raw rows can't give you. All through one API.
The pattern behind every module
Every dbr module runs the same value chain. The raw layer is free and chaotic; the derived layer is defensible, licensable — and where your decision rests.
Authoritative open sources land immutable and versioned — the trusted floor.
Complementary sources are crawled, cleaned and cross-referenced against the official record.
The same company, place or person is unified across every base on shared keys.
An index, score, network or forecast the raw rows alone could never express.
Metered, versioned, auditable — the sellable product behind one gateway.
The ecosystem
Each module owns a domain and answers one question. Geography, entities and compliance speak across module boundaries on the same keys — so any record can meet any other.
Brazil's territory turned into queryable geometry — then mobility, infrastructure and environment layered on top. The spatial backbone every other module joins to.
The ~60M-company national registry turned into a connected graph: who controls what, where, in which sector — with the ownership layers the registry doesn't show.
One API for every Brazilian fiscal obligation and payment rail. Emit any document, move money on any rail — always in conformity, ready for the Tax Reform.
◎ All modules run on the shared dbr-core substrate — crawlers, entity resolution, gateway, metering & billing. The domain catalogue is expanding.
Why the parts add up
Every record, from any module, carries the same keys. A company resolves to a place, a place to an outcome, a supplier to a contract — across bases that never spoke before.
Brazilian data is revised constantly. Every datapoint carries as_of / vintage / revision — query the country as it stood on any date. Time-travel is a first-class feature.
The APIs sell indices, scores, networks and forecasts — never raw rows. That protects source licences and is exactly where the defensible value sits.
A single entry point handles authentication, rate limits, usage metering and billing — uniform across every module. For procurement and finance, it's one relationship.
Built for the people who sign the contract
Decisions get defended. dbr is engineered so the number we serve is always reproducible, the provenance always attributable, and the legal posture never in question.
Crawled data is stored as aggregates and derivations — never redistributed raw. Sensitive social data is anonymised at source and protected by small-cell suppression. No endpoint returns individual-level records.
Raw is immutable; every figure we serve is rebuildable from it at any as_of. Forecasts always ship with intervals and backtest error — never a bare point estimate.
dbr-core tracks every source's expected cadence and schema. When a layout changes without notice — as the CNPJ files did in January 2026 — ingestion stops and flags, rather than serving you quietly wrong data.
Where the data touches the public sector, dbr reports source-attributed facts with no editorialising. Interpretation is left to you; the provenance travels with every response.
Request access
Start with a single module or wire the platform end-to-end. One gateway, one contract, and a derived data layer your competitors can't assemble.