Guinness · Platform briefing
Kura — Guinness's In-House Data Engine
Internal · The data engine running on Guinness's own Hetzner box — serves Guinness-owned data directly, falls back to x-trillion Orca for the rest, and keeps a dated snapshot of every live answer so the apps never go dark. Not a client-facing app.
Native first, Orca fallback#
Kura is internal. It runs on the Guinness box (kura.guinness.x-trillion.com) and sits between Brian and x-trillion's Orca gateway. For a small but growing set of tools it answers directly from Guinness-owned sources; for everything else it forwards to Orca and returns the same answer Orca would have given.
- Internal — not in the client sidebar, no login screen of its own.
- Native today: sovereign-credit indicators (World Bank Open Data, licence-free) and macro time series (Haver Analytics, Guinness's own subscription).
- Everything else is routed straight through to x-trillion Orca — the "strangler" pattern: native grows, the fallback shrinks over time.
Every live answer is snapshotted#
Kura always tries live Orca first — while Orca is healthy, nobody sees anything different. Behind the scenes, every successful answer is written to a small SQLite store on the box, stamped with the date it was fetched.
- Live is attempted on every single call — no artificial staleness.
- If Orca is slow, unreachable, or the connection to x-trillion is ever lost entirely, Kura serves the last stored copy instead of an error — clearly marked as dated, never presented as live.
- The moment Orca is reachable again, answers go back to live automatically. A queued query the moment it's asked while offline gets backfilled by a
/refreshreplay once Orca returns.
Why it matters#
Guinness already owns some of its data outright rather than licensing it through x-trillion — World Bank sovereign indicators are free and public, and Haver Analytics macro data is served through Guinness's own paid subscription. Kura is where that ownership actually shows up in the running platform: those answers come from Guinness's own pipes, not x-trillion's.
The snapshot layer is the other half of the same idea. If the relationship with x-trillion ever changes, the apps built on top of Kura keep answering — on the last known-good data, honestly dated — rather than breaking outright the day Orca access ends.
For the team#
Kura is internal plumbing. Users never open it directly — this guide explains what sits behind Brian's data answers, and why the platform keeps working even if x-trillion's Orca is ever unavailable.