Going with Supabase for auth — its free tier covers 5× the users Clerk’s does.
This keeps the stack lean: Supabase for authentication and Stripe for payments, with no extra provider costs at launch.
Saved 3 notes to memory
Lock the launch to before the 15th.
Locked in. That gives you nine working days, and the booking flow is the only piece still unfinished.
Saved 1 note to memory
What’s left in the booking flow?
Picking a time slot, the confirmation screen, and the reminder the day before.
15 or 30 minute slots?
Most salons book in 30-minute steps. 15 only makes the picker longer.
Draft the confirmation text
Booked: haircut with Dana, Friday at 14:30. Reply C to cancel.
How should the reminder go out?
By SMS the day before. It gets read, and the email stays as the receipt.
Can one booking hold two services?
Yes. Stack them back to back and send one confirmation.
What does the owner see first?
Today’s bookings in time order, with gaps highlighted so they can fill them.
Any risk in guest checkout?
No-shows. A card on file with a small hold covers most of it.
Why didn’t we go with Clerk?
Supabase’s free tier covers 5× the users Clerk’s does, so auth went to Supabase.
Memory
Booking app
Auth is Supabase: its free tier covers 5× the users Clerk’s does.today
Payments go through Stripe.today
No paid provider costs at launch.today
Launch is before the 15th.today
Pricing is $15 a month, annual billing only.4 days ago
Cancellation is free up to 24 hours before check-in.6 days ago
Room photos are capped at 8 per listing.26 days ago
Decisions and details that live only in this project. Edit or delete one from its row, or just say so in chat. Notes are stored on our servers and are not end-to-end encrypted.