server-ip-addresses VS carbonifer

This is actively updated - last update 12 hours ago - https://github.com/jhassine/server-ip-addresses

Managed challenge for a custom list of 10k ip range from datacenter / vpn, which 10k is the maximum limit for free plan. (I use this list)

I've started to work on Carbonifer, a tool that can estimate carbon emissions before deploying an infrastructure. A bit appreciate infracost, this reads Terraform files and estimates carbon emissions if this plan is applied. Currently targeting GCP computes, I plan to expand it to other providers and resources and of course target other IaC (pulumi? Chef?...). This is currently using average carbon intensity data (gCO2eq/kWh) but this will also read real-time data (example of real-time‏‏‎‏‏‎‏‏‎‏‏‎­data source: electricitymaps). Carbonifer can help to pick the best machine type/region/provider but I also can imagine it coupled with a scheduler to deploy where/when it's less carbonated or even resize/move an existing infra. Have a look at https://github.com/carboniferio/carbonifer I would appreciate any feedback or thoughts about it. Do you have this kind of need?

Some tools like Carbonifer reads terraform files and estimate carbon emissions, which varies a lot depending on your provider region. That tool could be part of your CI to show what would be the carbon impact of a change request.

Have a look at https://github.com/carboniferio/carbonifer

Reads Terraform files and estimate what will be the carbon emissions of a infra project if deployed. Currently supports only GCP (AWS, Azure are work in progress).

In the future, it will suggests better machine types or providers regions to minimise carbon footprint and will help pilot carbon footprint of infra with realtime carbon emissions of the grid.

Github: https://github.com/carboniferio/carbonifer