Skip to main content
Picking a cloud usually means learning its console, its machine names and its pricing before you can run anything. With Monk you name the cloud and region in a request. Monk creates the cluster in your own account, after you review the plan and its estimated cost.

What you can do

Run in your own account

Clusters run on AWS, Google Cloud, Azure, DigitalOcean or Hetzner, billed to you by the provider. For trying a configuration first, Monk can also run everything on your own machine, where nothing is created in the cloud. Credentials go through a form in the local dashboard and are stored in your OS keychain, never in chat. How: Ask Monk; you enter credentials and approve the cluster plan in the local dashboard. See Choose a cloud and region and Credentials.

Estimate before you create

Monk estimates the hourly and monthly cost of a cluster from its node specification, as the cloud provider will charge it. Ask for estimates on two providers to compare. Your real bill depends on usage, data transfer and any managed services you add. How: Ask Monk. See Choose a cloud and region.

Use GPUs

Monk can list the GPU accelerators available for a provider, region and instance type, so you pick a real one. Today that means GCP n1-* instance types, plus instance types that have GPUs built in. How: Ask Monk. See Scale and resize.

Mix providers in one cluster

Nodes in a cluster join an encrypted WireGuard network, including nodes on different clouds. A service on Hetzner can reach a database on AWS without a VPN or public ports. To add nodes on another provider, ask for them and review the plan. How: Ask Monk; you approve the plan and its cost in the local dashboard. See Networking and domains and Clusters and clouds.

Move to another cloud

Monk has no one-step migration. You deploy the same app to a new cluster in the other cloud, check it, move the data, switch your DNS and then delete the old cluster. Each step is reviewed, and both clusters cost money until you remove one. Monk does not copy data between clouds, and switching DNS is yours to do. How: Ask Monk, step by step; you approve each plan in the local dashboard. Deleting the old cluster asks you to type its name. See Move to another cloud.

Try it

Good to know

  • Some options differ by cloud. AWS and GCP need an availability zone, and disk size can’t be set on DigitalOcean.
  • Managed services such as RDS belong to one cloud. A move plan shows what replaces them.
  • Nodes get public IP addresses. NAT gateways and private subnets aren’t supported.

Choose a cloud and region

Compare estimates and pick where to run

Move to another cloud

The reviewed sequence, step by step

Credentials

What each cloud needs

Clusters and clouds

Nodes, tags, GPUs and the registry