On-premises deployment installs software on servers the organization owns and operates, retaining control over infrastructure, data location, and update timing.
The organization bears responsibility for security, availability, and maintenance.
Alternative Names:
On-Prem, Self-Hosted Deployment
Why it Matters?
Control is the argument for on-premises and it comes with the burden of actually exercising it, since the organization becomes responsible for patching, backup, monitoring, and physical security. Many firms maintaining on-premises systems achieve worse security than a competent cloud provider delivers, because the resources required are substantial. The legitimate cases are regulatory requirements and client mandates rather than a general preference for control.
Frequently Confused with
Related terms
Frequently asked questions
When is on-premises deployment justified?
What is the practical risk?
