Donggyu Yoon

We want your feedback!

Hey everyone!

It’s been a little while since Product Hunt, and we just wanted to say thanks.

We ended up with 131 upvotes and ranked #21 alongside some seriously well-funded projects. Didn’t expect that level of support this early.

Really appreciate everyone who checked out Recost, tried it, or dropped feedback.

Now we’re shifting into the next phase, polishing the product based on what you’ve told us. That means tightening the core experience, improving insights, and making it actually useful day-to-day instead of just “cool.”

If you’ve used it and have thoughts, good or bad, we want all of it.

Anything helps, whether it’s friction during install, confusion in the UI, or issues you ran into while using it.

And if you never ended up using it, why?

Please share anything.

81 views

Add a comment

Replies

Best
Evan Cooper

Is the main challenge here more about surfacing API cost breakdowns or actually helping teams act on those insights?

Donggyu Yoon

@evan_cooper1 Thank you for the question!

As you mentioned, both are real problems. Teams need visibility into API costs, but also help turning that visibility into action. Right now, we surface API costs in the dashboard and scan the codebase to predict production usage. We’re now working on an AI system that analyzes logs, suggests optimizations, and can connect via MCP to your llm in order to further the actions taken on these insights.

Ian Maxwell

Do you see Recost as a monitoring tool or more like a cost optimization platform long term?

Donggyu Yoon

@ian_maxwell2 Hey Ian,

We’re building Recost to solve both problems: giving teams visibility into where API costs are coming from, and helping them act on those insights.

Right now, we surface API cost data in the dashboard and scan the codebase to predict production usage. We’re also working on AI systems that analyze logs, suggest optimizations, and connect through MCP so teams can turn those insights into actual fixes.

We believe a real solution should solve the whole problem, not just one part of it.

Leah Josephine

If you had to prioritize one improvement from early feedback, what has come up the most so far?

Donggyu Yoon

@leah_josephine Hey Leah,

One of the main pieces of feedback we received was that setting up Recost felt a bit difficult. We addressed that by adding clearer instructions to the documentation page, so users have a smoother and lower-friction onboarding experience.

That said, we’re also trying to gather more feedback on the product itself so we can keep improving the core experience, not just setup.