Providers
EC2 is a provider. denv is the inference layer.
Your AWS credentials. denv launches A10G, L4, L40S, A100 and H100 instances in the regions it has checked. Like EKS on EC2, for inference.
Amazon EC2 is in the catalog. Status: available. You connect with your own AWS credentials. denv launches and terminates instances in your account. AWS bills you.
GPUs listed: A10G, L4, L40S, A100 40GB, H100. Regions denv has checked: us-east-1, us-east-2, us-west-2, eu-west-1, eu-central-1, ap-northeast-1.
This is the “EKS on top of EC2, but for inference” line made concrete. You can already run EKS and vLLM yourself. denv is the control plane that also attaches non-EC2 sites, pins a recipe, and runs health checks, driver reinstall and failover. If you want the software inside an account you already operate, that is self-hosted, including on EKS.
H200 and B200 are not on the EC2 row. They are on Nebius and, for B200, Lambda. An EC2 H100 can still be one site in a cluster that also has those.
denv does not publish EC2 prices. Capacity blocks, savings plans and on-demand are your contract with AWS. denv will not launch past the maximum you set on the site, and it will not treat “over quota” as “try forever”.