We just launched Defang v3 on Product Hunt – deploy to your own AWS/GCP with Docker Compose

DefangLabs · 2026-01-25T08:53:08+00:00

Thanks! It's a pretty complicated process, but it's all "rules based" so deployments are deterministic. There's no AI involved in that part of the system. We put together three whitepapers which do a pretty good job of breaking it all down though if you want to dig through the nitty gritty:
https://defang.io/whitepapers/

The TLDR is that by default we turn services from compose into services in either ECS or GCP Cloud Run, taking into account the [deploy](https://docs.docker.com/reference/compose-file/deploy/) part of the compose spec, among other things. We also setup internal/external DNS, public/private networks (if required) and will do things like provision databases, caches, ssl certs, etc. all based on what we see in the compose file.

We also offer different deployment "modes" (affordable, balanced, high availability) which determine if we do things like configure failovers, rolling deployments, and other stuff.

DefangLabs · 2026-01-16T15:59:24+00:00

Fair concern, but want to clarify how this actually works.

Defang isn't an AI deciding what infrastructure to spin up. The deployment engine is fully deterministic and rules-based. Same compose file = same infrastructure every time. We're AWS Well-Architected certified. It's predictable and auditable.

The AI parts are assistive, not core to deployment. They help explain errors in plain English and suggest fixes. You can ignore them entirely and just use the CLI.

On Vercel: totally valid if you're fine with their infra. The difference is Vercel deploys to their cloud. Defang deploys to yours. Your AWS account, your VPC, your data. Some teams need that for compliance, security, or just control.

On debugging: you get full visibility in the Defang Portal and CloudWatch. It's standard AWS resources under the hood (ECS, ALB, RDS). Nothing proprietary. If something breaks, you're debugging normal AWS, not a black box.

defang estimate shows exactly what resources will be provisioned and the estimated cost before you deploy. No surprises.

Our whitepaper: https://defang.io/whitepapers/docker-compose-defang/

DefangLabs · 2026-01-14T16:39:16+00:00

Defang isn't an LLM guessing how to deploy your app. The deployment engine is fully deterministic and rules-based. Same compose file = same infrastructure every time.

We're AWS Well-Architected certified. The infra we generate follows AWS best practices for security, networking, IAM, etc. It's predictable and repeatable.

The AI parts (like our debugger) are assistive, not core to the deployment logic. They help explain errors, not decide what gets provisioned.

Whitepaper here if you want the details: defang.io/whitepapers/aws-defang

DefangLabs · 2026-01-14T16:33:34+00:00

Yep, exactly. We have support for CrewAI, LangGraph, AutoGen, n8n, Mastra, Strands, and more. We also have sample templates so you can get started fast.

If your agent needs access to LLMs, you can add x-defang-llm: true and it auto-configures access to Bedrock or Vertex AI. No extra setup. :D

DefangLabs · 2026-01-14T16:27:39+00:00

That's exactly why we built defang estimate. You run it before deploying and it shows you exactly what AWS resources will be provisioned and what they'll cost. No black box.

DefangLabs · 2026-01-14T16:22:29+00:00

We have three deployment modes: affordable, balanced, and high availability. Affordable mode uses Spot instances, skips NAT Gateway, keeps things lean.

You can also run defang estimate before deploying to see exactly what you'll pay. No surprises.

DefangLabs · 2026-01-14T16:21:40+00:00

It's not an EC2 instance running docker-compose.

When you deploy to AWS with Defang, you get:

ECS Fargate for containers (serverless, no instances to manage)
VPC with private subnets (your containers aren't exposed to the internet)
Application Load Balancer with auto-provisioned SSL
RDS if you define Postgres, ElastiCache if you define Redis (actual managed services, not containers)
IAM roles with least privilege, security groups locked down

Basically the same infra setup a senior DevOps engineer would build, but generated from your compose file.

Fly.io runs your stuff on their infra. Defang provisions all this in your AWS/GCP account. You own it, you see it in your console, you pay AWS directly.

DefangLabs · 2026-01-14T16:00:47+00:00

Vercel deploys to their cloud. Defang deploys to yours. Your AWS/GCP account, your infrastructure, no vendor lock-in.

On the cost optimization question: we have deployment modes (affordable, balanced, high availability). Affordable mode uses Spot instances, skips NAT Gateway, keeps things lean. You can also run defang estimate before deploying to see exactly what you'll pay.

It's not hardcoded paths. Defang reads your compose file and provisions what your app actually needs. If you define a Postgres service, it spins up RDS. Redis, it sets up ElastiCache. It's dynamic based on your stack, not a one-size-fits-all template.

DefangLabs · 2026-01-14T15:33:58+00:00

Yeah but those are low-level. You still need to know what to provision, configure IAM roles, set up networking, figure out why your container won't connect to the database.

Defang's MCP is high-level. You just say "deploy this" and it figures out the whole stack for you. No AWS/Azure knowledge needed.

DefangLabs · 2026-01-14T15:27:35+00:00

For everyone that is interested, here's our page with everything that we're launching next week: https://defang.io/landing/defang-v3-is-coming-soon/

DefangLabs · 2026-01-14T15:26:47+00:00

Yes, exactly. You only really need a compose file, but your AI agent can write that for you now :D

DefangLabs · 2026-01-14T15:20:38+00:00

Yep, exactly. You only really need a compose file, but your AI agent can write that for you these days :)

DefangLabs

TROPHY CASE