AlgoRandevu — duration and resource defined in the product, still being built
Our own product, still being built — we describe it as work in progress, not a finished installation. Rather than baking the length of a booking, the resource it occupies and how closely bookings follow one another into a single trade, we keep all three definable inside the product, so a change in the rule is a change in a setting. A booking can attach to a person, a room or a piece of equipment, which puts the calendar in the hands of whatever is actually scarce. The ground is the Laravel and Inertia setup familiar from the AlgoKlima and AlgoCar panels, with records in MySQL, cache in Redis and the interface in Tailwind.
Read the case study →