Samyojak is built by Yarsa Himalaya, in Pokhara. It comes out of a check-in system written for a single property, which did the job well enough that other hotels asked for it — and which could not be given to them, because everything about that hotel was baked into the software. Adding a second hotel meant a second copy of the whole thing.

So this is the same idea rebuilt as a service. A hotel is a row in a database, not a deployment. What carried over is the part that cost something to learn: how availability actually works when a booking holds a room type and a check-in holds a room; that a stay can be zero nights; that a bill can be in two currencies; that a register must be correctable without being editable.

What did not carry over is the shape. One shared realtime document that nobody had to authenticate for, one hard-coded password, and deploying by pulling from git on the server — those are the four things this version exists in order not to repeat.

संयोजक is the one that joins things together. The name is about the seam between the guest’s phone, the front desk, and the property management system the hotel already runs.