Cloud Fundamentals

Cloud Deployment Models: Public, Private, Hybrid and Community Clouds

Compare the four NIST cloud deployment models: public, private, hybrid and community clouds, with examples, trade-offs and how to choose one.

On this page
  1. The four NIST deployment models at a glance
  2. Public cloud
  3. Private cloud
  4. Hybrid cloud
  5. Community cloud
  6. Multi-cloud is not a fifth NIST model
  7. How to choose a deployment model
  8. Common misconceptions
  9. Frequently asked questions

A cloud deployment model describes where a cloud’s infrastructure is hosted, who owns and runs it, and who is allowed to use it. The US National Institute of Standards and Technology (NIST) defines four: public, private, community and hybrid. Multi-cloud is also widely used in industry, but it is not one of NIST’s four.

The four NIST deployment models at a glance

Model Who uses it Who owns and runs it Where it is hosted
Public Anyone who signs up, with many customers sharing the same infrastructure A third-party cloud provider The provider’s data centers
Private A single organization The organization, or a third party on its behalf On-premises or in a hosted facility
Community Several organizations with shared concerns, such as compliance or mission Member organizations, a third party, or both On or off premises
Hybrid An organization using two or more distinct infrastructures Mixed Mixed, usually private plus public

The sections below cover each model, then multi-cloud and how to choose.

Public cloud

A public cloud is run by a provider that offers its infrastructure over the internet to many customers. Each customer’s resources stay logically separate from everyone else’s. The main cloud providers include AWS, Microsoft Azure, Google Cloud, Oracle Cloud, IBM Cloud and Alibaba Cloud.

Public cloud infrastructure services, the IaaS offerings, are the most common example. You rent virtual machines, storage and networking on demand. Examples include Amazon EC2, Azure Virtual Machines and Google Compute Engine.

Strengths

  • Little or no upfront spending on hardware
  • Pay for what you use
  • Capacity can grow or shrink quickly as demand changes

Trade-offs

  • You cannot control the physical hardware or the facility
  • You depend on the provider’s security and availability, and you still configure your own resources
  • Cost can be higher than on-premises for steady, always-on workloads

Private cloud

A private cloud is provisioned for one organization. It can run in the organization’s own data center or be hosted by a third party. Common platforms for building one include VMware Cloud Foundation, the open-source OpenStack, Azure Local and Nutanix.

Virtualized servers alone do not make a private cloud. The NIST model also expects self-service provisioning, resource pooling and metered usage.

Strengths

  • Direct control over hardware, data location and configuration
  • Easier to tailor to specific regulatory or security rules

Trade-offs

  • Higher upfront cost and ongoing maintenance
  • Requires staff who can run the infrastructure
  • Capacity is limited to what has been bought and installed

A private cloud is not automatically more secure than a public one. Security depends on how it is configured and operated.

Hybrid cloud

A hybrid cloud combines two or more distinct cloud infrastructures that are linked so data and applications can move between them. Most often this means a private environment plus a public cloud.

The links are usually a site-to-site VPN or a dedicated connection, such as AWS Direct Connect, Azure ExpressRoute or Google Cloud Interconnect. Products such as AWS Outposts, Azure Arc and Google Distributed Cloud extend a provider’s services into an on-premises environment.

  Private infrastructure                    Public cloud
 +------------------------+                 +------------------------+
 | Core systems and data  |<--------------->| Overflow capacity      |
 +------------------------+                 +------------------------+
   Connected by a VPN or a dedicated link

Common hybrid patterns include:

  • Cloud bursting: a workload runs on private infrastructure and overflows to the public cloud when demand peaks.
  • Split by sensitivity: regulated data stays on-premises while less sensitive workloads run in the public cloud.
  • Phased migration: workloads move to the cloud one at a time instead of all at once.

Trade-offs: connecting, securing and managing two environments consistently is harder than running one.

Community cloud

A community cloud serves several organizations that share a common concern, such as a regulatory framework, a security requirement or a research mission. It can be run by the member organizations, by a third party, or by both, on or off premises.

Examples include government-focused cloud regions such as AWS GovCloud (US) and Azure Government, and research or healthcare consortia that pool infrastructure. The line between a community cloud and a public cloud with restricted access can blur. It depends on how the offering is governed, so check the provider’s terms before assuming a category.

Trade-off: members share costs and compliance work, but decisions about the cloud are shared too, which can slow change.

Multi-cloud is not a fifth NIST model

Multi-cloud means using two or more public cloud providers at the same time, often for different workloads. It is common because it can:

  • Let teams pick the best service from each provider
  • Reduce dependence on one vendor, which relates to vendor lock-in
  • Improve geographic reach or resilience

Multi-cloud and hybrid are different ideas. Hybrid mixes private or on-premises infrastructure with public cloud. Multi-cloud mixes public providers. An organization can use one, the other, or both. Running multi-cloud adds cost and effort in tooling, skills and integration.

How to choose a deployment model

There is no single best model. Teams usually weigh:

  • Data sensitivity and regulation: rules may dictate where data can be stored and who can access it.
  • Workload pattern: spiky demand suits public cloud, while steady, predictable demand may suit private hardware.
  • Existing investment: hardware, software licenses and contracts already in place.
  • Latency and location: where users are, and which regions are close to them.
  • Skills: whether the team can operate the chosen model well.
  • Budget shape: upfront capital spending versus ongoing usage costs.

Many organizations end up with a mix, and the right answer can change as their needs change.

Common misconceptions

  • Private cloud means on-premises. It can also be hosted by a third party.
  • Hybrid and multi-cloud are the same. Hybrid combines private and public. Multi-cloud combines public providers.
  • Private cloud is automatically more secure. Control helps, but configuration and operations decide the outcome.
  • Deployment models are the same as service models. Deployment models describe where and who. Service models such as IaaS, PaaS and SaaS describe what the provider delivers.

For the five essential characteristics that apply across all of these models, read the guide to key characteristics of cloud computing. For a broader introduction, see how cloud computing works.

Frequently asked questions

How many cloud deployment models are there?

NIST defines four: public, private, community and hybrid. Multi-cloud is also commonly discussed, but it is not in the NIST list.

What is the difference between hybrid and multi-cloud?

Hybrid combines private or on-premises infrastructure with public cloud. Multi-cloud uses two or more public cloud providers. An organization can be hybrid, multi-cloud, both or neither.

Which deployment model is cheapest?

Public cloud usually has the lowest upfront cost because there is no hardware to buy. A steady, always-on workload can still cost more in the cloud than on-premises, so the answer depends on the workload.

Is a private cloud more secure than a public cloud?

Not automatically. A private cloud gives more control over configuration and data location. Whether it is secure depends on how it is run. Under the shared responsibility model, the customer has security work to do whichever model it uses.

The complete guide to cloud fundamentals

How Cloud Computing Works (With Diagram)
Read the guide

Keep exploring

Guides from other topics

All topics →