> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/cloud-for-dpi/chapter-1/separate-the-three-decisions.md). # Separate the three decisions Every hosting decision has three connected dimensions: where a workload runs, how much of the stack is managed, and who does the work. The permit service remains a concrete example, but the distinction applies to any workload under review. ## Where the service runs ### Owned, collocated, or managed hosting The authority may retain infrastructure it operates, place it in a colocation facility, or use managed hosting. These routes can fit a stable service when the authority needs a defined environment and can sustain the necessary hardware, patching, recovery, staffing, and contract oversight. They do not automatically provide more control. An old environment with one specialist operator can be harder to recover or change than a well-governed external service. ### Public cloud A public cloud uses provider-operated shared infrastructure and usually offers a broad range of computing and managed services. For the permit service, it may make adjustable capacity, managed databases, or shared monitoring easier to obtain. The authority still has to test access, records, cost controls, support, recovery, contracts, and exit against the service's actual requirements. ### Private cloud A private cloud is dedicated to one organization or a defined group. It may give the authority more direct control over the environment and its operating procedures. It also needs sustained investment in design, patching, monitoring, recovery, and skilled operation. A private placement is not automatically secure, recoverable, or sovereign. ### Hybrid cloud A hybrid arrangement combines environments. The permit interface might use a managed delivery platform while a registry remains in an existing environment, or it may do so temporarily while an unsupported component is replaced. Hybrid is a combination, not a separate place where a workload runs. It adds boundaries that identity, network, logging, monitoring, backup, incident response, and data-flow rules must cross. ### Multi-cloud Multi-cloud also describes a combination, in this case the use of more than one cloud provider. The authority might choose it for distinct capabilities or for deliberate diversification. It is not automatically resilience, portability, or sovereignty. For the permit service, a second provider helps recovery only if data, identity, capacity, ownership, and operating procedures allow the service to be restored or failed over there and people have exercised that route. ## How much of the stack is managed ### Infrastructure as a Service (IaaS) IaaS supplies basic virtual computing capabilities such as virtual machines, compute, storage, and networks. If the permit service uses IaaS, the authority or its partner still manages much of the operating system, application, configuration, identity integration, backups, monitoring, and restoration. ### Platform as a Service (PaaS) PaaS supplies managed runtimes, databases, integration components, development platforms, or container services. It can reduce work on infrastructure layers, while making the provider's interfaces, deployment method, data services, and operational tooling more consequential. ### Software as a Service (SaaS) SaaS supplies a complete application. It can fit a standard function, but the authority still has to govern users, configuration, records, accessibility, identity, audit evidence, continuity, and export. ## Who operates it The authority may operate the permit service itself, use a managed partner for defined tasks, outsource much of the work, or combine these arrangements. Self-operation can preserve hands-on capability but requires sustained people, routines, and funding. A managed partner may provide specialist monitoring, patching, backup operations, security operations, or platform administration. Outsourcing can reduce internal work for a standard service. Each model still needs public roles that can define the service, direct recovery, interpret evidence, and supervise what the authority remains answerable for. ![Decision framework for a public-service workload. Three choices run from left to right: placement or environment, where it runs, with owned or colocated or managed hosting, public cloud, and private cloud; service layer, what the provider manages, with IaaS, PaaS, and SaaS; and operating model, who performs the work, with authority, managed partner, outsourced, and mixed. Hybrid and multi-cloud are combination patterns. A band across all three reads: public accountability and digital sovereignty, lawful control, real choice, technology visibility, retained competence. The footer says to test recovery, evidence, data export, supplier dependency, and exit across the complete arrangement.](https://1406653965-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkZFMZ3jCMUwHtTN0sL4J%2Fuploads%2Fgit-blob-5f7d487d06c7f04bb499c4e9f6dfa3943bdc8d80%2Ffinal.png?alt=media) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://experience-digital-transform.gitbook.io/experience-digital-transformation/cloud-for-dpi/chapter-1/separate-the-three-decisions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.