monkWriting
Notes from building an operator.
What we are building, what broke, and the arguments underneath it. Engineering posts carry individual bylines; launches come from the team.
Monk: The Safe Way to Run MongoDB Atlas from Your Coding AgentToday we're introducing our MongoDB Atlas integration: provisioning, scaling, networking, backups and recovery from your coding agent, with Monk enforcing the controls that keep production safe.Monk Team · 3 min read
Monk knows the live state of everything - your application and your infrastructure, at every moment.Part 3 of 5: a gate is only as good as what it knows. "Don't restart the production database" means nothing unless the layer knows which database is production - and that knowledge is state.Monk Team · 2 min read
Monk isn't just an AI - and that's the point.Part 2 of 5: No amount of DevOps productivity is worth an AI deleting your production. We wouldn't give an agent direct access to our infrastructure, so we won't ask you to hand over yours. Monk sits between the agent and your infrastructure - a validation layer that runs on facts and logic, and can't hallucinate.Monk Team · 2 min read- ProductMonk is a DevOps agent that does the work for you.2 min
- EngineeringPretty please won't stop your agent from deleting production. Here's what will.14 min
- EngineeringCapsules as audit targets4 min
- EngineeringWhy giving your coding agent shell access is a bad idea5 min
- ProductMonk Capsules: 0 config, full-stack, per-branch previews5 min
- EngineeringState vs context — the difference in 5 examples6 min
- EngineeringThe other half of the harness7 min