# Ephemeral Cloud Sandbox Cost Calculator & Teardown Auditor Price a throwaway sandbox across AWS, GCP, Azure, Vercel, Fly.io, Railway, Replit, Codespaces and Gitpod, then audit what forgetting to tear it down actually costs per forgotten day. > Canonical page: https://elysiatools.com/en/tools/ephemeral-cloud-sandbox-cost-calculator-teardown-auditor-aws-gcp-azure-vercel-fly - **Category:** Development - **Keywords:** cloud cost, sandbox pricing, aws bill, elastic ip charge, orphaned ebs, teardown audit, forgotten resources, codespaces pricing, fly.io cost, dev sandbox, side project bill, cloud waste ## Overview Say what the sandbox is (web API, database box, T4 GPU batch, dev environment, static preview), how long it runs each day and for how many days, plus egress, volumes, snapshots, logs, static IPs and whether a load balancer fronts it. The comparison table prices the window on nine providers from a dated price snapshot: verified numbers (GitHub Codespaces $0.18/hr for 2 cores and $0.36/hr for 4, Fly.io shared-cpu-1x units at $0.0030/hr, AWS EBS gp3 $0.08/GB-month, S3 $0.023/GB-month, CloudWatch $0.50/GB ingest) carry a ● marker; entries that drift by region or plan are marked as estimates. Egress free tiers are honoured (AWS 100 GB/month, GCP 200 GB/month, Azure 5 GB, Vercel 1 TB). The teardown auditor is the part that saves real money: every resource class that keeps billing after you stop caring — the $0.005/hr unattached Elastic IPv4 ($3.60/month since February 2024), orphaned EBS volumes at $0.08/GB-month, snapshots at $0.05/GB-month, log groups that keep ingesting at $0.50/GB, S3 residue, an idle ALB at ~$16/month — priced across a configurable forgotten-days horizon with the reminder that deleting an instance does not delete its IP, volumes, snapshots or logs. ## Inputs - **Workload profile** (select) - **Hours active per day** (number) - **Days in the window** (number) - **Egress traffic (GB)** (number) - **Block storage (GB)** (number) - **Snapshots (GB)** (number) - **Logs ingested per day (GB)** (number) - **Static IPv4 addresses** (number) - **Load balancer enabled** (checkbox) - **Forgotten-days horizon** (number) ## When to use - Comparing runtime costs across nine cloud and dev environment platforms before launching a temporary project. - Auditing the hidden recurring bills caused by orphaned cloud resources after terminating virtual machine instances. - Budgeting intermittent development or batch workloads with custom daily run hours and egress traffic requirements. ## How it works - Select your workload profile—such as Web API, Dev Environment, or GPU Batch—and set active hours per day and total runtime days. - Specify infrastructure requirements including storage volumes, snapshot sizes, daily log ingestion, static IPv4 addresses, and load balancers. - Review the multi-provider price comparison alongside the teardown audit to see cumulative waste across a configurable forgotten-day horizon. ## Use cases - Selecting the most cost-effective cloud provider for short-lived dev environments and feature branch previews. - Calculating potential billing leaks from forgotten prototype infrastructure and orphaned block storage. - Forecasting infrastructure expenses for intermittent GPU batch training jobs with high outbound data transfer. ## Frequently asked questions ### Which cloud providers are compared in this tool? The tool compares AWS, GCP, Azure, Vercel, Fly.io, Railway, Replit, GitHub Codespaces, and Gitpod. ### Why do cloud sandboxes incur costs after instance termination? Terminating a compute instance does not automatically delete associated EBS volumes, snapshots, log groups, or unattached Elastic IPs. ### Are provider free egress allowances included in calculations? Yes, monthly free egress allowances—including 100 GB for AWS, 200 GB for GCP, 5 GB for Azure, and 1 TB for Vercel—are factored into estimates. ### How is the forgotten-days horizon calculated? It multiplies the daily storage, IP, load balancer, and log retention rates by the number of days resources remain undeleted. ### What rate is used for unattached static IPv4 addresses? Unattached static IPv4 addresses are priced at the standard rate of $0.005 per hour, which equals approximately $3.60 per month. ## Related tools - [Tailwind Color Palette Sync](https://elysiatools.com/en/tools/tailwind-color-palette-sync): Generate theme.extend.colors for tailwind.config.ts from HEX colors, with WCAG contrast levels and optional dark mode. - [Gray Code and Thermometer BCD Encoder Visualizer](https://elysiatools.com/en/tools/gray-code-and-thermometer-bcd-encoder-visualizer): Convert an N-bit value to binary, Gray, one-hot and thermometer codes with a counting truth table, Hamming-distance chart and Verilog/VHDL encoder stubs. - [API Contract Mutation Tester](https://elysiatools.com/en/tools/api-contract-mutation-tester): Mutate OpenAPI request fields into semantically risky variants and optionally send them to a real backend to check defensive validation coverage - [API Contract Stress Tester](https://elysiatools.com/en/tools/api-contract-stress-tester): Generate boundary-value test cases from an OpenAPI 3.x document and optionally send them to a real backend to spot contract mismatches - [cURL to Go (net/http) Converter](https://elysiatools.com/en/tools/curl-to-go): Convert a cURL command into a Go net/http code snippet with http.NewRequest, headers, and body - [cURL to JavaScript (axios) Converter](https://elysiatools.com/en/tools/curl-to-js-axios): Convert a cURL command into a JavaScript axios code snippet with config object, headers, and data - [cURL to JavaScript (fetch) Converter](https://elysiatools.com/en/tools/curl-to-js-fetch): Convert a cURL command into a JavaScript fetch() code snippet with headers, body, and method - [cURL to PHP (cURL) Converter](https://elysiatools.com/en/tools/curl-to-php): Convert a cURL command into a PHP cURL code snippet with curl_setopt, headers, and post fields ## Samples - [Contentful Cloud-based CMS Samples](https://elysiatools.com/en/samples/contentful-samples): Comprehensive Contentful examples covering content modeling, API integration, webhooks, migrations, and frontend integration patterns - [Web Image Processing Python Samples](https://elysiatools.com/en/samples/web-image-processing-python): Web Python image processing examples using PIL/Pillow including reading, saving, resizing, and format conversion - [Google Cloud Platform Samples](https://elysiatools.com/en/samples/google-cloud): Google Cloud Platform services examples including Cloud Functions, Cloud Storage, Firestore, and Cloud Run - [Linode Cloud Service Samples](https://elysiatools.com/en/samples/linode): Linode cloud platform examples including Linode instances, Object Storage, Load Balancers, and Kubernetes