Carbonly instruments your codebase at the feature level — turning execution time and memory into energy and CO₂ per call, in real time. No black boxes, no guesswork.
Trusted by engineering teams at Adobe, AngelList, Customer.io, Hotjar, Zoho and more
import { CarbonlyClient } from "@carbonly/node";
const carbonly = new CarbonlyClient({
apiKey: process.env.CARBONLY_API_KEY,
});
export async function checkoutFlow(cart: Cart) {
return carbonly.track("checkout-flow", async () => {
// your feature logic here
return await processCart(cart);
});
}Trusted by engineering teams with sustainability at scale
What you get
Instrument once, then roll from clear signals to rankings your team can act on—without turning sustainability into a side project.
Wrap the product flows and code paths you care about with a lightweight SDK. Carbonly batches signals in the background so you get a clear picture of cost and usage without slowing down shipping.
How it works
Carbonly is designed to fit into your existing codebase without changing how you write features.
Why Carbonly
Carbonly was built from the ground up for developer teams who want real numbers, not approximations.
| Dimension | Carbonly | Typical APM | Details |
|---|---|---|---|
| Feature-level, not service-level | Per-feature footprint | Service-wide averages | Most tools smooth impact across an entire service. Carbonly ties usage to the product flows you name—so teams see what actually moved the needle, not a blended average. |
| Deterministic, auditable math | Transparent methodology | Opaque scoring | Every estimate is built from documented assumptions you can review and revisit. Same inputs produce the same outputs—so the story holds up in a design review or audit conversation. |
| Decision-ready, not dashboard-only | Consistent, explainable signals | Periodic reporting workflows | Carbonly gives teams a stable way to interpret impact alongside delivery priorities, so sustainability becomes part of routine execution rather than a separate process. |
| Built for engineers, not execs | Ships with your workflow | Quarterly slide decks | Instrumentation lives next to the code, checks sit alongside the rest of your automation, and signals show up beside the tools your team already trusts—not as a one-off narrative for leadership. |
Most tools smooth impact across an entire service. Carbonly ties usage to the product flows you name—so teams see what actually moved the needle, not a blended average.
Every estimate is built from documented assumptions you can review and revisit. Same inputs produce the same outputs—so the story holds up in a design review or audit conversation.
Carbonly gives teams a stable way to interpret impact alongside delivery priorities, so sustainability becomes part of routine execution rather than a separate process.
Instrumentation lives next to the code, checks sit alongside the rest of your automation, and signals show up beside the tools your team already trusts—not as a one-off narrative for leadership.