Skip to main content
Monk runs your app in your own cloud account. It supports AWS, Google Cloud, Azure, DigitalOcean and Hetzner, and it can also run everything on your own machine.

​
Before you start

Get credentials for the cloud you want. Each page shows the permissions Monk needs: You don’t need to paste them anywhere yet. Monk asks when it needs them.

​
Ask Monk

Name the cloud and region in your request:
Ask which regions and machine types a cloud offers:
Compare estimates before you commit:
Need GPUs? Ask which accelerators are available:

​
What you review

  • Credentials. The first time you use a cloud, a credential form opens in the local dashboard. Enter or upload the values there, never in chat. They are stored in your OS keychain.
  • The plan. It shows the cloud, region, machine types, node count and an estimated monthly cost that includes Monk’s fee. Nothing is created until you approve.
Estimates come from the provider’s prices for the machines in the plan. Your real bill depends on usage, data transfer and any managed services you add.

​
What you get

A cluster in the chosen cloud and region, registered to your Monk account and visible in the web dashboard under Clusters. Later deploys to the same project go to this cluster unless you ask for another one.

​
Limits

  • To run parts of an app in different clouds or managed services, describe that when you ask for the plan, and check how the parts connect before you approve.
  • Some options differ by cloud. For example, AWS and GCP need an availability zone, and disk size can’t be set on DigitalOcean.

​
Next