// Articles
Guides, tutorials, and comparisons to help you build better backend applications.
Six guardrails for letting agents ship backend changes to your own AWS or GCP, how to apply each one with any tooling, and which platforms enforce them.
Five ways to handle cloud access for coding agents, ranked by what an agent can break and who approves the change.
Claude Code can edit a backend and open a pull request in minutes. The hard part is the deploy job: how the change reaches your AWS or GCP account without putting long-lived cloud keys in the agent session. This guide covers the safe way for AI agents to ship backend changes to your cloud.
Agentic coding is AI agents that edit, run and propose deploys for real repositories. What Cursor and Claude Code change for backend teams, where cloud credentials go wrong, and the safe way for AI agents to ship backend changes to your cloud.
Skip the portal project. Give agents a governed path that provisions and deploys backends into your own cloud.
Ops teams import customer lists, price sheets and backfills from spreadsheets every week. Here is a tested TypeScript import tool with direct uploads to S3, a background worker and a status endpoint, built by a coding agent and deployed to your own AWS account.
A /refund command that support can run from Slack, built by a coding agent as a TypeScript endpoint with a verified signature, a secret and a Postgres table, and deployed to your own AWS account.
Discount requests, access grants and refunds over a limit follow the same pattern, where a request waits for another person's approval before any work happens. Here is how an agent can build that on AWS by hand, and with Encore.
An internal tool where every logged-in employee can do everything is one bad click away from an incident. Here is how to have an agent add roles from your identity provider to a Go backend, by hand and with Encore.
Operations and support staff are building their own tools with coding agents. The question for the engineering team is where those apps run and what reviews them. Here is a setup on plain AWS and one with Encore.
Weekly revenue summaries and daily failed-payment lists are the internal tools nobody opens a browser for. Here is how an agent can build one as a Go cron job on AWS by hand, and how it looks with Encore.
Once an internal tool can refund orders or change customer records, someone will ask who did what. Here is how to have an agent add an audit log on AWS by hand, and how to do it with Encore and a Pub/Sub topic.