All activity
KCCleft a comment
👋 Makers, I built the Forex Consensus Engine because I got tired of the "Multi-Source Paradox." I saw Risk teams using one price (e.g., from Reuters) and Accounting teams using another (e.g., from Bloomberg), simply because their APIs were out of sync by 200ms. This creates a Valuation Gap that fails audits and bleeds P&L. Most solutions ask you to send your trade data to their cloud API to...
Forex Consensus EngineThe self-hosted "Supreme Court" for your price feeds.
The "Multi-Source Paradox" costs banks millions: Bloomberg says 1.05, Reuters says 1.07, and Risk model is flying blind.
The Forex Consensus Engine (FCE) is not another data feed. It is a sovereign Arbitration Layer that sits inside VPC.
How it works:
Ingest: Pipes in existing feeds (Fix/REST/Socket).
Police: Uses Context-Aware Physics to detect "Flatlines" and "Flash Crashes" in real-time.
Unify: Outputs a single, mathematically defensible "Golden Source" rate for downstream apps.
Forex Consensus EngineThe self-hosted "Supreme Court" for your price feeds.
KCCleft a comment
👋 Makers, I built this because I got tired of the 'Valuation Gap.' working in institutional fintech, I saw Risk teams using one price and Accounting teams using another, just because their APIs were out of sync by 200ms. The FCE is designed to be a 'Sovereign' piece of infrastructure. It doesn't rely on my servers. It runs on yours (Docker). It treats Price not as a fact, but as a consensus...
Forex Consensus EngineThe self-hosted "Supreme Court" for your price feeds.