The data arrives before the decision.
You declare where each field comes from. The pipeline fetches everything at once, with your operation's credentials, and hands the policy the complete input.
Illustrative timings: they show the effect of fetching in parallel, not a measurement.
Four ways to bring in a field
Your contract and your key. Today: BigDataCorp.
Any API — yours, a partner's, a vendor's.
Watchlists, spreadsheets, exception lists, as JSON.
An event that already went through your pipeline.
It never decides with missing data
Each source is marked optional or required, and each has its own timeout. The behaviour on failure is declared up front, not improvised on the spot.
The policy decides with what arrived. The decision shows which source was missing and why.
Without the field the rule requires there's no decision — and an aborted execution doesn't count toward your allowance.
Lookups run on your contract
We don't resell data. The pipeline uses your operation's credentials, and every lookup carries its declared purpose — which is what Brazil's LGPD asks for as proof.
- Caching
- The same lookup within the window you set is answered without going back to the bureau.
- Deduplication
- The same document at the same moment becomes one lookup, not three.
- Cost
- How much each organization spent on lookups, measured, not estimated.
- Isolation
- Files and queues are only read inside your organization's space; HTTP calls are protected against internal addresses.