monkChoose what you
want to operate.
These tools solve different parts of the job. Start with where the app runs, what holds its state and who handles the next change.
Your coding agent alone
A persistent application model and controlled operations, beyond one conversation.
What keeps operating when the conversation ends?
Terraform
Infrastructure as code and the work of running the application.
Who connects infrastructure changes to the running application?
Kubernetes
The runtime platform and the services around it.
How much of the application platform do you want to assemble?
Deployment platforms
Hosted infrastructure or an application in your own cloud account.
Whose cloud account should the application run in?
A useful comparison
starts with your app.
Use the same repository, dependencies and acceptance test. Compare the complete workflow, including the parts your team still owns.
Deploy the whole system
Include the database, workers, storage and service connections. Check the app’s real workflow, beyond loading its homepage.
Make a second change
Open a fresh agent session. Update one service, inspect what will change and verify the rest of the application still works.
Account for operating it
Include infrastructure, platform fees, recovery, access control and the work needed to move data or leave the system.
Already have a platform
that works?
Evaluate Monk on a separate environment. Your existing tools may already cover the job well; the question is which work Monk removes for your team.
An evaluation path for ops teamsTry it with your application.
Start from your repository. Review the resources and costs before you deploy.