Defang

Defang lets you build AI agents once and deploy them to any cloud environment with a single command. It handles all the infrastructure, including networking, compute, databases, and LLMs, mapped to native services on AWS, GCP, and beyond. Try it at defang.io

Great article and we agree in general. Which is why we at Defang use Compose.yaml as our "spec" and we emit (not "generate") Infra-as-code for your desired cloud: #AWS, #GCP, #Azure coming soon. The translation is deterministic, not probabilistic. We tend to think of it as a "compiler for the cloud". Try it at defang.io.

New blog post: "A sufficiently detailed spec is code" I wrote this because I was tired of people claiming that the future of agentic coding is thoughtful specification work. As I show in the post, the reality devolves into slop pseudocode haskellforall.com/2026/03/a-suff…

Defang now provides detailed deployment views so you can see exactly what’s running in your cloud account. You can: • View all provisioned resources by service • See how resources are grouped and tagged • Navigate directly to the corresponding resource in your cloud console Everything created during a deployment is visible and traceable.

Deploy with Defang via AWS Marketplace. Subscribe in a few clicks. Roll costs into your existing AWS bill. Keep procurement simple. Everything runs in your AWS account, now it’s even easier to get started.

Every deployment now tracks: • Which branch it came from • Who triggered it • Whether it was via CLI, Portal, or CI Clear visibility. Full traceability. Built for teams that need accountability across environments.

Love the features, scale, security, and reliability of #AWS but struggle with its complexity? #Defang just made it even easier to deploy your application to AWS, without ever touching the AWS console. Well, almost - you do have to create your AWS account first! Defang enables you to easily connect *your* #GitHub to *your* AWS account. And then deploy your cloud agnostic #Docker #Compose application directly to your AWS account every time you merge code. Compute, storage, caches, networking, DNS, even LLMs - all taken care of, all mapped to native AWS services like #ECS, #RDS, #Elasticache, #ALB, #Route53, and #Bedrock. Secure, Cost-efficient, Scalable. And compliant with AWS Well-Architected Framework (#WAFR). No infrastructure-as-code needed. Check out details in our latest blog here: defang.io/blog/post/depl… 🚀 🚀 🚀 Try it today at defang.io

Need to peer VPCs or avoid IP range conflicts? Defang now supports custom network CIDR configuration for BYOC deployments. You can define your subnet directly in your Compose file: networks: default: ipam: config: - subnet: 10.12.0.0/16 This gives you more control over how your infrastructure integrates with existing cloud environments, especially in multi-VPC or enterprise setups.

It's now even easier to deploy your application to #GCP with #Defang! 🚀 🚀 🚀 Check out this video that demonstrates how, in 3 easy steps: youtu.be/9D_swvGGd1E?si… 1. Define your cloud-agnostic application (especially agentic apps) as a #Compose project in your #GitHub account. 2. Connect to your GCP account from Defang with our new Cloud Connection feature. 3. Let Defang set up trust between *your* GitHub and *your* GCP accounts. And that's it! Defang does all the heavy lifting of mapping from your Compose project to the details of GCP. DNS, networking, load-balancing, compute, databases, queues, and even LLMs - all taken care of with native GCP services. Deployed to your GCP account directly from a GitHub Action every time you merge code. As simple as that. Production-ready - secure, scalable, cost-efficient. No Infra-as-code needed! Try it today at defang.io

The Defang Portal now includes a command palette for faster navigation and actions. Press Cmd+K to instantly: • Jump to projects • Open deployments • Trigger common actions • Navigate without leaving your keyboard

When you deploy infrastructure for customers, security can’t be an afterthought. Defang is SOC 2 compliant. That means audited controls, formalized processes, and real accountability around how we handle data, access, and infrastructure operations. If you're building production systems or deploying into enterprise environments, trust matters. Explore our Trust Center: trust.defang.io

We’ve added support for: defang config set --if-not-set This flag ensures a config value is only set if it hasn’t already been defined. It’s especially useful in CI or automated environments where you want manually applied configuration to take precedence and avoid unintended overwrites.

The Defang CLI login flow has been updated for a smoother login experience. It now uses shorter URLs and logs you into the Portal at the same time. Simpler flow. Fewer steps. Consistent sessions.

Defang now provides detailed deployment views so you can see exactly what’s running in your cloud account. You can: • View all provisioned resources by service • See how resources are grouped and tagged • Navigate directly to the corresponding resource in your cloud console Everything created during a deployment is visible and traceable. No abstraction layers hiding what’s happening underneath.

You can now deploy to AWS from GitHub Actions without storing long-lived cloud credentials. Using the Defang Portal, you can configure OIDC so your AWS account trusts your GitHub Actions workflows directly. This means: • No access keys stored in GitHub • No manual credential rotation • Short-lived, scoped authentication • A cleaner and more secure CI setup Configure once in the Portal, and your workflows can deploy safely to your AWS account.

Kiro Powers give agents specialized capabilities without overwhelming them with context. Install once. Activate on demand. Focused execution. The Defang Kiro Power does one thing extremely well: It turns your generated app into real cloud infrastructure. Check out the demo: youtube.com/watch?v=2xzUIH… In the demo, we: • Vibe-coded a Flask app with Kiro • Generated a Dockerfile and Compose setup • Deployed instantly to Defang Playground • Switched to AWS • Re-deployed into real ECS infrastructure All from inside the IDE. No Terraform. No CloudFormation templates. No manual IAM wiring. No guessing at VPC config. Kiro handles the build. Defang handles the infrastructure. Your Compose file becomes production-ready AWS or GCP resources, with proper networking, health checks, scaling, and security — based on deterministic rules, not hallucinated infrastructure. Build with natural language. Deploy with one command. That’s the Defang Kiro Power.

GPT-5.3 Codex can generate real apps. APIs. Agents. Full backends. The next step isn’t copy-pasting into a hosting dashboard. Use the Defang MCP Server to deploy directly to your own AWS or GCP account. Codex can even easily tail logs and iterate based on your deployed app. Your AI builds the app. Defang provisions the infrastructure. VPC. Load balancer. Managed database. IAM roles. All derived from your Compose file. No Terraform. No CloudFormation templates. No manual cloud wiring. Built something awesome with Codex? Deploy it to real infrastructure in your cloud.

You build your app. Now you need dev, staging, production. Then your first enterprise customer wants their own isolated deployment. Suddenly you’re managing duplicated configs, separate pipelines, and drifting infrastructure. Stacks solve this. A Stack is an isolated deployment of the same project. Same codebase. Same compose file. Completely separate infrastructure. Each stack gets its own: • Services • Load balancers • Databases • Secrets • DNS endpoints Your compose file remains the single source of truth. A stack is simply a deployment target. This makes common patterns simple: • Dev / staging / production • Per-customer isolated deployments • Regional deployments • Feature branch previews One codebase. Unlimited isolated environments. That’s what Stacks unlock. Learn more: defang.io/blog/post/name…

Claude Code isn’t just for generating files. With the Defang MCP integration, it can deploy your application directly to AWS or GCP. All from the same terminal session. Set it up once: defang mcp setup --client=claude-code Now your Claude Code agent can: • Deploy services • List running infrastructure • Retrieve logs for debugging • Estimate cloud costs • Destroy stacks • Manage configs You describe what you want. Claude writes the Compose changes. Defang provisions real cloud infrastructure. Whether you're using Claude Sonnet or the newer Opus 4.6 models for deeper reasoning and multi-step workflows, the result is the same: From idea → to infrastructure → in one conversational loop. No Terraform. No CloudFormation. No manual IAM wiring. Claude thinks. Defang deploys. To any supported cloud.

AI agents aren’t traditional web apps. They can run continuously, call LLMs, manage state, coordinate tasks, and need reliable compute that can scale under load. That means production-grade infrastructure. AWS and GCP have become the standard for serious agent deployments: • Containerized compute (ECS Fargate / Cloud Run) • Managed databases for persistent state • Secure LLM access (Bedrock / Vertex AI) • VPC isolation and enterprise-grade security The problem isn’t the cloud. It’s the complexity of deploying agents correctly across environments or client accounts. Defang turns your Docker Compose file into production-ready AWS or GCP infrastructure. One command deploys your agent with proper networking, IAM, databases, monitoring, and scaling. No Terraform. No CloudFormation templates. Just working infrastructure. If you're running agents in production or deploying for clients, this is the foundation that scales. Read more: defang.io/blog/post/what…

Open source powers the internet. It shouldn’t have to pay for deployment tooling. If your GitHub repository is public, Defang lets you deploy to your own AWS or GCP account for free. No trial. No credit card. No approval process. You bring your cloud account. You pay AWS or GCP directly for the infrastructure you use. Defang’s fee is zero. You still get radically simpler cloud deployments: • Deploy on push • Secure, scalable cloud infrastructure • Deployment history in the Portal • Easy integration with Bedrock or Vertex Every push can trigger a production deployment using GitHub Actions. Real cloud infrastructure. Production-grade. Yours to inspect and control. As long as your repo is public. You deploy to your own cloud. Defang is free. Open source deserves better. Get started at defang.io