AlgoRandevu — we are building the back-to-back gap as a product setting
Our own product, under construction; we do not present it as a finished installation. How long an appointment runs, what gap follows it and what resource it holds are kept definable inside the product rather than baked into a sector. One business can remove the gap and put two jobs back to back while another leaves room between them, and both run inside the same product with no separate release. An appointment can hold a person, a room or equipment. We build it on the same Laravel and Inertia ground as AlgoKlima and AlgoCar: MySQL holds the records, Redis is the cache layer, Tailwind shapes the panel.
Read the case study →