Find the feature behind the footprint.

Estimated carbon and energy for every feature you ship, next to the calls behind it.

Join the waitlist View live demo

Your dashboards show how fast, how often and how broken. Not how much carbon.

Every block is one feature.

Image upload: 2% of calls, 13% of the carbon.

38%Product searchsearch-query
24%Feed renderingfeed-render
17%Checkoutcheckout-flow
13%Image uploadimage-upload
8%14 other featuresall others

Example data: share of estimated CO2e by feature, Acme Shop · Production · Last 30 days
Feature	Share of app total	Est. CO2e	Calls	Share of calls
Product search	38%	7.07 kg	4.1M	45%
Feed rendering	24%	4.46 kg	2.9M	32%
Checkout	17%	3.16 kg	380k	4%
Image upload	13%	2.42 kg	210k	2%
14 other features	8%	1.49 kg	1.6M	17%
Whole app	100%	18.6 kg	9.19M	100%

The column your monitoring never had.

Codensity doesn't replace the monitoring you already have. It adds the column it never had: estimated carbon, attributed to the features your team recognizes.

Feature	Calls	p95 latency	Error rate	Est. CO₂e
	What your monitoring already shows			What Codensity adds
Product search`search-query`	4.1M	180 ms	0.2%	7.07 kg
Feed rendering`feed-render`	2.9M	240 ms	0.4%	4.46 kg
Checkout`checkout-flow`	380k	620 ms	0.9%	3.16 kg
Image upload`image-upload`	210k	1.4 s	0.3%	2.42 kg

Three steps from function to footprint.

Wrap it.

Install @codensity/node and wrap the work you care about. Your function's return value passes through unchanged, and events are batched in the background.

checkout.ts

import { CodensityClient } from "@codensity/node";

const codensity = new CodensityClient({
  key: process.env.CODENSITY_KEY,
  environment: "production",
});

export async function checkoutFlow(cart) {
  return codensity.track("checkout-flow", () => processCart(cart));
}

02
It shows up.
The first event creates the feature for you, with a readable name taken from its key.
Your code sendstrack("checkout-flow", …)
Codensity creates
Features
Product searchsearch-queryActive
Feed renderingfeed-renderActive
Checkout Flowcheckout-flowNew
03
Watch it over time.
Every feature gets its calls, energy and carbon estimates by day, so a change in the line has a name attached.
Checkout · est. g CO₂e per day
30 days agoToday

Built around your features.

Rankings

See which features carry the most carbon.

1Product search7.07 kg
2Feed rendering4.46 kg
3Checkout3.16 kg
4Image upload2.42 kg

Dormant features

Spot the features nobody calls anymore.

legacy-exportNo telemetry in 30 days
promo-banner-v1No telemetry in 30 days

Structure

Projects, environments, features.

Acme Shop
- Production
  - search-query
  - checkout-flow
  - image-upload
- Staging

Plain units

Every unit, explained where it appears.

g CO₂e: Grams of carbon dioxide equivalent: the warming impact of different greenhouse gases expressed as one number.
kWh: Kilowatt-hours of energy used to do the work.
est.: Carbon and energy figures are estimates, and the product labels them that way.

Integrations

Node.js today, with Express and NestJS helpers.

@codensity/node
Express
NestJS

Start free. Pay when every feature counts.

Compare all plans →

Free

5M events a month, one project and 7 days of history. Enough to find your heaviest feature.

Join the waitlist

Team

$79per month

CO₂e for every feature, full history, rankings and comparisons across 5 projects.