Full-Stack Cloud Platform

The Problem

A production entertainment company needed to replace a patchwork of spreadsheets, email chains, and manual processes with a unified digital platform. The technical team was small (just me), the budget was tight, and the system needed to handle scheduling for 7+ audio engineers, event management, invoicing, and real-time coordination — all without traditional server infrastructure.

The Approach

I chose Cloudflare's edge platform as the foundation: Workers for compute, D1 for the relational database, KV for caching and session management, R2 for file storage. This gave me a serverless architecture with global edge distribution, zero cold starts, and minimal operational overhead.

The entire system lives in a monorepo, with each application deployed as its own Cloudflare Pages project sharing a common API layer built on Hono.

Architecture

Five distinct applications serve different user roles:

• Admin Dashboard — Full CRUD for events, personnel, venues, and financial data. Role-based access control.
• Scheduling Portal — Band leaders can view and manage their upcoming shows, submit availability, and coordinate with the team.
• Invoice System — Contractors submit invoices tied to specific events. Automated calculation of rates, taxes, and payment tracking.
• Calendar Feeds — iCal-compatible feeds that sync directly to Google Calendar, Apple Calendar, or any CalDAV client.
• iOS Companion — SwiftUI mobile app backed by the same API for on-the-go access.

Authentication supports WebAuthn passkeys alongside OAuth with Google, Apple, Microsoft, and Azure AD — handling both personal and corporate identity providers.

Background processing uses Cloudflare Cron Triggers for scheduled notifications, data aggregation, and cleanup tasks. Real-time presence tracking lets the admin dashboard show who's online.

Key Achievements

• 5 production applications serving daily operations for a team of 20+ across multiple venues
• WebAuthn passkey authentication — passwordless login alongside traditional OAuth providers
• Zero-downtime deployments via Cloudflare Pages with preview URLs for every PR
• Real-time presence tracking across the admin dashboard
• Automated iCal feeds syncing directly to users' calendar apps
• Sub-50ms response times globally thanks to edge computing

What I Learned

Building an entire platform solo taught me to make ruthless architecture decisions. Every abstraction had to earn its place. The Cloudflare edge stack proved that you can build production-grade SaaS without managing any infrastructure — D1 handles the relational data, KV handles the ephemeral state, and Workers handle the compute. The monorepo structure kept shared logic DRY while letting each app evolve independently.