Skip to content

Find the feature behind the footprint.

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

View live demo

Why carbon

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

How it works

Three steps from function to footprint.

  1. 01

    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));
}
  2. 02

    It shows up.

    The first event creates the feature for you, with a readable name taken from its key.

  3. 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 dayExample data

    30 days agoToday

In the product today

Built around your features.

Rankings

See which features carry the most carbon.

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

Est. CO₂e · last 30 days

Dormant features

Spot the features nobody calls anymore.

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

Candidates to archive, or code to remove.

Structure

Projects, environments, features.

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

Questions

Is Codensity free to start?
Yes. You can start on the Free plan and upgrade when your team needs more.
Are the numbers exact?
No. They are estimates, built from how long each feature runs and the memory it uses, combined with published grid carbon intensity. They are consistent enough to compare features and to track changes over time.
What does the SDK send?
Only what you track: the feature key, how long it ran, the memory it used, a timestamp and any metadata you add. It never reads request bodies, headers or user data.
Which languages are supported?
There is an SDK for Node.js, with integrations for Express and NestJS. Any other language can send events through the HTTP API. Support for more languages is on the roadmap and will be prioritized based on demand.
When can I create an account?
We will email everyone on the waitlist as soon as registration opens.

Get started

Wrap one feature. Watch its footprint appear.