
SeatRelay: Turning Empty Bus Seats into Second Chances with AWS
What if a cancelled bus ticket didn't have to mean lost money? SeatRelay uses cloud technology to create a trusted way for passengers to transfer unused seats while keeping operators in control.
The Problem: A Seat Can Be Empty Without Being Available
Imagine booking a ₹850 bus ticket and having your plans change a few hours before departure. Under a typical cancellation policy, you may lose the money.
Meanwhile, another traveller is looking for the same route and sees “Sold Out.”
The problem isn't a lack of demand. It's a lack of a trusted transfer mechanism.
We wanted to build a system where:
- Sellers can recover the value of an unused ticket.
- Buyers pay the original ticket price, not a scalped price.
- Operators remain in control of the transfer.
- The passenger manifest stays accurate.
- A single seat can never be claimed by two people.
That became the foundation of SeatRelay.
What We Built
SeatRelay is an operator-authorized ticket transfer platform.
The workflow is intentionally simple:
Seller lists seat → Buyer claims it → Payment is held → Operator approves → Original ticket is cancelled → New ticket is issued.
The important part is what happens behind the scenes.
A listing isn't simply marked as “sold.” It moves through explicit states:
LISTED ↓CLAIMED ↓PAYMENT HELD ↓AWAITING OPERATOR ↓REISSUED ↓COMPLETED
If something goes wrong, the workflow can move backwards safely — for example, releasing a claim when payment times out or cancelling the transfer when an operator rejects it.
Where the Architecture Gets Interesting
The hardest part isn't displaying available seats.
It's preventing two people from buying the same seat at the same time.
Imagine two buyers click Claim within milliseconds of each other.
Our system needs to guarantee:
One seat → One successful claim.
The current implementation uses guarded state transitions. In the production AWS architecture, this responsibility maps naturally to Amazon DynamoDB conditional writes, allowing the database to reject a claim if the listing has already changed state.
The transfer itself is also a perfect candidate for AWS Step Functions.
Instead of treating a ticket transfer as one huge backend request, we can model it as a workflow with clear success and failure states.
For example:
Claim ↓Hold Payment ↓Operator Decision ├── Approve → Reissue Ticket └── Reject → Release Payment
This makes failure a designed part of the system rather than an afterthought.
Our AWS Roadmap
The current EC2 deployment is our hackathon implementation. As the platform grows, individual responsibilities can move to managed AWS services:
Requirement | AWS Service |
|---|---|
Frontend hosting | AWS Amplify |
Authentication & roles | Amazon Cognito |
APIs | API Gateway + AWS Lambda |
Transaction data | Amazon DynamoDB |
Workflow orchestration | AWS Step Functions |
Scheduled expiry | Amazon EventBridge |
Notifications | Amazon SNS |
Ticket storage | Amazon S3 |
Monitoring | Amazon CloudWatch |
This gives SeatRelay a natural path from a hackathon prototype to an event-driven cloud architecture.
What Fought Back
The hardest challenges weren't the flashy features.
They were the edge cases.
What if two buyers claim the same seat?
Only one should win.
What if payment succeeds but the operator rejects the transfer?
The transaction needs a safe rollback path.
What if nobody buys the seat?
The listing must automatically expire before departure.
What if the operator never responds?
The workflow cannot remain stuck forever.
These cases forced us to think beyond CRUD operations and treat the application as a stateful transaction system.
That changed how we designed the entire backend.
More Than a Ticket Marketplace
SeatRelay isn't really about selling bus tickets.
It's about creating a trusted bridge between unused capacity and unmet demand.
The seller gets a chance to recover their money.
The buyer gets a genuine seat at the original price.
The operator keeps control of the passenger manifest.
And the seat gets a second chance.
We started with a simple question:
What if a cancelled ticket didn't have to become a lost seat?
With SeatRelay, we're building the answer — one transfer at a time, with AWS providing the foundation to take it beyond the hackathon.
One empty seat. One waiting passenger. One trusted transfer.
Built for First Commit – Bharat Builds 2026
WeMakeDevs × AWS
-Team VOID
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article