Agent Deployment at Writer
The problem
Writer's enterprise customers wanted to run AI agents on the platform. Each customer's agents had to run in their own isolated environment, so that one customer's agent could never see or affect another customer's data or execution.
Agent Builder was Writer's product for building agents. I worked on both versions, and for v2 I led the platform and authentication architecture. Agent Deployment was the part that had to run those agents for real customers, safely, for many customers at once.
What made it risky
Four things had to be right at the same time: tenant isolation, customer secrets, untrusted files, and agreement between SecOps, DevOps and the customer-facing teams. Getting any one of them wrong would have been a security incident or a stalled project.
Each of the four needed its own answer. Isolation meant per-tenant execution, so no two customers ever shared a runtime. Secrets meant customer keys never sat in plain text. Files meant anything a customer uploaded was scanned before an agent touched it. And every decision had to work for SecOps, DevOps, customer engineering and the solution architects.
What I did
As tech lead and lead of a team of 4 on Writer's Agent Builder, I architected Agent Deployment on Cloudflare Containers and Durable Objects, with MCP OAuth integrations for tools. I designed the security layer: environment variables encrypted at rest and decrypted only on demand, ClamAV malware scanning for files, Redis rate limiting, and a DynamoDB partition key strategy. To get every team behind one design, I wrote the options and trade-offs down, met each team one to one to understand its constraints, and then ran a single large design review.
Before building, I researched the options: multi-agent orchestration patterns, agent frameworks such as the AWS Strands SDK, and MCP as the standard for how agents use tools. That research fed straight into the design. Day to day I led and mentored the team, and former teammates describe me as a good mentor.
Result
The platform was live in a limited rollout when I left in May 2026. In the words of Writer's Sr. Director of Engineering, I "consistently turned ambiguous, cross-team problems into a shipped system."

