Some History: Client-Server vs Cloud
Quickbase was a cloud platform ahead of its time when it was launched by Intuit in 2000. Multi-user business process database powered applications were not new of course, and many enterprises deployed products like Lotus Notes, Novell Groupwise or Microsoft Access to provide business applications to enterprise users. These products were hosted “on-prem” and delivered to users over private “behind the firewall” networks via thick Windows client applications in a client-server architecture.
Quickbase, on the other hand, has always been delivered from a multi-tenant architecture to an end users web browser over the Internet, a delivery model which has come to dominate IT services today.
In the client-server era, the main concerns from a security perspective were if the software could be configured securely and if it had been tested and patched for security bugs. Otherwise, the organization depended on its IT department to install, configure and manage the software, and hopefully that was being done well.
Because more of the tech stack is outsourced to a third-party, vendor risk management is more important to get right for a cloud service provider than it is for legacy hosted on-premises software. There is a greater responsibility placed on today’s vendor risk and related teams. Your job is to ensure your organization’s data is protected, your business processes are continuously available, and, in many cases, you remain compliant with relevant regulations which pertain to the types of data you store and process in a cloud service like Quickbase.
Additionally, client-server and on-premises hosted infrastructure are much more costly to maintain than outsourcing all that to a cloud service provider. By reducing costly overhead and enabling agility, cloud services like Quickbase have been successful.