file 01/06 · brief
home / projects / bizzdeck
// case study · backend & cloud

The engine room of
a restaurant SaaS.

Backend and serverless cloud for BizzDeck LLP: the API layer restaurants rely on to run their online sales.

client · bizzdeck llprole · backend + infrasince · apr 2025
live in production ↗
BizzDeck restaurant SaaS · screenshot
the story
// 01 · the challenge

Dinner rush is
a load profile.

BizzDeck needed a backend restaurants could bet their evenings on, highly available, quick to ship, priced like a startup, on a deadline that didn't move.

Traffic that spikes at mealtimes and sleeps at dawn is exactly what serverless is for, if you can do it without cold-start pain or runaway bills.

// 02 · what we built

Built to spike,
priced to sleep.

Serverless by design
Infrastructure that scales with service hours: busy at eight, nearly free at four in the morning.
An API layer that stays quick
Endpoints for menus, orders and sales built for the dinner-rush spike, not the average.
Postgres as the source of truth
Orders, accounts and sales in one reliable relational core: boring on purpose, correct always.
Shipped inside the deadline
Production-ready on the date promised, with headroom for the restaurants still to come.
// 03 · the stack

Boring where it should be.

Proven parts, assembled carefully. Novelty goes into the product, not the plumbing.

api
Node + Express
data
PostgreSQL
infra
Serverless
billing
Scales to zero
backend buildcloud infrastructure
// 04 · in production

Fast at eight, free at four.

0 idleserverless infra spends nothing while the restaurants sleep, and scales the moment they don't.
on timeproduction-ready backend delivered inside a tight deadline, with headroom to grow.
livethe API layer behind bizzdeck.com, taking restaurant orders right now.