Health, home and travel decision
Seats.aero
A small technical team can build a narrow booking+seat-locking MVP (and open-source prior art exists), but reproducing a full production product (payments, compliance, UX polish, support, and scale) is nontrivial—so build an MVP yourself but keep paying for a complete hosted product if you need turnkey production readiness.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.
What a replacement has to do
- Allow users to search flights, select seats on a seatmap, reserve/checkout, and persist bookings with concurrency-safe seat locking.
What it still won’t have
- SLA-backed uptime and managed hosting
- production-grade fraud detection and payments dispute handling
- user support, refunds, and chargeback handling
- polished UX, analytics, and integrations provided by a vendor
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 1 seat.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal seat-booking web app using Next.js (React) frontend, Node.js/Express backend, Postgres for persistent bookings, Redis for seat-locking/ephemeral reservations, and Stripe for payments. In scope: flight search API (DB-backed), interactive seat map UI, booking endpoint with concurrency-safe locking and transactional seat assignment, Stripe payment flow, booking confirmation emails (SMTP/SendGrid), Docker-based deployment, basic admin UI to view bookings. Out of scope: dynamic airfare pricing engine, multi-region high-availability infra, OMS/gateway integrations, PCI hosting (use Stripe to avoid storing card data). Include error handling for lock timeouts, double-book attempts, payment failures, and unit+integration tests for booking and locking logic.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 3 cited sources+3
- 3/3 assessment runs agreed+4
- Evidence score64
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.
How scoring works →Cited sources · 3
Every page the run actually retrieved.
- official productSeats.aero — Home
- open sourcedebuggerdragon311/airline-reservation-system
- open sourcenileshkapse/Flight-Booking-Reservation-System
Integrity checks
What held up, and what did not.
