Choose the environment you control.
Read this page as JSON or Markdown.
Cloud accounts, VPS servers and application-platform projects offer different controls. Choose a provider group, then check the application deployment boundary and operating responsibilities.
Cloud support belongs to a specific product and deployment option. A marketplace listing alone does not establish that its data plane runs in your account.
Infrastructure clouds and application platforms have different account boundaries. Railway, Render, Heroku, Fly.io and hosted Northflank let you operate the application in your own project on platform-managed infrastructure. Review the account boundary below when choosing a deployment.
Cloud infrastructure
Compute, storage and networking provisioned through a customer cloud account, subscription, project or tenancy. Providers may also offer application platforms; check the listed deployment path.
| Provider | Deployment boundary | Network | Access controls |
|---|---|---|---|
| AWS | AWS account | VPC | IAM roles and policies |
| Azure | Subscription and resource group | Virtual Network (VNet) | Microsoft Entra identities and Azure RBAC |
| Google Cloud | Google Cloud project | VPC network | IAM policies and service accounts |
| Oracle Cloud | Tenancy and compartment | Virtual Cloud Network (VCN) | OCI IAM policies and identities |
| Alibaba Cloud | Alibaba Cloud account and resource group | VPC | Resource Access Management (RAM) |
| DigitalOcean | DigitalOcean team/account and project | VPC and Cloud Firewalls; review public endpoints | Team roles, scoped API tokens and SSH keys |
| Hetzner | Hetzner account and cloud project | Cloud networks, public IPs and firewalls | Project access and server SSH keys |
| Ubicloud | Ubicloud account/project; managed service or a separately operated cloud | Private networking and controlled application exposure | Account/project access and Kubernetes credentials |
| Linode | Akamai Cloud account and Linode compute instances | Public interfaces, VPCs and Cloud Firewalls | Cloud account access and server SSH keys |
| Vultr | Vultr account and compute instances | Instance networks and firewall rules | Cloud account access and server SSH keys |
| IBM Cloud | IBM Cloud account and resource group | VPC, subnets and security groups | Cloud access controls and server SSH keys |
| Tencent Cloud | Tencent Cloud account, project and selected region | Virtual Private Cloud (VPC), subnets and security groups | Cloud Access Management (CAM) roles and instance SSH keys |
| Volcano Engine | Volcano Engine account and selected ECS region | Virtual Private Cloud (VPC), subnets, security groups and optional public EIP | Cloud account permissions, cross-service authorization and instance SSH key pairs |
| STACKIT | STACKIT organization and project | Project-scoped cluster and application networking; review ingress and service exposure | Project roles, service accounts and optional OIDC workload identity federation |
| Scaleway | Customer Scaleway account and project | Review public/private interfaces, stable addresses and security-group rules for the selected instance | Scope provisioning credentials to the project and review guest administrator/SSH access separately |
Amazon Web Services
- Account boundary
- AWS account
- Network
- VPC
- Identity & access
- IAM roles and policies
- Deployment tooling
- CloudFormation or Terraform; review stack changes and requested IAM permissions.
Official deployment documentation ↗ · Browse AWS software and evidence →
Guidance reviewed 2026-11-10. Validate region, service and product availability.
Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Provider boundary source ↗ · Checked 2026-11-20
Microsoft Azure
- Account boundary
- Subscription and resource group
- Network
- Virtual Network (VNet)
- Identity & access
- Microsoft Entra identities and Azure RBAC
- Deployment tooling
- Bicep/ARM templates or Terraform; review deployment scope and role assignments.
Official deployment documentation ↗ · Browse Azure software and evidence →
Guidance reviewed 2026-11-10. Validate region, service and product availability.
Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Provider boundary source ↗ · Checked 2026-11-20
Google Cloud
- Account boundary
- Google Cloud project
- Network
- VPC network
- Identity & access
- IAM policies and service accounts
- Deployment tooling
- Terraform, optionally using Infrastructure Manager for resource provisioning; deploy the application separately.
Official deployment documentation ↗ · Browse Google Cloud software and evidence →
Guidance reviewed 2026-11-10. Validate region, service and product availability.
Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Provider boundary source ↗ · Checked 2026-11-20
Oracle Cloud Infrastructure
- Account boundary
- Tenancy and compartment
- Network
- Virtual Cloud Network (VCN)
- Identity & access
- OCI IAM policies and identities
- Deployment tooling
- Terraform, optionally orchestrated through OCI Resource Manager stacks.
Official deployment documentation ↗ · Browse Oracle Cloud software and evidence →
Guidance reviewed 2026-11-10. Validate region, service and product availability.
Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Provider boundary source ↗ · Checked 2026-11-20
Alibaba Cloud
- Account boundary
- Alibaba Cloud account and resource group
- Network
- VPC
- Identity & access
- Resource Access Management (RAM)
- Deployment tooling
- Resource Orchestration Service (ROS) templates or Terraform; review the required RAM permissions.
Official deployment documentation ↗ · Browse Alibaba Cloud software and evidence →
Guidance reviewed 2026-11-10. Validate region, service and product availability.
Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Provider boundary source ↗ · Checked 2026-11-20
DigitalOcean
- Account boundary
- DigitalOcean team/account and project
- Network
- VPC and Cloud Firewalls; review public endpoints
- Identity & access
- Team roles, scoped API tokens and SSH keys
- Deployment tooling
- Provision Droplets or Kubernetes in your account; review the application image, storage, updates and firewall rules.
Official deployment documentation ↗ · Browse DigitalOcean software and evidence →
Guidance reviewed 2026-11-12. Validate region, service and product availability.
Droplets and managed Kubernetes use the customer infrastructure account. App Platform is a separate platform-workspace path and is identified per listing. Provider boundary source ↗ · Checked 2026-11-20
Hetzner Cloud
- Account boundary
- Hetzner account and cloud project
- Network
- Cloud networks, public IPs and firewalls
- Identity & access
- Project access and server SSH keys
- Deployment tooling
- Create a server with a supported OS and install the application; manage updates, storage and backups in the customer project.
Official deployment documentation ↗ · Browse Hetzner software and evidence →
Guidance reviewed 2026-11-12. Validate region, service and product availability.
Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Provider boundary source ↗ · Checked 2026-11-20
Ubicloud
- Account boundary
- Ubicloud account/project; managed service or a separately operated cloud
- Network
- Private networking and controlled application exposure
- Identity & access
- Account/project access and Kubernetes credentials
- Deployment tooling
- Deploy applications using customer Kubernetes and database resources; distinguish the managed service from operating Ubicloud on your own bare metal.
Official deployment documentation ↗ · Browse Ubicloud software and evidence →
Guidance reviewed 2026-11-12. Validate region, service and product availability.
The published Windmill path provisions managed Kubernetes and PostgreSQL in a customer Ubicloud project; it does not describe a customer-operated Ubicloud installation. Provider boundary source ↗ · Checked 2026-11-20
Akamai Cloud (Linode)
- Account boundary
- Akamai Cloud account and Linode compute instances
- Network
- Public interfaces, VPCs and Cloud Firewalls
- Identity & access
- Cloud account access and server SSH keys
- Deployment tooling
- Create a Linode compute instance and install the documented application; manage OS updates, persistent storage and recovery.
Official deployment documentation ↗ · Browse Linode software and evidence →
Guidance reviewed 2026-11-12. Validate region, service and product availability.
Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Provider boundary source ↗ · Checked 2026-11-20
Vultr
- Account boundary
- Vultr account and compute instances
- Network
- Instance networks and firewall rules
- Identity & access
- Cloud account access and server SSH keys
- Deployment tooling
- Provision compute through the console, API, CLI or Terraform, then install and operate the documented application.
Official deployment documentation ↗ · Browse Vultr software and evidence →
Guidance reviewed 2026-11-12. Validate region, service and product availability.
Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Provider boundary source ↗ · Checked 2026-11-20
IBM Cloud
- Account boundary
- IBM Cloud account and resource group
- Network
- VPC, subnets and security groups
- Identity & access
- Cloud access controls and server SSH keys
- Deployment tooling
- Provision virtual servers through the console, CLI, API or Terraform; obtain and configure the selected vendor private application package.
Official deployment documentation ↗ · Browse IBM Cloud software and evidence →
Guidance reviewed 2026-11-12. Validate region, service and product availability.
Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Provider boundary source ↗ · Checked 2026-11-20
Tencent Cloud
- Account boundary
- Tencent Cloud account, project and selected region
- Network
- Virtual Private Cloud (VPC), subnets and security groups
- Identity & access
- Cloud Access Management (CAM) roles and instance SSH keys
- Deployment tooling
- Provision a supported Cloud Virtual Machine (CVM) in your account, configure storage and network rules, then install the vendor-documented application stack. Confirm certified GPU/OS combinations and BYOL requirements for NVIDIA AI Enterprise.
Official deployment documentation ↗ · Browse Tencent Cloud software and evidence →
Guidance reviewed 2026-11-16. Validate region, service and product availability.
Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Provider boundary source ↗ · Checked 2026-11-20
ByteDance Volcano Engine
- Account boundary
- Volcano Engine account and selected ECS region
- Network
- Virtual Private Cloud (VPC), subnets, security groups and optional public EIP
- Identity & access
- Cloud account permissions, cross-service authorization and instance SSH key pairs
- Deployment tooling
- Create a customer Elastic Compute Service (ECS) instance, select its region, VPC, security group and SSH key, then install the documented application. NVIDIA AI Enterprise uses a standard-instance BYOL path with certified OS, driver and container-toolkit requirements.
Official deployment documentation ↗ · Browse Volcano Engine software and evidence →
Guidance reviewed 2026-11-16. Validate region, service and product availability.
Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Provider boundary source ↗ · Checked 2026-11-20
STACKIT
- Account boundary
- STACKIT organization and project
- Network
- Project-scoped cluster and application networking; review ingress and service exposure
- Identity & access
- Project roles, service accounts and optional OIDC workload identity federation
- Deployment tooling
- Use the documented vendor-managed customer-cloud deployment or a separately supported installation path. STACKIT Kubernetes Engine supplies managed Kubernetes; platform availability alone does not establish application support.
Official deployment documentation ↗ · Browse STACKIT software and evidence →
Guidance reviewed 2026-11-17. Validate region, service and product availability.
Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Provider boundary source ↗ · Checked 2026-11-20
Scaleway
- Account boundary
- Customer Scaleway account and project
- Network
- Review public/private interfaces, stable addresses and security-group rules for the selected instance
- Identity & access
- Scope provisioning credentials to the project and review guest administrator/SSH access separately
- Deployment tooling
- Use an application-specific installer on a compatible customer instance. The reviewed BigBlueButton 4.0 installer explicitly handles Scaleway NAT and requires the operator to configure the external firewall; a generic Ubuntu image alone does not establish support for other applications.
Official deployment documentation ↗ · Browse Scaleway software and evidence →
Guidance reviewed 2026-11-19. Validate region, service and product availability.
Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Provider boundary source ↗ · Checked 2026-11-20
VPS hosting
An application installed on a virtual server in the customer's hosting account. The host operates the physical infrastructure; application and guest-system responsibilities depend on the selected service.
| Provider | Deployment boundary | Network | Access controls |
|---|---|---|---|
| Hostinger | Hostinger account and VPS | Customer server networking, DNS and firewall rules | Cloud account access, server root/SSH access and application administrators |
| LumaDock | LumaDock account and VPS | Customer server networking, DNS and firewall rules | Cloud account access, server root/SSH access and application administrators |
Hostinger
- Account boundary
- Hostinger account and VPS
- Network
- Customer server networking, DNS and firewall rules
- Identity & access
- Cloud account access, server root/SSH access and application administrators
- Deployment tooling
- Provision the documented Cloudron VPS template in your account, complete domain and administrator setup, then install and operate the reviewed application package.
Official deployment documentation ↗ · Browse Hostinger software and evidence →
Guidance reviewed 2026-11-13. Validate region, service and product availability.
The documented route uses a customer VPS and application administrator; the hosting provider operates its physical infrastructure. Provider boundary source ↗ · Checked 2026-11-20
LumaDock
- Account boundary
- LumaDock account and VPS
- Network
- Customer server networking, DNS and firewall rules
- Identity & access
- Cloud account access, server root/SSH access and application administrators
- Deployment tooling
- Provision the documented Cloudron VPS template in your account, complete domain and administrator setup, then install and operate the reviewed application package.
Official deployment documentation ↗ · Browse LumaDock software and evidence →
Guidance reviewed 2026-11-13. Validate region, service and product availability.
The documented route uses a customer VPS and application administrator; the hosting provider operates its physical infrastructure. Provider boundary source ↗ · Checked 2026-11-20
Application platforms
An application deployed in a customer workspace or project on infrastructure operated by the platform. This does not establish ownership of an underlying cloud account.
| Provider | Deployment boundary | Network | Access controls |
|---|---|---|---|
| Railway | Railway workspace, project and environment; platform-managed infrastructure | Project/environment private networking with separately exposed public services | Workspace/project access and scoped deployment tokens |
| Northflank | Northflank team and project; hosted platform or a separately connected customer cluster | Private project services with explicitly exposed public ports | Team/project roles, API tokens and secret groups |
| Render | Render workspace, project and services; platform-managed infrastructure | Private services with separately exposed public endpoints | Workspace membership and deployment credentials |
| Heroku | Heroku account/team and application; platform-managed infrastructure | Application routing; network isolation depends on the selected plan | App/team access and configuration variables |
| Fly.io | Fly.io organization and app; platform-managed Machines | App networking and explicitly published services | Organization/app access, deployment tokens and secrets |
Railway
- Account boundary
- Railway workspace, project and environment; platform-managed infrastructure
- Network
- Project/environment private networking with separately exposed public services
- Identity & access
- Workspace/project access and scoped deployment tokens
- Deployment tooling
- Deploy application containers and data services into your project. Community templates require review of source images, credentials, volumes and release compatibility; they do not imply upstream vendor support.
Official deployment documentation ↗ · Browse Railway software and evidence →
Guidance reviewed 2026-11-12. Validate region, service and product availability.
Hosted application platform; a workspace is not a customer-owned underlying hyperscaler account. Provider boundary source ↗ · Checked 2026-11-20
Northflank
- Account boundary
- Northflank team and project; hosted platform or a separately connected customer cluster
- Network
- Private project services with explicitly exposed public ports
- Identity & access
- Team/project roles, API tokens and secret groups
- Deployment tooling
- Deploy builds, containers, jobs and database add-ons in a project. The hosted platform is separate from Northflank BYOC: confirm the underlying account, cluster ownership and operating agreement for that option.
Official deployment documentation ↗ · Browse Northflank software and evidence →
Guidance reviewed 2026-11-12. Validate region, service and product availability.
The published Northflank recipes use its hosted platform. Northflank also offers connected customer clusters; those require separate application-specific evidence. Provider boundary source ↗ · Checked 2026-11-20
Render
- Account boundary
- Render workspace, project and services; platform-managed infrastructure
- Network
- Private services with separately exposed public endpoints
- Identity & access
- Workspace membership and deployment credentials
- Deployment tooling
- Deploy application services and databases using a Blueprint or Docker/source build; configure persistent disks, secrets and recovery.
Official deployment documentation ↗ · Browse Render software and evidence →
Guidance reviewed 2026-11-12. Validate region, service and product availability.
Hosted application platform; a workspace is not a customer-owned underlying hyperscaler account. Provider boundary source ↗ · Checked 2026-11-20
Heroku
- Account boundary
- Heroku account/team and application; platform-managed infrastructure
- Network
- Application routing; network isolation depends on the selected plan
- Identity & access
- App/team access and configuration variables
- Deployment tooling
- Deploy with Git, containers or app templates; configure paid dynos, database add-ons and durable file storage.
Official deployment documentation ↗ · Browse Heroku software and evidence →
Guidance reviewed 2026-11-12. Validate region, service and product availability.
Hosted application platform; a workspace is not a customer-owned underlying hyperscaler account. Provider boundary source ↗ · Checked 2026-11-20
Fly.io
- Account boundary
- Fly.io organization and app; platform-managed Machines
- Network
- App networking and explicitly published services
- Identity & access
- Organization/app access, deployment tokens and secrets
- Deployment tooling
- Use flyctl and fly.toml to deploy the application and database; configure regions, volumes, secrets and recovery.
Official deployment documentation ↗ · Browse Fly.io software and evidence →
Guidance reviewed 2026-11-12. Validate region, service and product availability.
Hosted application platform; a workspace is not a customer-owned underlying hyperscaler account. Provider boundary source ↗ · Checked 2026-11-20
Before choosing a region
Check the application's supported regions, service quotas, backup destinations, identity integration and permitted support access. Cloud ownership alone does not determine data residency or remove your operational responsibilities.
Continue with the launch methodology.