I’m coming back to this, as I’m still doing a bit of work in this field and figured others might be interested in joining in or following aling.
I mentioned before that where I work, we’ve been working on an IP to carbon intensity API now - this provided country level carbon intensity figures.
This doesn’t seem to work for Fly.io, because the IP ranges are not exposed. You can see the confirmation here:
I’ve realised though that because fly.io exposes the FLY_REGION environment variable to the application server managing a request, you can share where it is being served from.
This would let you work out the average carbon intensity of the energy being used, at country level at least. We we publish this data as part of an open source software library, CO2.js.
This is driven by the data visible here in the app:
Carbon intensity varies within a country, but this would be a starting point.
I’m planning to use fly.io for a project later this month, where I’m intending to experiment with exposing this info via headers so that users can start to understand the carbon footprint of request. I’ve outlined some more below, here:
If you’re up for experimenting in this field, let me know - I really like Fly.io as as platform, and I’d rather Fly.io becomes a greener platform than try to find a green platform, and somehow hope the developer experience eventually reaches that of fly.io.