The Next Version of Curling IO
This post reflects our earlier Gleam exploration for Curling IO v3. We ultimately chose Rust and TypeScript. Why We Chose Rust for Version 3 explains that decision and what we kept from the exploration.
This is an overview of the technical foundation explored for Curling IO v3. It is written for software engineers and others interested in application architecture, and goes deeper into Gleam, the BEAM, SQLite, hosting, and scaling than our usual product posts.
The next version of Curling IO should feel familiar: the same registrations, schedules, scoring, and club admin workflows, just faster and harder to break. The work is mostly under the surface, but the payoff is practical: fewer slowdowns at peak registration, better reliability during live events, and a platform we can keep improving for a long time.
This series explains what changes, what doesn't, and why we're making the bet.