Skip to main content

> CALCULATION ENGINE // INTERACTIVE

Cloud Sizing & Bill-of-Materials Wizard

Input your transaction throughput, storage, and egress metrics to calculate an itemized, rightsized cloud bill.

Workload & Sizing Parameters

Spot & Savings Plans Active (-58%)
4. Monthly Requests25.0M / mo
5. Persistent Storage2.5 TB
6. Outbound Egress10.0 TB / mo
Optimized Monthly Spend
$719/ mo
Unoptimized Baseline
$1,914
Monthly Savings
$1,195
Cost Reduction
%62
Recommended ArchitectureSCALED_PRODUCTION

High-Density Multi-Tenant AWS EKS with Karpenter & Graviton Spot

Inspect Full Architecture
Breakeven Inflection:Inflection champion above 50 vCPUs. Consistently 50% - 65% cheaper than ECS Fargate or standard managed compute across steady-state workloads.

Itemized Bill of Materials (BOM)

Monthly cost breakdown with applied FinOps optimizations

CategoryResourceQuantity / SpecsApplied FinOps TechniqueMonthly ($)
COMPUTEAutoscaling Container Nodes (19 vCPUs Graviton3)19 vCPUs provisioned across Karpenter Spot/Savings poolKarpenter Just-in-Time Spot + 1-Yr Savings Plan (-58%)$235
NETWORKINGGlobal Edge CDN & Outbound Egress Pipeline10.0 TB outbound bandwidth (80% Edge Cache Hit)Edge CDN Caching + Origin Shielding (-73% Egress Bill)$276
STORAGETiered Object Storage & Persistent Volumes2500 GB across Hot NVMe, Warm Standard & Cold S3 ArchiveLifecycle Rules + S3 Intelligent-Tiering + ZSTD Compression (-52%)$28
DATABASEHigh-Density Relational & State StoreRightsized Postgres + Connection PoolerPgBouncer Connection Pooling + Storage Autoscaling (-55%)$180
Total Optimized Spend:$719 / mo

Top Waste Vulnerabilities

  • •WST-CMP-01: Pod CPU/RAM request overprovisioning
  • •WST-NET-02: Cross-AZ chatter without Topology Aware Routing

Recommended FinOps Playbooks

  • Enable Karpenter consolidationPolicy: WhenEmptyOrUnderutilized
  • Enforce Goldilocks VPA recommendations
  • Deploy Cilium cluster mesh with local routing
AI Summary & Agent Operating Digest
AEO / GEO / Perplexity Indexable

The TinyCTO Cloud Economics & FinOps Architecture Canon ('The Cloud Bill Bible') establishes an operational engineering discipline for cloud financial governance. Built upon the FinOps Foundation FOCUS 1.0 open specification, the canon details 18 production cloud architectures across 6 archetypes, 24 cloud waste typologies with detection queries and CLI remediation playbooks, a deterministic sizing wizard engine with itemized Bill-of-Materials calculations, 10 deep bilingual engineering manuals, and a 26-tool comparison matrix.

FOCUS 1.0 Ontology & AttributionStandardized 12-column billing dataset mapping BilledCost, EffectiveCost, and ChargeSubcategory across AWS, GCP, Azure, and Bare Metal with mandatory 5-key tagging.
18 Architectures & Breakeven Curves54 maturity configurations across Serverless, Containers, Karpenter Kubernetes, Streaming, GenAI GPUs, and Bare-Metal Colocation with mathematical breakeven inflection models.
24 Cloud Waste TypologiesExhaustive waste detection queries and automated remediation commands covering Compute, Storage, Networking, Database, AI/ML, and Observability cost leaks.
Deterministic Sizing WizardInteractive calculation engine modeling throughput, storage, and egress to produce itemized BOMs, realistic savings projections, and waste vulnerability disclosures.

Cloud Sizing & BOM Calculation FAQs

How does the Cloud Sizing Wizard calculate itemized Bill of Materials (BOM)?

The wizard evaluates workload inputs (monthly requests, storage GB, outbound egress TB, GPU node hours, cloud provider) through deterministic cost formulas derived from current cloud rate cards. It calculates compute sizing (vCPUs and memory required for throughput), storage lifecycle tier distributions, CDN cache hit ratios for egress, and database connection pooling efficiency, generating an itemized BOM with baseline vs optimized comparisons.

What assumptions are used for the unoptimized baseline spend comparison?

The baseline models typical unmanaged cloud deployments: 100% On-Demand compute pricing (zero Savings Plans or Spot instances), standard uncompressed S3 storage with no lifecycle transitions, zero edge CDN caching (paying full $0.09/GB public internet egress fees), and unpooled relational databases with 2x over-provisioned CPU headroom.

Can the sizing wizard output be exported into infrastructure-as-code?

Yes. The generated BOM includes resource types, instance families, storage tiers, and autoscale parameters that map directly to Terraform/OpenTofu variables and Helm values for Karpenter and vLLM deployments.

How does the wizard factor in GPU Spot instance interruptions?

When GPU hours are entered, the engine evaluates whether Spot Preemptible instances can be safely utilized. It calculates the blended cost assuming an 80% Spot / 20% On-Demand fallback pool, factoring in checkpointing overhead and multi-region capacity routing.

Why does the wizard recommend colocation when egress exceeds 25 TB/month?

At 25 TB of outbound data transfer, hyperscaler egress fees ($2,250/month) exceed the total hardware rental cost of multiple dedicated servers with unmetered 1 Gbps connections ($300 - $600/month). The mathematical breakeven curve definitively shifts toward bare-metal colocation or hybrid egress shielding.

Does the sizing wizard support custom multi-region configurations?

The wizard models multi-region active-active and active-passive disaster recovery topologies, explicitly computing cross-region data transfer fees ($0.02/GB) and replication latency implications.