# Deployment models and account boundaries

Canonical page: https://launchinyourcloud.com/guide/deployment-models/

[Guide](/guide/) › Deployment models and account boundaries



“Launch in your cloud” describes commercial or open‑source software deployed into the buyer's cloud account or application-platform project. Infrastructure clouds provide an account, subscription, project or tenancy; application platforms such as Railway manage the underlying infrastructure while you operate the application in your project. Confirm the account boundary, data access and operational ownership that your organization requires.


The selected deployment may use a customer cloud account, a customer VPS, or a customer project on an application platform. A platform project does not give the customer control of the underlying cloud account. A vendor or open-source project supplies the application and upgrades. Support may be commercial or community-based; vendors may operate it remotely through access the customer grants.




- Customer account: The cloud account, subscription or project the organization owns and pays for.


- Data plane: The parts of the software that process and store data. In the customer environment for the deployment options covered here; review metadata and telemetry separately.


- Control plane: Management functions — provisioning, upgrades, monitoring. In the customer account, or hosted by the vendor.


- BYOC: “Bring your own cloud”: commonly a vendor-managed data plane in the customer environment. Terminology varies; check the actual operating model.





[Read the focused comparison of SaaS, self-hosted and BYOC](/questions/saas-self-hosted-byoc/).



## Compared with other delivery models



Aspect | Vendor‑hosted SaaS | DIY self‑hosted | Launch in your cloud | 



Where data lives | Vendor environment; check connected services | Your selected environment; check connected services | Documented customer cloud account, VPS or platform workspace; check connected services | 


Packaging & upgrades | Vendor | Your team | Vendor or project supplies the package; customer, vendor or partner operates it as documented | 


Infrastructure bill | Usually included in the service price; check extras | Separate from software and operating costs | Separate infrastructure and software charges; commitment eligibility is offer- and agreement-specific | 


Security review | The service, its integrations and your configuration | Your installation and its dependencies | The package, delegated access and selected service’s controls | 


Network integration | Public or private endpoints | Anything you build | Private connectivity where supported | 











## Benefits



### Data residency and sovereignty


You can choose the deployment region and account boundary. Verify backup locations, support access and outbound data flows against your requirements.



### Apply the available security controls


Review the identity, encryption, logging, network and policy controls available for the selected service. An application-platform project does not provide all the controls of an underlying infrastructure account.



### Cloud commitments


Eligible infrastructure spend or marketplace purchases may count toward cloud commitments. Confirm eligibility, exclusions and commercial terms with your provider.



### Private integration


Where supported, the software can reach your databases, queues and identity provider over private networking.



### Cost visibility


Resource usage is visible, taggable and sizeable in your own billing tools.



### Data portability


If you change vendors, the data is already in your account, which reduces exit effort.




## Trade‑offs


More responsibility moves to the customer: operating infrastructure, applying upgrades, paying for cloud resources and any license or support fees, and reviewing the permissions the software needs. See [Pitfalls & mitigations](/guide/#pitfalls).





## 1. Deployment models


Listings distinguish customer-operated, vendor or partner-operated, and shared operations. Some customer-operated deployments use an external vendor control plane; connected management does not establish a vendor-operated application service. Marketplace is a purchasing and delivery channel, not a guarantee that software runs in your account.



Model | Who operates it | Vendor access | Typical delivery | 



Customer-operated | Customer | Confirm standing and support access | IaC template, Helm chart, image | 


Vendor-operated BYOC | Vendor or service partner, in a customer environment | Scoped identity, role or agent | Vendor console + cross‑account role | 


Shared operations | Customer and vendor divide responsibilities | External management plane or delegated access; inspect each task | Customer resources connected to a vendor service | 


Marketplace delivery | Either | Depends on listing | Cloud marketplace, billed on cloud invoice | 











### Infrastructure: serverless, servers or hybrid


Infrastructure and operating responsibility are separate choices. A customer-operated application can use serverless functions, and a vendor-managed BYOC service can run on servers.



- Serverless: Event-driven functions and managed services, without a persistent application-server deployment.

- Servers / containers: Application servers, virtual machines, long-running containers or Kubernetes workloads.

- Hybrid: A serverless core combined with server, container or provisioned search workloads.

- Not specified: The reviewed documentation does not establish the runtime topology.



Listings can show multiple documented configuration options. Managed container services may be marketed as serverless; this directory distinguishes their application runtime from event-driven functions. Check the listing notes and selected modules.


Directory inclusion requires a documented deployment path on at least one named cloud provider or application platform. Products with only generic self-hosting documentation remain research candidates until a provider-specific path is confirmed. Check the listed edition, technical requirements and support scope; one documented path does not establish support on every cloud.




### Licensing models


The licensing filter describes the edition or service listed. It is separate from deployment location, infrastructure and whether support costs money.



- Open Source / Open Core: Software with an open-source edition or foundation. Some offerings add separately licensed proprietary or restricted features. Check each listing’s edition and license details; paid support alone does not imply restricted feature code.

- Commercial Only: The listed commercial edition or service is proprietary, even if the vendor also offers a separate open-source product.

- Source Available: Code is visible, but core terms include use, redistribution or branding restrictions beyond an open-source license.

- Not specified: The reviewed evidence does not support a more precise classification.



These directory classifications summarize the selected scope; the actual license and edition terms govern use. See the [Open Source Definition](https://opensource.org/osd) and the vendor sources on each listing. Features, embedding rights and enterprise components may have separate terms.



### AI hosting has several layers


Hosting an AI interface, workflow builder or observability server does not automatically host its models. Check inference endpoints, embeddings, vector storage, connectors and trace destinations separately. Locally served models and external APIs have different data flows and licensing requirements.




[Complete guide](/guide/) · [Download evaluation templates](/guide/toolkit/)



## Related questions

- [What does “launch in your cloud” mean?](https://launchinyourcloud.com/questions/launch-in-your-cloud/)
- [What is BYOC (bring your own cloud)?](https://launchinyourcloud.com/questions/byoc/)
- [What’s the difference between SaaS, self-hosted and BYOC?](https://launchinyourcloud.com/questions/saas-self-hosted-byoc/)
- [What is a control plane vs a data plane?](https://launchinyourcloud.com/questions/control-plane-data-plane/)
- [Does buying from a cloud marketplace mean the software runs in my account?](https://launchinyourcloud.com/questions/marketplace-account-boundary/)
- [Is serverless software different to operate than container-based software?](https://launchinyourcloud.com/questions/serverless-versus-containers/)
- [What’s the difference between open source, open core and source-available?](https://launchinyourcloud.com/questions/software-licenses/)
- [How do I check whether vendor-operated BYOC fits our security model?](https://launchinyourcloud.com/questions/vendor-operated-byoc/)
- [Can my team run self-hosted software without Kubernetes expertise?](https://launchinyourcloud.com/questions/without-kubernetes/)

