monkGive each branch room to run.
Run each branch with the services it needs. Developers and coding agents can test in parallel, without taking turns on one staging stack.
Give parallel work a place to run.
Parallel code changes need parallel environments. Give each branch an application stack with explicit service, credential and data boundaries, then clean it up when the work is done.
feature / checkout
Its own configuration, credentials and test data.
feature / search
Its own configuration, credentials and test data.
Branch. Test. Clean up.
Choose the branch and its scope
Ask Monk for a Capsule for the branch. Decide which services belong in it, what can be shared and what must stay separate. Check provider support for every dependency.
Review data, secrets and costs
Provide the environment’s credentials and decide how to seed test data. Review the plan before creating resources. A preview should not inherit access to production just because it uses the same code.
Test, then clean up
Run the branch and verify its workflow. When the preview is no longer needed, review its teardown, including persistent data and any billable resources that must remain.
Separate resources. Deliberate data.
A separate environment does not automatically include a copy of production data. Supported resource types and cloud configuration affect what can be reproduced. Preview resources incur cloud costs; define ownership and cleanup before creating many branches.
Is this only a frontend preview?
A Capsule can include the application’s supporting services. The environment plan determines what is created or shared; inspect it rather than assuming every dependency is duplicated.
Will it copy my production database?
Do not assume it will. Decide on seed data, snapshots or a separate reviewed transfer. Keep credentials and sensitive production data out of test environments unless deliberately authorized.
How do I control the cost?
Review the resources before creation and plan teardown when the work ends. Independent environments can add both cloud resources and managed capacity. Confirm the applicable billing rules for your account.
Try it with your application.
Start from your repository. Review the resources and costs before you deploy.