Contact

Primary contact

Use the contact module below if you want the most reliable path. It works even when the local mail app does not open automatically.

Best reasons to contact us

• Report a calculator bug, broken input path, or output that looks directionally wrong.
• Point out a factual mistake, stale boundary explanation, or overlap between two pages.
• Ask for help understanding a provider pricing unit, validation step, or missing line item.
• Suggest a new calculator or guide when an existing workflow is clearly missing a real job.

Requests are triaged by type first: correction, calculator bug, estimate help, new topic request, or general site issue.

Reports without a page URL, a concrete broken step, or a clear boundary problem are harder to action well.

If you are asking for estimate help

• Include the page URL and the provider or region you care about.
• Share the measured driver you are using, such as requests per month, GB per month, retention days, or instance-hours.
• Say whether you want a baseline estimate, a peak scenario, or help understanding a billing boundary.
• If something looks wrong, include the exact inputs you used and the direction of the mismatch.

For correction requests, include:

• Include the page URL and the specific statement, output, or workflow step that looks wrong.
• Share the provider, region, unit, and any pricing rule involved if you know them.
• If the problem is reproducible, include the exact inputs or a screenshot of the issue.
• If the issue is about unclear wording or overlap with another page, link both pages.

If you want a new tool or guide

• Describe the service and the key billable units, such as requests, GB processed, GB-month, or hours.
• List the line items that must be included or excluded, such as transfer, logs, replication, or add-ons.
• Share one realistic usage example so the default workflow can be designed around an actual planning task.
• If a similar page already exists, explain what is missing from it instead of only naming a new keyword.

What we can and cannot help with

• We can: help model drivers, boundaries, units, and common missing line items.
• We can: fix calculator bugs and improve wording, routing, and validation guidance.
• We cannot: provide official quotes or guarantee a final bill because pricing tiers, regions, contracts, and rounding rules vary.
• We cannot: access your provider billing data, so only share what you are comfortable sending.

Response expectations

We aim to review clear correction or bug reports within a few business days. If your request is time-sensitive, add that context so it can be prioritized appropriately.

Requests that include the page URL, provider, region, unit, and the exact part that looks wrong are much easier to review than generic "this seems off" messages.

A strong report can lead to a direct correction, a clearer boundary explanation, a workflow rewrite, or lower prominence for a page that is no longer carrying its job well.

Review does not guarantee that every suggestion will be adopted exactly as submitted.

Related trust pages

• About: what the site is for and how pages earn publication.
• Methodology: how estimates should be built and validated.
• Editorial Policy: how topics are reviewed, updated, and corrected.
• Privacy Policy: how browser-side inputs and site usage are handled.

Privacy note

Calculator inputs run in your browser. Some pages may store values in browser storage so your inputs persist between visits. See Privacy Policy and Cookie Notice.