Skip to main content
Reviewing a change is easier when you can open it running. Keeping staging and production apart matters just as much. Monk gives you named environments to keep stages apart, and preview environments, called capsules, to review changes. Each branch gets its own copy of the app, created and removed by GitHub Actions.

​
What you can do

​
Deploy to named environments

A project can have environments such as dev, staging and production. Each is linked to a cluster, and several can share one. The environment decides which cluster receives the deploy. Secrets can be scoped to a project or an environment, so staging and production get different values. How: Ask Monk. You approve the deploy in the local dashboard. See Environments and previews.

​
Get a preview environment per branch

Monk writes a GitHub Actions workflow that deploys each branch you push and removes the environment when its pull request closes. Each capsule can run on its own new cluster, or on a pool of nodes in a cluster you already have. Everything inside a capsule’s cluster is its own, and your coding agent gives per-branch names to anything created outside it, such as a managed database. How: Ask Monk. You approve the plan in the local dashboard. The repository must be on GitHub. See Preview environments.

​
Control what previews cost

A schedule sets when previews are up, for example weekdays from 8 to 19 in your timezone. One schedule covers the project, and a single preview can override it. How: Ask Monk, or in the web dashboard. You approve schedule changes in the local dashboard. See Manage preview environments.

​
Give previews their own secrets

Update the secrets that previews use. Values go through the local dashboard like any other secret. How: Ask Monk, with the values entered in the local dashboard. See Manage preview environments.

​
See every preview in one place

Previews are listed under a project’s Previews tab, with the branch, pull request, schedule and last deploy. You can also ask Monk to list them. How: In the web dashboard, or ask Monk. See Manage preview environments.

​
Try it

​
Good to know

  • Previews need the repository on GitHub, a project with a MANIFEST in an organization, and the Pro plan or above.
  • Production data is not copied into previews. A new environment starts empty, and anything your templates create outside the cluster needs a per-branch name.
  • A preview costs money while it runs. A cluster per branch costs more than a shared pool.
  • main, master and the branch you set up from are excluded by default.

Preview environments

Set up capsules step by step

Capsules

Modes, lifecycle, schedules and secrets

CI/CD

Deploy to one fixed cluster on every push