On-Premise or Cloud-Based Permit Software - What's Better?

Though governments have tailed behind the private sector in their adoption of cloud software, according to a 2021 NASCIO survey, 88% of state CIO respondents noted plans to expedite cloud adoption across their operational domains, with 74% stating security as the biggest draw of a move to the cloud. Add to that the flexibility and cost savings of cloud-based permitting systems, and it becomes clear why they're the top choice for modern organizations.

Comparatively, on-premise systems don’t scale, aren’t agile, and require constant updates and maintenance. They simply don’t work long-term.

It’s better to be prepared with a cloud-based system that can be updated without a heavy lift from IT or system integrators. 

Here’s a closer look at how SaaS (software as a service) cloud solutions and on-premise systems compare:

	Cloud	On-Premise
Scalability	Infinitely scalable to meet as many users and departments as required.	Limited scalability. Increased hardware investment required to scale infrastructure.
Hosting	Everything - including data and applications - is hosted in the cloud by a third-party provider.	Installed on an organization’s on-premise servers making it vulnerable to network outages or other security issues.
Data Storage	Data resides with the third-party provider. It’s always available, backed up, and secure.	Data located within in-house servers and IT infrastructure. Data backup is the agency’s responsibility.
Security	Regarded as one of the most secure forms of application and data management, with providers required to adhere to many national security standards such as FedRAMP, MIST, SOC Type 2, and others. Learn more about government cloud security here.	Vulnerable to the level of security managed by IT for application, network, and organizational risk exposure, including additional costs.
Service Continuity	Offers protection against network outages, security breaches, and other unforeseen events. All you need is an internet connection to access your solution from anywhere.	Vulnerable to organizational security breaches and service outages.
Total Cost of Ownership	Lower total cost of ownership - users only pay for the resources they use.	Higher total cost of ownership: maintenance costs, hardware, power, staff time, and space.
Ability to Make Changes	Highly configurable systems require minimal to no customization for changes, integrations, or updates, and are infinitely scalable.	Heavily reliant on customization for any changes, integrations, or updates - not scalable without considerable work.
Demand on IT Resources	Most maintenance can be performed by department staff.	Demanding on IT staff to maintain the solution.
Licensing	Pay-as-you-go models: software-as-a-service models (SaaS).	Requires a software license that will eventually require additional costly infrastructure and major upgrades.