A Foundational Creations product
Valet operations,
run in real time.
Digital tickets, guest car requests over WhatsApp, one-driver-per-car dispatch and owner analytics — built for hotels, hospitals, malls, restaurants and venues.
Preparing first pilot · not yet deployed with a customer
The problem
Valet parking still runs on paper stubs and radios
Lost tickets, wrong cars
Paper stubs and hand-written plates cause disputes and delays right at the door.
Guests wait blind
No way to ask for the car ahead of time, and no way to see when it will actually arrive.
Owners see nothing
No record of wait times, damage claims or how each driver performed.
ValetBee is vertical operations software. Its value is correctness and reliability at the door — AI is a planned add-on, not the core.
Workflow
Every car request follows one path
1 GUEST TAP → 7 STATES → CAR AT THE DOOR
Guests see each step live. Drivers move a car forward in three to five taps. Owners see every lane at once.
Dispatch guarantees
One request, one driver — enforced by the database
-- the claim, as one conditional update UPDATE vehicle_requests SET status = 'claimed', claimed_by = $1, claimed_at = NOW() WHERE id = $2 AND status = 'waiting' RETURNING ticket_id; -- loser → 409 VEHICLE_REQUEST_ALREADY_CLAIMED
Two drivers can never walk to the same car. The database decides the winner, not the app.
Tenant isolation
A venue's business_id is resolved from the session and never trusted from the client, so one venue can never read another's records.
Transactional outbox
Guest messages are written in the same transaction as the state change; a SKIP LOCKED worker delivers and retries them.
Realtime board
A WebSocket hub pushes every lane change straight to staff and owners.
One product, three people at the door
Guest, driver and owner — each with the view they need
Guest · no app to install
- Receives a message with a private link to their ticket
- Requests the car before walking out
- Sees when it is being fetched and when it is ready
Guest messaging is built against the Meta WhatsApp Cloud API. It needs the venue's own WhatsApp Business credentials to run.
Driver · the next job, in a tap
- Sees open requests the moment they arrive
- Claims one — nobody else can then take it
- Found → ready → handed over, in three to five taps
One staff app, with the screen changing by role.
Owner · the whole operation, live
- Waiting, retrieving and ready lanes on one board
- Retrieval times and daily reports
- Damage incidents with photos and how they were resolved
Honest build status
What is built, and what is not
Go service covering tickets, dispatch, vehicles, staff, incidents, locations, events, notifications, reporting and analytics, on PostgreSQL and Redis.
The conditional update above, with tenant isolation and a transactional outbox.
A Next.js web app with the live lanes board and an app-less guest page reached by a private link.
A single Flutter app whose screens change with the member of staff's role.
Terraform for Cloud Run and Cloud SQL, Kubernetes manifests and Docker Compose exist. Nothing is running in production yet.
Razorpay subscription handling with signed webhooks is written. No subscription has been sold.
Today ValetBee validates and normalises the format of an Indian registration number that has been typed in. Reading a plate from a photo is planned and not built.
Where ValetBee stands: the platform is built and we are preparing a first pilot. It is not deployed at a customer site, it has no paying venues and no live guests, and we are not claiming any.
Get in touch
Interested in a first pilot?
Preetham Yerramshetty · ValetBee, a Foundational Creations product
hello@valetbee.app