Kobas is hospitality management software as a service (SaaS). This means we aim to provide a continuous service that’s always available and is constantly improving. By and large the vast majority of our improvements are either small changes or brand new features, but it’s inevitable that sometimes we will need to make changes to our customers’ workflow.
We therefore strive to provide continuous delivery of bug fixes and small improvements, and we bundle together any workflow changes into more formal releases that carry advanced warning.
No one wants to use buggy software. Robustness and stability are very important to the value provided by the Kobas service, so we take a number of steps to minimise the issues our customers encounter. We automatically unit test our code every time we change anything, and additionally at random intervals. All our services are automatically monitored and our engineers are alerted any time even the slightest discrepancy is noted, whether night or day.
We also recognise that while the back of house “Cloud” service is important, Kobas EPoS is mission critical and used in high pressure environments, and that unexpected changes there can be especially painful. We therefore run separate schedules for these two services.
Typically we will update customer EPoS installations monthly, usually on a Monday. We try to avoid updates in December as we know everyone is exceptionally busy.
We keep a Change Log of all EPoS changes.
Our Cloud offering covers a vast array of web applications, from customer loyalty, ticketing and reservations handling, through our APIs to the main back of house portal. As such we will typically perform around 40 minor patches a month across all these properties, and we aim for one major update a month, preceded by an email alert and a blog article detailing the advantages of the forthcoming release.
We keep a Change Log of all major Kobas Cloud changes.