https://openexchange.dev/blog Engineering notes from building Open Exchange: the numbers and the trade-offs behind the decisions. en Thu, 23 Jul 2026 00:00:00 GMT https://openexchange.dev/blog/exchange-for-148 https://openexchange.dev/blog/exchange-for-148 Thu, 23 Jul 2026 00:00:00 GMT The full stack, six Raft nodes plus services, runs on one 4-vCPU box: about 7,500 order submissions per second end-to-end at p50 2.2ms, over a matching core that clears 150k/sec. What $148/month handles, why it is cheap to build on, and how to run your own. https://openexchange.dev/blog/v0-4-0-beta https://openexchange.dev/blog/v0-4-0-beta Wed, 22 Jul 2026 00:00:00 GMT Money moves to its own Raft cluster: the Assets Engine joins as the fifth repo, every money movement lands in a replayable journal, egress becomes totally ordered, and three HIGH CVEs get closed on release day. https://openexchange.dev/blog/demo-live https://openexchange.dev/blog/demo-live Tue, 07 Jul 2026 00:00:00 GMT Sign up at trade.openexchange.dev and trade five crypto markets against a realistic simulated crowd: funded demo balances, price action anchored to real markets, and a rebuilt trading screen. Plus everything else that shipped in the week after beta. https://openexchange.dev/blog/v0-3-0-beta https://openexchange.dev/blog/v0-3-0-beta Sun, 05 Jul 2026 00:00:00 GMT The stack reaches beta: a failover test that kills the leader on every commit, exact money math end to end, a frozen v1 API, secure defaults, and an honest 800k orders/sec baseline. https://openexchange.dev/blog/building-an-exchange-hidden-costs https://openexchange.dev/blog/building-an-exchange-hidden-costs Wed, 01 Jul 2026 00:00:00 GMT What’s actually hard about building an exchange: the durability, precision, and overload problems that sink teams, and the case for not building the core yourself. https://openexchange.dev/blog/array-backed-order-book https://openexchange.dev/blog/array-backed-order-book Sat, 27 Jun 2026 00:00:00 GMT How we replaced the matching engine’s order book, what the load tests actually showed, and the out-of-memory bug we found pushing for its limits.