At TKEG Expat, a corporate-services firm, what we used was consolidation followed by deleting the cloud resources that no longer had a job, which AWS's own Well-Architected guidance calls decommissioning workload resources that are no longer required. In July 2026, we moved our site's server-side renderer, APIs and MySQL cache off a deprecated Alibaba US server, and our AI chat app off Azure Container Apps, onto one AWS EC2 t3.medium. After that, we deleted the container app, the container registry, storage, the environment with its 2 certificates, Front Door, an orphaned workspace and a cognitive account, and only kept the model and telemetry.
The level I can show is our steady hosting core, which now sits at about $77 a month at list price, with two workloads from two providers running on one server. On Azure, our trailing 30-day consumption went from about $17.45 to about $1.70 at list price, all sponsorship-funded. However, the container stack itself only cost a few dollars a month and most of that fall came from lower model inference, so I would not credit it to the deletions. Because gross list-price usage rose once the new server was added (the Alibaba bill it replaced is not in AWS), AWS Cost Explorer shows no AWS-side reduction at all, and credits have offset every month since June 2026.