Software Deployment Models

Enterprise and cloud deployment models

Different software deployment models satisfy the needs of different types of enterprise, with differing costs and value propositions. To make the right decision for your software product and its target audience, it's worth taking a quick look at the most popular traditional and cloud computing deployment models.

Hosted
Some software (ERP solutions, for instance) requires a server. It's often impractical to have a server in-house, so an enterprise may prefer a vendor or third party to run the software off their servers, usually hosted in secure remote data centers. The enterprise owns the software but then pays a monthly or annual fee to access the server, which also covers the cost of deployment, security, backups and server maintenance.

On-Premises ('On-Prem')
On-premises (or ‘on-prem’) software is directly installed and run on individual machines or local servers belonging to the customer, i.e. on physical hardware rather than remote hosting.

Typically, a license is required for each user or server, and license keys are either downloaded via the internet or activated with a license dongle. 

Perpetual or subscription license models are common, and customers are responsible for installing updates to ensure they’re running the latest version, which helps reduce exposure to  security issues. Updates are typically provided through paid maintenance plans.

Cloud deployment models

Cloud deployment is about creating a virtual environment that defines how servers are used and managed. The three most popular cloud deployment models are software as a service (SaaS), platform as a service (PaaS), and infrastructure as a service (IaaS).

Public Cloud

Software that is deployed in the public cloud is remotely owned and hosted by the software vendor. Typically, the enterprise pays for a cloud subscription license rather than owning the software outright – known as software as a service (SaaS) – mimicking popular cloud subscription models for applications like Salesforce.com, Adobe Creative Cloud and Microsoft Office 365.

Private Cloud

A private cloud deployment model involves using the same mix of tools as a public cloud offering, but hosted on-premise. An enterprise gains the flexibility to customize an app and tailor the software to meet their specific needs while having all the benefits of a packaged SaaS solution. In some cases, the vendor or service provider may manage the on-premise server remotely or provide ongoing maintenance and development.

Virtual Private Cloud

A virtual private cloud (or VPC) is a private cloud hosted in a public cloud. A VPC is typically used by an enterprise that needs flexible but secure access to cloud storage, to host websites, or to execute code. By isolating resources and ring-fencing them from a larger public cloud, VPCs get all the benefits of mainstream cloud infrastructure with the privacy and security of private cloud. VPCs often consist of subnets (a range of reserved IP addresses within a network for private use, hidden from public internet), VLAN (a virtual local area network where devices are connected without the internet, partitioning the public and private cloud), and VPNs (virtual private networks that use encryption to create a private network overlaid on top of a public network, scrambling traffic through routers and switches).

VPCs enable an enterprise to scale and add more resources on demand, as well as boosting the performance of cloud-hosted applications by taking the best of public cloud infrastructure.

Community Cloud

A community cloud operates in much the same ways as a private cloud, with one key difference: it consists of a multi-tenant architecture. That means organizations can form a community to share computing resources on public cloud infrastructure but with tightly controlled security and access.

Community clouds are hosted on third-party servers or a tenant data center, allowing resources to be pooled. This is particularly useful for 'sister' organizations in the same sector to be able to access databases and software applications that are in common use, but without public access. Security settings and applications must be the same across the group.

Costs involved in establishing and maintaining a community cloud are typically vastly below a private cloud, and organizations can share resources for best efficiency.

Learn more: 
Growing Cloud-Native Application Revenue with Enhanced Entitlement Management