Production meet operations

Pole Vault Meet Manager

A web and mobile platform that runs registrations, check-in, scoring, live results, and organizer workflows from one shared system.

StatusLive production system
PlatformsWeb, iOS, Android
RoleProduct owner and full-stack engineer
SourcePrivate repository
DemoFresh fictional scoring flight
Authenticated Pole Vault Meet Manager dashboard showing event operations and athlete counts
Production interfaceCaptured August 2026

The product

Built around a real workflow.

I designed this around the pressure of a real meet day: many athletes, multiple devices, fast scoring decisions, and no room for data drift. The product combines public registration and results with role-aware administration, native clients, operational health checks, and a shared backend.

  • Meet and camp registration, athlete check-in, organizer administration, scoring, and live public results.
  • Shared Convex data and scoring workflows used by the web experience and native clients.
  • Self-hosted across primary and failover Linux servers with Cloudflare routing, health checks, automated deployments, backups, and recovery drills.

Architecture

From user action to production service.

A public, high-level view of the system. Credentials, private data, deployment identifiers, and source code remain protected.

01Athletes + staff

Web, iPhone, iPad, and Android clients

02Cloudflare edge

Traffic routing, tunnel, health, and failover

03Application layer

Flask pages, public APIs, mobile APIs, and admin routes

04Shared backend

Convex functions and authoritative production data

05Self-hosted operations

Two Linux servers, monitoring, backups, failover, and releases

Technology stack
PythonFlaskTypeScriptConvexReact NativeExpoCloudflare

Engineering decisions

What makes the system hold together.

01

One scoring model

Web and native scoring share the same backend rules so attempt limits and results remain consistent across devices.

02

Production resilience

Cloudflare routing, health endpoints, primary and failover services, backups, and documented recovery paths reduce meet-day risk.

03

Release discipline

Code changes move through explicit checks and repeatable native release workflows before reaching athletes and organizers.

Next projectPV Video Capture