Counterfoil: From a Booking Monolith to an Event-Driven Platform

The challenge

Counterfoil's first-generation product proved the model but grew into a monolith where booking, billing, and identity were tightly coupled — hard to evolve and hard to reuse across new surfaces.

Our approach

Ternary keeps the production platform stable and maintained while rebuilding it in parallel as Continuum: an event-driven architecture that separates concerns into independent services with clear API boundaries.

What we built

Continuum is organized as focused services — identity and tenancy, a booking engine, sales, and notifications — communicating through a reliable outbox-to-queue pattern, with a modern operator dashboard on top. The booking engine encodes a "Unified Booking Theory": a bitmask inventory model that computes real-time availability and fans updates out over WebSockets.

To make the platform reusable across products, every surface is served by a generated SDK — operator, customer, partner, and storefront — wire-generated from the API contract so web, mobile, and partner integrations stay in lockstep.

Where it stands

The original platform remains live and maintained; Continuum is in active development, moving the core booking logic into a foundation that multiple front-ends and partners can build on.