Highlight the pricing tiers AND the fine-print footnotes
Cloud billing surprises almost always live in the 'Data Transfer' or 'Additional Charges' notes below the main table. Select both together.
How to decode AWS, GCP, and cloud pricing tables without getting burned by hidden fees.
Highlight complex AWS, GCP, or Cloudflare pricing tables and egress rules to calculate real monthly costs and spot hidden data-transfer fees.
Best fit
Best for cloud architects, DevOps engineers, and founders estimating monthly infrastructure bills from tiered pricing documentation.
On-screen walkthrough
How this looks on a real webpage.
Instead of switching tabs and rebuilding context, highlight the exact passage that slowed you down and press your shortcut (default: Ctrl+Shift+X or Cmd+Shift+X on macOS, fully customizable in settings).
1. Highlighted on page (Cloud Provider Documentation — Managed NAT Gateway Pricing)
You are charged for each 'NAT Gateway-hour' that your NAT gateway is provisioned and available ($0.045 per hour in us-east-1). You are also charged $0.045 per GB of data processed by the NAT gateway, regardless of the traffic's source or destination (including S3 and DynamoDB unless a Gateway VPC Endpoint is configured in the route table).
Ctrl+Shift+X“If we run 3 NAT Gateways (one per AZ) and push 15 TB/month to S3 through them, what does that cost and how do we cut it?”
2. Vezz me on-screen answer overlay
1. **Fixed Hourly Cost**: 3 gateways × 730 hrs × $0.045/hr = **$98.55/month**.
2. **Data Processing Cost**: 15,000 GB × $0.045/GB = **$675.00/month**.
3. **Total Monthly Cost**: **$773.55/month**.
4. **How to eliminate the $675/mo fee**: Add a free **Gateway VPC Endpoint for S3** to your private subnet route tables so S3 traffic bypasses the NAT Gateway.
3. Suggested follow-up questions in thread
- “What if 5 TB of that traffic is pulling container images from ECR instead of S3?”
- “Compare this against running a self-managed fck-nat / t4g.nano instance.”
Step-by-step workflow
How to run this workflow in place.
Provide your approximate workload numbers in the prompt
Press Ctrl+Shift+X and enter your rough traffic (e.g., '50M requests/month, 500GB storage, 2TB egress') so Vezz me performs the unit conversions.
Ask for the worst-case billing cliff
Ask which line item scales uncapped if a retry loop, DDoS spike, or high-cardinality metric explosion occurs.
Key details
Why this approach works better than switching tabs.
Comparison Matrix
Estimating Cloud Infrastructure Costs
Comparing in-page AI unit math with calculators and manual spreadsheet modeling.
| Method | Strengths | Tradeoffs |
|---|---|---|
| Vezz me on Pricing Table + Footnotes | Instant monthly dollar estimates and catching footnote egress traps in 15 seconds | Best for single-service or architecture-component estimates rather than 50-service BOMs |
| Official Cloud Pricing Calculator | Exporting formal multi-service procurement quotes | Takes 20+ minutes and requires knowing every hidden sub-resource ahead of time |
| Mental math while skimming | Rough order-of-magnitude checks | Frequently misses 1,000x unit conversions (GB-sec vs GB-month) and cross-AZ fees |
Frequently asked questions
Common questions about cloud finops workflow.
Can Vezz me compare two cloud providers' pricing tables?
Yes. Paste the first provider's numbers into the prompt box and highlight the second provider's pricing table on screen to compare them side-by-side.
Does Vezz me work inside the AWS Billing Console?
Yes, when you explicitly invoke Ctrl+Shift+X on selected text. Because Vezz me uses activeTab only, it never runs in the background of your AWS console.
Can it help decode SaaS per-seat and usage overage contracts?
Yes. Highlight observability (Datadog/New Relic) or AI token pricing tables to calculate overage break-even points.
Related workflows & guides
Explore connected pages.
Ready to try this workflow on your own reading?
Install Vezz me free, highlight text on any webpage, and press your customizable shortcut (default: Ctrl+Shift+X or Cmd+Shift+X on Mac) to get an answer right beside the source.
