Before you start
- Monk is installed and you are signed in. See Install.
- The repository is open in your coding agent.
- Credentials for the cloud you want to use: AWS, GCP, Azure, DigitalOcean or Hetzner. You can also deploy locally first.
Ask Monk
MANIFEST that are needed.
You can be specific from the start:
What you review
The plan opens in the local dashboard. It lists:- the services Monk will run and how they connect
- databases and other dependencies, and whether each is self-hosted or managed
- configuration and secrets that are missing
- the cloud, region and machine sizes, with an estimated cost
What you get
- A cluster in your cloud account running the app from source
- Services wired together, with connection settings injected
- A model of the running app that later requests (logs, scaling, CI/CD) build on
Moving over from the original
The new environment runs next to the old one, and both cost money while they run. When you are ready:- Data. Copy the data yourself, or ask Monk which backup and restore actions your database supports. See Back up and restore.
- Traffic. Point your domain at the new environment. See Custom domain.
- Retire the original with the tools of wherever it runs.

