-
-
FreeRoom: see every free classroom on campus, reserve it in two taps.
-
Campus map: each building is colored and labeled by how many rooms are free right now.
-
Room timeline: classes (striped, book icon) vs. reservations, with drag-to-reserve.
-
My reservations: the confirm window before the 4-hour cutoff, plus incoming claims to approve.
-
A new class took your room: instant release and 3 alternative rooms, one tap to rebook.
-
Architecture: React on CloudFront, Hono on Lambda, DynamoDB transactions + Streams, EventBridge sweeper, KMS.
Inspiration
At UMass, finding a study room means walking a building and peeking through doors. 25Live knows every class on campus, but it's built for schedulers: there's no "free right now, near me" view. And when you do find a room, a class you didn't know about can walk in.
What it does
- Live campus map: buildings colored and labeled by how many rooms are free this minute.
- Search and filter by capacity, features and building, refreshed every 10 seconds.
- Room timeline: classes (purple, striped, book icon) vs. reservations (person icon). Hover or focus a class for its course, section and department.
- Two-tap reserve: drag across free time and confirm.
- Claims: ask for a held room. The owner approves, and only then do you see the one contact they chose to share.
- 4-hour confirm cutoff: unconfirmed reservations auto-release at
start − 4h, so rooms don't get squatted. - 25Live always wins: if a new class lands on your reservation, it's released instantly and you get 3 alternative rooms with a one-tap rebook.
The demo runs on seeded UMass campus data until UMass IT grants 25Live and SSO access. The adapter and SAML support are built, so switching them on is configuration, not code.
How we built it
- React + Vite + Tailwind on S3 + CloudFront: static, cheap, fast.
- Hono on AWS Lambda behind API Gateway HTTP API: one small app, simple routing.
- DynamoDB single table + Streams: transactions enforce the core rules; Streams drive notifications, with an SQS dead-letter queue.
- EventBridge Scheduler: a 1-minute sweeper enforces the cutoff; a sync job pulls 25Live.
- Cognito: email/password now, SAML-ready for campus SSO.
- KMS + Secrets Manager: encrypted contact info and the HMAC pepper for University IDs.
- CloudFront + AWS WAF (prod): managed rules and a per-IP rate limit for both site and API.
- Amazon Location Service + MapLibre: the campus map.
- CloudWatch: structured logs with correlation IDs, a dashboard, alarms to SNS.
- AWS CDK (cdk-nag on every synth) and GitHub Actions for CI.
The hard part. A reservation is cut into 15-minute slots, and creating it is one DynamoDB TransactWriteItems with a LOCK item per slot that must not already exist. If any slot is taken, the whole write fails, so there's no read-then-write gap to race through. We fire 50 parallel requests at the same slot: exactly 1 succeeds. The 25Live sync writes class locks with the same keys, so nothing can commit over a class.
Challenges we ran into
- Concurrency: "check, then write" loses races, so we moved the guarantee into the database.
- An exact 4-hour cutoff: confirm, claim and approve are conditional writes against the server's clock. Tests prove 1 ms before the cutoff works and exactly at it fails.
- Privacy: University IDs are stored only as an HMAC. Only one Lambda can decrypt contact info, and an infrastructure test fails if any other role gets
kms:Decrypt. - Account guardrails: the hackathon account's SCP locks us to us-east-2, denies GitHub OIDC (we deploy with short-lived
aws logincredentials instead, no long-lived keys), and blocks Bedrock, so we cut natural-language search as planned.
Accomplishments that we're proud of
- Dev and prod both deployed on AWS, with separate CDK bootstraps.
- 224 automated tests (domain rules, integration on DynamoDB Local, the 50-way concurrency test, infrastructure), plus 12 Playwright tests and 12 end-to-end API flows. [CHECK]
- An adversarial release audit found no way to break the core rules or reach other users' data.
- A keyboard-accessible timeline, statuses in color + icon + text, and Lighthouse accessibility 100 on the main pages.
What we learned
- Put invariants in the database: a conditional write can't be raced; an
ifstatement can. - Inject the clock. Pure functions that take
nowmake time edge cases easy to test. - Account limits shape the architecture as much as features do.
What's next
- Plug in UMass 25Live and SSO credentials (configuration, not code).
- Bedrock natural-language search, where the model only fills in the existing filters.
- WebSockets, week view, and following a room to get notified when it frees up.
Built With
- amazon-api-gateway
- amazon-cloudfront
- amazon-cloudwatch
- amazon-cognito
- amazon-dynamodb
- amazon-eventbridge
- amazon-location-service
- amazon-sns
- amazon-sqs
- amazon-web-services
- aws-cdk
- aws-kms
- aws-lambda
- aws-secrets-manager
- aws-waf
- cdk-nag
- hono
- maplibre
- node.js
- react
- tailwindcss
- tanstack-query
- typescript
- vite
- zod