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
Culpa
Local-first cost tracking for AI products
Your bill spiked and your dashboard shows one number. Culpa names the conversation that spent it, then forecasts your next bill. Local-first LLM cost tracking. Your prompts stay on your own infrastructure. Most AI dashboards just show what you spent. Culpa shows who spent it. As a local-first cost tracker, Culpa traces every LLM dollar back to the exact conversation and user. The best part? Your prompts never leave your infrastructure.
I’m Zolani, founder of Culpa. Culpa started with a question I couldn’t get answered while building a different AI product:
What is this bill increase? What exactly moved it?
Provider dashboards showed the model, tokens and total spend. That was useful, but when we started looking at unit economics, I wanted to know which conversation, feature, customer or agent step was behind the increase. I kept going back to spreadsheets, logs and guesswork, so eventually I built the tool I wanted for myself.
One conversation made 2,438 model calls.
🔍 Our launch trace recorded 6,621 model calls. One conversation accounted for 2,438 of them. Culpa calculated $946.43 in model cost from the recorded usage and applicable provider pricing.
By turn 2, the context being carried forward had already roughly doubled. The conversation was still running comfortably inside the model’s context window, but its cost profile had changed very early.
💡 Culpa lets you work backwards from there.
Which customer used which feature? Which conversation ran? Which workflow expanded? Which call or step changed the pattern? Instead of knowing only that your model bill increased, you can see which part of the product needs attention.
You can also compare AI cost with customer revenue and forecast what a feature, cohort or launch is likely to cost before you run it.
🔓 Culpa runs on your infrastructure. Your prompts and responses stay there. Culpa only sends the counts needed to run your plan, and if Culpa ever fails to record something, your application keeps running.
For the PH launch, we’re opening the first 100 Culpa workspaces at $199 for the founding year, normally $480.
That’s seven months free. Find your first culprit and activate within 14 days to keep the founding price. After year one, your workspace renews at the standard Builder price.
First 100 workspaces only.
One question for the thread:
When your AI workflows get expensive, what’s the smallest unit you can currently trace that cost back to?
Model, request, conversation, customer action or individual call?
About Culpa on Product Hunt
“Local-first cost tracking for AI products”
Culpa was submitted on Product Hunt and earned 3 upvotes and 1 comments, placing #92 on the daily leaderboard. Your bill spiked and your dashboard shows one number. Culpa names the conversation that spent it, then forecasts your next bill. Local-first LLM cost tracking. Your prompts stay on your own infrastructure. Most AI dashboards just show what you spent. Culpa shows who spent it. As a local-first cost tracker, Culpa traces every LLM dollar back to the exact conversation and user. The best part? Your prompts never leave your infrastructure.
On the analytics side, Culpa competes within Analytics, Developer Tools and Artificial Intelligence — topics that collectively have 1.2M followers on Product Hunt. The dashboard above tracks how Culpa performed against the three products that launched closest to it on the same day.
Who hunted Culpa?
Culpa was hunted by ISTIAK AHMAD. 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 Culpa including community comment highlights and product details, visit the product overview.
ISTIAK AHMAD
Hey Product Hunt,
I’m Zolani, founder of Culpa. Culpa started with a question I couldn’t get answered while building a different AI product:
What is this bill increase? What exactly moved it?
Provider dashboards showed the model, tokens and total spend. That was useful, but when we started looking at unit economics, I wanted to know which conversation, feature, customer or agent step was behind the increase. I kept going back to spreadsheets, logs and guesswork, so eventually I built the tool I wanted for myself.
One conversation made 2,438 model calls.
🔍 Our launch trace recorded 6,621 model calls. One conversation accounted for 2,438 of them. Culpa calculated $946.43 in model cost from the recorded usage and applicable provider pricing.
Then we followed the conversation.
Turn 1 carried 30,157 tokens of context. Turn 2 carried 62,411.
By turn 18, it had reached 164,926.
The final context reached 867,161 tokens.
By turn 2, the context being carried forward had already roughly doubled. The conversation was still running comfortably inside the model’s context window, but its cost profile had changed very early.
💡 Culpa lets you work backwards from there.
Which customer used which feature? Which conversation ran? Which workflow expanded? Which call or step changed the pattern? Instead of knowing only that your model bill increased, you can see which part of the product needs attention.
You can also compare AI cost with customer revenue and forecast what a feature, cohort or launch is likely to cost before you run it.
🔓 Culpa runs on your infrastructure. Your prompts and responses stay there. Culpa only sends the counts needed to run your plan, and if Culpa ever fails to record something, your application keeps running.
For the PH launch, we’re opening the first 100 Culpa workspaces at $199 for the founding year, normally $480.
That’s seven months free. Find your first culprit and activate within 14 days to keep the founding price. After year one, your workspace renews at the standard Builder price.
First 100 workspaces only.
One question for the thread:
When your AI workflows get expensive, what’s the smallest unit you can currently trace that cost back to?
Model, request, conversation, customer action or individual call?