The country,
alive.
Static directories rot the moment they ship. Bell's data doesn't. Every record on the graph is polled continuously, every change is detected and timestamped, every fact carries its own freshness — down to the 60-second air-traffic ping, up to the weekly sector report.
Twenty-two record types. Five refresh tiers. Continuous, every day, on Bell-owned infrastructure.
Every record type, on its own clock.
The pulse of the country isn't uniform. Air traffic moves by the second; macro indicators move by the week. Bell respects that. Below: every record type and the exact cadence Bell polls, change-detects, and updates it.
Field-level diffs, as they land.
Not events — field-level changes. This is what ‘alive’ actually looks like, inside the graph: every datapoint compared against its previous value, every diff captured with its source attached. Watch a new change land at the top every few seconds.
- Tayyar FintechEmployee count3847LinkedInjust now
- Doha Health NetworkCFOvacantYousef Al-MannaiMoCI filing8s ago
- QTerminalsOpen tenders23QFC bulletin22s ago
- Industries QatarFamily-office LP %22%24%MoCI registry41s ago
Same record. Six months later.
The same record on Doha Health Network, seen through a static directory frozen six months ago versus seen through Bell's live graph today. Where they diverge is what you missed.
Catching change without lying to chase it.
Detecting that something changed is the easy part. The hard part is knowing it actually changed — not just that one source said so. Bell's change-detection engine corroborates, weights, cites, and resolves every change before it promotes to the record.
Field-level diffs
Bell diffs every record at the field level, not the record level. Knowing what changed is more useful than knowing that something changed.
Multi-source corroboration
A change only lands when corroborating sources agree. Single-source disagreements are flagged for review, not promoted to the record.
Confidence-weighted promotion
Each change carries a confidence score derived from source strength, agreement count, and historical reliability. High-confidence changes promote instantly.
Source-level provenance
Every change in the record carries the source that caused it. Click any datapoint — see exactly what fired, exactly when, exactly where.
Full change history
Every change a record has ever had is retained. Replay the record at any past date and see what it looked like, what it knew, what sources it cited.
Bella-augmented resolution
When sources disagree or a change is ambiguous, Bella reviews the candidates, evaluates the evidence, and proposes the resolution — with reasoning attached.
Every surface inherits the pulse.
Live isn't a separate product. It's the property that every other surface inherits — the CRM is fresh because Live keeps it fresh; the Map pulses because Live emits the changes; Intent and Prediction work because Live keeps the rate of change honest.
Live is one of four.
You've just read why the data stays alive. The other three Data surfaces explain what's in it, how it's built, and how it's protected.
What Bell.qa changes when data stays alive.
Cadence is observable per record type. Every diff is timestamped, sourced, and replayable. You can audit the freshness of any field at any point in history — the graph remembers.
The records you procure aren't snapshots. Every field carries its last-verified timestamp; every change carries its corroboration; every datapoint stays as fresh as the country. No quarterly stale-data write-off.
Live is the defensibility moat. Anyone can license a dataset; nobody else has built the change-detection engine that keeps a Qatari country graph current, on Bell-owned servers, with full provenance.
Records that don't age.
Twenty-two record types. Five refresh tiers. 1.2 billion datapoints kept current every single day. Every field cited, every change replayable, every record as fresh as the country it represents.