Foundry.
Features: cost and capacity

Numbers that show their coverage.

A cost figure with no source behind it is worse than none. Foundry reports what AWS billed, what it only estimated, and what it could not see, and keeps IP space on the same footing.

Illustration: a machinist's tool wall with every tool hanging in its own place, and one bench drawer open under an amber lamp.
Cost

Where cost comes from

Cost Explorer is the always-available source: exact totals per day, account, and service, and exact attribution for one tag key. The Cost and Usage Report through Athena is the richer source, used when its export, database, workgroup, and results bucket are provisioned. Foundry tries the report first and falls back with a stated reason.

Actual and estimated, apart

A summary reports billed spend and Pricing API estimates in separate blocks. When neither supports a figure the total is null, not a sum of guesses.

A source status that explains an empty screen

It says whether there is no spend or no pipeline, and lists the active cost allocation tag keys.

Backfill

Load a date range with one Cost Explorer request, not one per day. A day is replaced, never added to, so two sources cannot double count it.

Cost by stack and by taxonomy

Group spend by stack, or by the tag keys in the organization's taxonomy.

Spend ahead

Forecasts and rightsizing

Forecasts for 30, 60, and 90 days come from a linear trend over the daily rollup, and a day more than two standard deviations from the trailing month is flagged as an anomaly. Cost and performance findings on resources Foundry manages become rightsizing patches that run through the governance gate. Moving an EC2 instance from an old generation to a current one is one click. Deleting an idle database deliberately is not.

Capacity

IP space and CIDR

  • Total, used, and free IPs for every VPC and subnet in the inventory
  • A pre-deploy estimate of how many IPs a stack will take per subnet, with a warning below a threshold
  • A ledger of every VPC and subnet CIDR, overlap checks, and suggested blocks from a supernet budget
  • A peering and transit gateway map that flags overlaps, and a per-VPC exhaustion forecast
Screens

On screen

Captures of the running console with fictional StrataForge Robotics data. No real AWS account or cost appears.

The cost page: month-to-date spend split by the project tag, with a tagging coverage chart over 27 days.The cost page: month-to-date spend split by the project tag, with a tagging coverage chart over 27 days.
Cost by taxonomy tag, with the tagging coverage behind it.
The forecast page: cost anomalies with their z-scores, and an empty rightsizing patches table.The forecast page: cost anomalies with their z-scores, and an empty rightsizing patches table.
Forecast: anomalies flagged, with rightsizing patches to follow.
The IP space page: six VPCs with their CIDR blocks, subnet counts, and availability.The IP space page: six VPCs with their CIDR blocks, subnet counts, and availability.
IP space: every VPC and its subnets.
The CIDR planner checking a block against the allocation ledger, showing seven conflicts and suggested non-overlapping blocks below.The CIDR planner checking a block against the allocation ledger, showing seven conflicts and suggested non-overlapping blocks below.
The CIDR planner: conflicts found, and blocks that fit.

← Back to features

Contact

Questions about this tool?

Write to Renkara Media Group and a person will answer.

Email contact@renkara.com