Case Study · ZapBook
Weekly crashes. Shadow spreadsheets. Customers verifying your data externally.
Five years of growth pushed ZapBook past a single-VPS architecture. We rebuilt on GCP with zero-downtime deploys, 12+ verified reporting verticals, a white-label booking widget, and Square reconciliation.
Status: Live; Phase II ongoing.
Last updated:
Problem
The challenge
Five years of growth had pushed ZapBook past what its single-VPS architecture could support — weekly crashes under peak load. Operators maintained shadow spreadsheets to verify booking and revenue data against the platform.
Outcome
What we built
We rebuilt from the ground up: GCP + Cloud Run + Docker for auto-scaling with zero-downtime deployments, 12+ reporting verticals rebuilt with verified accuracy, plus an embeddable white-label booking widget and Square payment integration with full reconciliation.
- →GCP + Cloud Run + Docker migration
- →Zero-downtime deployment pipeline
- →12+ reporting verticals verified
- →Embeddable white-label booking widget
- →Square payment + reconciliation
Tech stack
Full stack used on this build
Screenshots
Product in context
Talk to an engineer
30 minutes. You'll leave with a rough scope and a real timeline — whether or not you work with us.
