{"kind":"guide","markdown":"# Adopting launch-in-your-cloud software\n\nCanonical page: https://launchinyourcloud.com/guide/\n\n\nGuide › Model, methodology \u0026 pitfalls\n\n\n\n[Start with 50 customer-cloud questions and answers](/questions/), from deployment models and vendor evaluation to security, costs and finding software.\n\n\nWhat the model is, then a methodology for platform, security and procurement teams evaluating software that deploys into their own cloud accounts, followed by the problems that most often arise.\n\n\n\n[Deployment models](/guide/deployment-models/) · [Vendor evaluation](/guide/vendor-evaluation/) · [Download evaluation templates](/guide/toolkit/) · [Review methodology](/guide/review-methodology/)\n\n\n\n## Definition\n\n\n“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.\n\n\nThe 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.\n\n\n\n\n- Customer account: The cloud account, subscription or project the organization owns and pays for.\n\n\n- 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.\n\n\n- Control plane: Management functions — provisioning, upgrades, monitoring. In the customer account, or hosted by the vendor.\n\n\n- BYOC: “Bring your own cloud”: commonly a vendor-managed data plane in the customer environment. Terminology varies; check the actual operating model.\n\n\n\n\n\n\n## Compared with other delivery models\n\n\n\nAspect | Vendor‑hosted SaaS | DIY self‑hosted | Launch in your cloud | \n\n\n\nWhere data lives | Vendor infrastructure | Your infrastructure | Your cloud account | \n\n\nPackaging \u0026 upgrades | Vendor | Your team | Vendor or project ships, you apply or approve | \n\n\nInfrastructure bill | Bundled | Yours | Yours; may count toward cloud commitments | \n\n\nSecurity review | The vendor as a whole | Your build | The package, within your controls | \n\n\nNetwork integration | Public or private endpoints | Anything you build | Private connectivity where supported | \n\n\n\n\n\n\n\n\n\n\n\n## Benefits\n\n\n\n### Data residency and sovereignty\n\n\nYou can choose the deployment region and account boundary. Verify backup locations, support access and outbound data flows against your requirements.\n\n\n\n### Existing security controls apply\n\n\nThe software runs under your IAM policies, encryption keys, logging and guardrails.\n\n\n\n### Cloud commitments\n\n\nEligible infrastructure spend or marketplace purchases may count toward cloud commitments. Confirm eligibility, exclusions and commercial terms with your provider.\n\n\n\n### Private integration\n\n\nWhere supported, the software can reach your databases, queues and identity provider over private networking.\n\n\n\n### Cost visibility\n\n\nResource usage is visible, taggable and sizeable in your own billing tools.\n\n\n\n### Data portability\n\n\nIf you change vendors, the data is already in your account, which reduces exit effort.\n\n\n\n\n## Trade‑offs\n\n\nMore 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 \u0026 mitigations](#pitfalls).\n\n\n\n\n\n## 1. Deployment models\n\n\nListings 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.\n\n\n\nModel | Who operates it | Vendor access | Typical delivery | \n\n\n\nCustomer-operated | Customer | Confirm standing and support access | IaC template, Helm chart, image | \n\n\nVendor-operated BYOC | Vendor or service partner, in a customer environment | Scoped identity, role or agent | Vendor console + cross‑account role | \n\n\nShared operations | Customer and vendor divide responsibilities | External management plane or delegated access; inspect each task | Customer resources connected to a vendor service | \n\n\nMarketplace delivery | Either | Depends on listing | Cloud marketplace, billed on cloud invoice | \n\n\n\n\n\n\n\n\n\n\n\n### Infrastructure: serverless, servers or hybrid\n\n\nInfrastructure and operating responsibility are separate choices. A customer-operated application can use serverless functions, and a vendor-managed BYOC service can run on servers.\n\n\n\n- Serverless: Event-driven functions and managed services, without a persistent application-server deployment.\n\n- Servers / containers: Application servers, virtual machines, long-running containers or Kubernetes workloads.\n\n- Hybrid: A serverless core combined with server, container or provisioned search workloads.\n\n- Not specified: The reviewed documentation does not establish the runtime topology.\n\n\n\nListings 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.\n\n\nDirectory 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.\n\n\n\n\n### Licensing models\n\n\nThe licensing filter describes the edition or service listed. It is separate from deployment location, infrastructure and whether support costs money.\n\n\n\n- 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.\n\n- Commercial Only: The listed commercial edition or service is proprietary, even if the vendor also offers a separate open-source product.\n\n- Source Available: Code is visible, but core terms include use, redistribution or branding restrictions beyond an open-source license.\n\n- Not specified: The reviewed evidence does not support a more precise classification.\n\n\n\nThese 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.\n\n\n\n### AI hosting has several layers\n\n\nHosting 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.\n\n\n\n\n## 2. Evaluating a vendor\n\n\nQuestions to answer before a trial. Well‑documented products answer most of them publicly.\n\n\n\n\n- Which permissions do the installer and the running software need, and why?\n\n- Does any data, metadata or telemetry leave the account? Can it be disabled?\n\n- Which regions, services and instance types are required or supported?\n\n- How are upgrades delivered, tested and rolled back?\n\n- What is the expected infrastructure cost at your scale?\n\n- What continues to work if the license lapses or the vendor ceases trading?\n\n\n\n\n\n## 3. Launch methodology\n\n\n\n### 3.1 Prepare a dedicated account\n\n\nUse a separate account, subscription or project per application and environment. Apply landing‑zone guardrails, budgets, cost‑allocation tags and baseline logging before installing anything.\n\n\n\n### 3.2 Scope identity and access\n\n\nUse a dedicated deployment identity with the minimum required permissions and provider-appropriate guardrails. If the vendor needs access, give it a separate, time‑bound, logged role rather than shared credentials.\n\n\n\n### 3.3 Design the network\n\n\nDecide what is private, what is exposed, and how the software reaches your identity provider, data sources and the vendor's update endpoints. Prefer private endpoints and explicit egress rules.\n\n\n\n### 3.4 Deploy as infrastructure‑as‑code\n\n\nInstall from the vendor's reviewed CloudFormation, Bicep/ARM, Terraform, Helm or marketplace package. See [cloud-specific deployment guidance](/clouds/) for the documented providers and application platforms. Keep parameters in version control and deploy through your pipeline.\n\n\n\n### 3.5 Observability and backups\n\n\nRoute logs, metrics and alerts into existing tooling. Enable backups and point‑in‑time recovery, and test a restore.\n\n\n\n### 3.6 Upgrade cadence\n\n\nSubscribe to release notes, stage upgrades in a non‑production account, and set a deadline for applying security fixes.\n\n\n\n### 3.7 Exit plan\n\n\nDocument how to remove the software while keeping the data, in which formats, and what happens to running workloads if the license ends.\n\n\n\n\n## 4. Shared responsibility\n\n\nA typical split for the “fully in your account” model. Confirm the actual split with each vendor and attach it to the contract.\n\n\n\nArea | Customer | Vendor | \n\n\n\nAccount, IAM, keys | Owns | Documents requirements | \n\n\nApplication code \u0026 security fixes | Applies | Builds and ships | \n\n\nSizing \u0026 infrastructure cost | Owns | Recommends | \n\n\nData, backups, retention | Owns | Provides tooling | \n\n\nIncident response | Leads | Supports per SLA | \n\n\n\n\n\n\n\n\n\n\n\n## 5. Pitfalls \u0026 mitigations\n\n\n\nPitfall | What happens | Mitigation | \n\n\n\nOver‑broad permissions | Templates request administrator or wildcard access. | Require documented permissions, cloud-specific access guardrails, and reviewed audit logs. | \n\n\nUnclear responsibility | Nobody owns patching, on‑call or key rotation. | Agree a responsibility matrix (section 4) with named owners and response times. | \n\n\nUpgrade drift | Installs fall many versions behind and become hard to support. | Automate upgrades through the pipeline; agree a maximum version lag. | \n\n\nUnexpected infrastructure cost | Default sizing, idle environments or data transfer inflate the bill. | Request a cost model at your scale; set budgets and alerts; tag from day one. | \n\n\nUndisclosed data egress | Telemetry or licence checks send more than expected. | Restrict egress to documented endpoints and inspect traffic during the trial. | \n\n\nSkills gap | The team that bought the software cannot operate it. | Prefer managed cloud services in the stack, ask for runbooks, or choose a BYOC model. | \n\n\n\n\n\n\n\n\n\n\nNext: [browse the directory](/directory/) · See also: [where each model runs](/#where)\n\n\n\n## Further reading\n\nUse the official infrastructure documentation linked in the [cloud provider guide](/clouds/) and the product-specific sources on every directory entry. The responsibility matrix above is a planning example; agree actual ownership with your vendor.\n\nEditorial review: November 10, 2026.\n\n\n\n","questions":[],"relatedQuestions":[],"schemaVersion":1,"title":"Adopting launch-in-your-cloud software","url":"https://launchinyourcloud.com/guide/"}