Measure and reduceyour website CO2 emissions
GreenFrame helps developers build low-carbon, energy-efficient web applications and reduce their environmental footprint, using a state-of-the-art platform based on real science.
These companies are reducing their digital carbon footprint with GreenFrame
Continuous monitoring of the carbon footprint
GreenFrame integrates into your CI pipeline to help you understand the impact of your changes and improve your development practices.
Simulate real user interactions
GreenFrame lets you write custom scenarios reflecting what people actually do on your website or application. Not just for idle pages!
- Scenarios are written in a simple language so that even non-tech people can contribute.
- Test your scenarios visually before running an analysis.
- GreenFrame relies on Playwright, the fast browser automation tool, which has a negligible footprint.
Monitor the entire architecture
GreenFrame collects system metrics on the browser, the network, the server, and the database to give you a full picture.
- GreenFrame uses Docker to isolate the components of your stack and collect usage metrics exempt from noise.
- Detect which component in your web stack emits the most CO2 for a given scenario, so you know where to start optimizing.
- The GreenFrame CLI lets you run analyses in your dev or CI environment. No customer data is ever sent to GreenFrame.
Our model computes the footprint
The GreenFrame Model turns system metrics into energy consumption (in Watt.hours) and Carbon emissions (in g eq. CO2).
- GreenFrame takes into account CPU, Network I/O, memory, disk usage, datacenter PUE, screens, and makes a difference between intranet and internet consumption.
Based on scientific publications
- We partnered with French research teams and CNRS to build a solid model applicable to real-world usage.
- The GreenFrame model is open-source, so you can understand our calculations.
Detect hot spots in your code
For each analysis, GreenFrame provides a detailed report designed to guide developers in their carbon reduction journey.
- Define the maximum emission budget for a scenario, and the CI build will fail for new features that emit too much CO2.
- Knowing which part of your architecture emits the most allows you to prioritize your efforts and decrease CO2 emissions quickly.
- To help you detect the piece of code that caused a spike, analysis reports show the timeline of emissions for a scenario.
What's at stake?
The growing use of digital technologies contributes to climate change.
- Share of digital in global carbon emissions
- Yearly increase of the digital carbon footprint
- Comes from usage, driven by developers
Developers must change their practices to build sustainable applications. Green IT requires accurate measurements of CO2 emissions.
From one-man agencies to large corporate companies, we have plans for everyone
Test GreenFrame on public websites
Uses the GreenFrame model
Basic user scenario
Measure only the browser & network
Analyses are public
Max 1 analysis per day per URL
Shared worker queue
Unlock all features, get the most value
Uses the GreenFrame model
Customize the scenario at will
Analyses are private
Unlimited analyses per URL
Dedicated worker queue