Adopting launch‑in‑your‑cloud software

Start with 50 customer-cloud questions and answers, from deployment models and vendor evaluation to security, costs and finding software.

What 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.

Deployment models · Vendor evaluation · Download evaluation templates · Review methodology

Definition

“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.

Compared with other delivery models

AspectVendor‑hosted SaaSDIY self‑hostedLaunch in your cloud
Where data livesVendor infrastructureYour infrastructureYour cloud account
Packaging & upgradesVendorYour teamVendor or project ships, you apply or approve
Infrastructure billBundledYoursYours; may count toward cloud commitments
Security reviewThe vendor as a wholeYour buildThe package, within your controls
Network integrationPublic or private endpointsAnything you buildPrivate 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.

Existing security controls apply

The software runs under your IAM policies, encryption keys, logging and guardrails.

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.

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.

ModelWho operates itVendor accessTypical delivery
Customer-operatedCustomerConfirm standing and support accessIaC template, Helm chart, image
Vendor-operated BYOCVendor or service partner, in a customer environmentScoped identity, role or agentVendor console + cross‑account role
Shared operationsCustomer and vendor divide responsibilitiesExternal management plane or delegated access; inspect each taskCustomer resources connected to a vendor service
Marketplace deliveryEitherDepends on listingCloud 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 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.

2. Evaluating a vendor

Questions to answer before a trial. Well‑documented products answer most of them publicly.

  1. Which permissions do the installer and the running software need, and why?
  2. Does any data, metadata or telemetry leave the account? Can it be disabled?
  3. Which regions, services and instance types are required or supported?
  4. How are upgrades delivered, tested and rolled back?
  5. What is the expected infrastructure cost at your scale?
  6. What continues to work if the license lapses or the vendor ceases trading?

3. Launch methodology

3.1 Prepare a dedicated account

Use a separate account, subscription or project per application and environment. Apply landing‑zone guardrails, budgets, cost‑allocation tags and baseline logging before installing anything.

3.2 Scope identity and access

Use 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.

3.3 Design the network

Decide 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.

3.4 Deploy as infrastructure‑as‑code

Install from the vendor's reviewed CloudFormation, Bicep/ARM, Terraform, Helm or marketplace package. See cloud-specific deployment guidance for the documented providers and application platforms. Keep parameters in version control and deploy through your pipeline.

3.5 Observability and backups

Route logs, metrics and alerts into existing tooling. Enable backups and point‑in‑time recovery, and test a restore.

3.6 Upgrade cadence

Subscribe to release notes, stage upgrades in a non‑production account, and set a deadline for applying security fixes.

3.7 Exit plan

Document how to remove the software while keeping the data, in which formats, and what happens to running workloads if the license ends.

4. Shared responsibility

A typical split for the “fully in your account” model. Confirm the actual split with each vendor and attach it to the contract.

AreaCustomerVendor
Account, IAM, keysOwnsDocuments requirements
Application code & security fixesAppliesBuilds and ships
Sizing & infrastructure costOwnsRecommends
Data, backups, retentionOwnsProvides tooling
Incident responseLeadsSupports per SLA

5. Pitfalls & mitigations

PitfallWhat happensMitigation
Over‑broad permissionsTemplates request administrator or wildcard access.Require documented permissions, cloud-specific access guardrails, and reviewed audit logs.
Unclear responsibilityNobody owns patching, on‑call or key rotation.Agree a responsibility matrix (section 4) with named owners and response times.
Upgrade driftInstalls fall many versions behind and become hard to support.Automate upgrades through the pipeline; agree a maximum version lag.
Unexpected infrastructure costDefault sizing, idle environments or data transfer inflate the bill.Request a cost model at your scale; set budgets and alerts; tag from day one.
Undisclosed data egressTelemetry or licence checks send more than expected.Restrict egress to documented endpoints and inspect traffic during the trial.
Skills gapThe team that bought the software cannot operate it.Prefer managed cloud services in the stack, ask for runbooks, or choose a BYOC model.

Next: browse the directory · See also: where each model runs

Further reading

Use the official infrastructure documentation linked in the cloud provider guide and the product-specific sources on every directory entry. The responsibility matrix above is a planning example; agree actual ownership with your vendor.

Editorial review: November 10, 2026.