This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Codensity
Find the feature behind your software's carbon footprint
Codensity shows the estimated carbon and energy of every feature in your Node.js app. Wrap a function with the SDK, and each feature gets its calls, energy and carbon by day, so you can see which one costs the most. Free plan to start.
Hi Product Hunt, I'm Prince and I built Codensity.
I've been a developer for years, living in dashboards like Grafana and Prometheus: latency, error rates and throughput for every service. During my master's in informatics, focused on sustainability and software development, one question kept coming back: if we can measure everything else about our software, why can't we see the carbon behind it? Not for a whole server or cloud account, but for the features we actually ship.
The tools that do this are rarely built or priced for small and medium-sized teams. So I started building Codensity in February 2026, on my own until September, when a fellow developer joined me. Along the way it was selected as one of six finalists in a startup challenge at Innovatum Science Centre in Sweden.
How it works: you wrap the work you care about with the Node.js SDK. Codensity estimates the energy and carbon behind each feature and shows it by day, next to its calls. The first event creates the feature for you, so there's nothing to set up in the dashboard (PS, if you want to move fast. You can still set up anyway and use its ID).
What it makes visible:
- How often a feature runs isn't how much carbon it causes. In our demo, checkout is 14% of the calls but 34% of the carbon, because each call does far more work. - Dormant features show up too, so dead code stops hiding. - Carbon and calls on one timeline tell you whether a spike was more traffic or heavier work per call.
Every figure is an estimate, and the product labels it that way. It's built to compare features and spot changes over time, not for audited reporting.
I'd love to hear from you, especially teams working on sustainability: which feature in your app would you measure first? I'll be here all day answering questions.
About Codensity on Product Hunt
“Find the feature behind your software's carbon footprint”
Codensity was submitted on Product Hunt and earned 2 upvotes and 1 comments, placing #147 on the daily leaderboard. Codensity shows the estimated carbon and energy of every feature in your Node.js app. Wrap a function with the SDK, and each feature gets its calls, energy and carbon by day, so you can see which one costs the most. Free plan to start.
On the analytics side, Codensity competes within Analytics, Developer Tools and Climate Tech — topics that collectively have 710.6k followers on Product Hunt. The dashboard above tracks how Codensity performed against the three products that launched closest to it on the same day.
Who hunted Codensity?
Codensity was hunted by Prince Appiah. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Codensity including community comment highlights and product details, visit the product overview.
Prince Appiah
Hi Product Hunt, I'm Prince and I built Codensity.
I've been a developer for years, living in dashboards like Grafana and Prometheus: latency, error rates and throughput for every service. During my master's in informatics, focused on sustainability and software development, one question kept coming back: if we can measure everything else about our software, why can't we see the carbon behind it? Not for a whole server or cloud account, but for the features we actually ship.
The tools that do this are rarely built or priced for small and medium-sized teams. So I started building Codensity in February 2026, on my own until September, when a fellow developer joined me. Along the way it was selected as one of six finalists in a startup challenge at Innovatum Science Centre in Sweden.
How it works: you wrap the work you care about with the Node.js SDK. Codensity estimates the energy and carbon behind each feature and shows it by day, next to its calls. The first event creates the feature for you, so there's nothing to set up in the dashboard (PS, if you want to move fast. You can still set up anyway and use its ID).
What it makes visible:
- How often a feature runs isn't how much carbon it causes. In our demo, checkout is 14% of the calls but 34% of the carbon, because each call does far more work.
- Dormant features show up too, so dead code stops hiding.
- Carbon and calls on one timeline tell you whether a spike was more traffic or heavier work per call.
Every figure is an estimate, and the product labels it that way. It's built to compare features and spot changes over time, not for audited reporting.
There's a free plan to start (https://getcodensity.com/pricing), and you can explore a demo workspace without signing up: https://getcodensity.com/demo?re.... Node.js/Express and NestJS are supported today.
I'd love to hear from you, especially teams working on sustainability: which feature in your app would you measure first? I'll be here all day answering questions.