Offers Work About 2 slots · May Book a call

Case study · Calendbook

Calendbook.
Scheduling for SMBs, on AWS serverless from day 1.

Co-founded and run by me. Booking, calendar sync, payments, multi-language. Built and deployed entirely on AWS serverless, in production with paying customers.

Calendbook screenshot 1Calendbook screenshot 2Calendbook screenshot 3

01 / Role

What I built and run.

Co-founder, backend and infrastructure lead. I designed the AWS architecture, wrote the backend in Python on Lambda, built the booking and calendar-sync engine, integrated Stripe and the email pipeline, and handle everything from the database schema to the deploy pipeline.

The frontend is Next.js. I work across the stack but the system design and the production line are mine.

02 / Stack

What it runs on.

  • · AWS Lambda (Python) behind API Gateway for every backend endpoint.
  • · DynamoDB single-table for bookings, schedules, integrations, with TTL for cleanup.
  • · Step Functions for the booking orchestration (calendar conflict checks, calendar writes, email confirmations, payment capture).
  • · EventBridge for the cross-tenant event bus (booking created, cancelled, rescheduled).
  • · S3 + CloudFront for static assets and the Next.js export.
  • · Cognito for auth, with Google and Microsoft federation.
  • · SES for transactional email, plus webhooks back into the system.
  • · CloudWatch + structured logs + alarms for observability. Sentry for the frontend.
  • · Terraform + GitHub Actions for IaC and CI/CD. Blue-green deploys with canary traffic.

03 / Outcome

What it does today.

Calendbook serves SMBs and professionals across multiple countries with localized booking flows. The AWS serverless choice keeps unit economics tight, since cost scales with usage instead of with idle infrastructure. There is no team running ops at night, the system runs itself.

Every architecture decision I make for client MVPs is informed by what I had to fix in Calendbook. The case study is also a stress-test of my own methodology.

Apply this

Want a serverless backend like this?

If you need AWS serverless for an MVP or a rescue, the same playbook applies. Start with a 30-min call.

Book a 30-min call

Related