Hi everyone, I m Bruce, the maker of RecipeCat. I m building a tool to help people work through the steps between a recipe and a packaged food-product plan.

I d like feedback on a specific product-design question: how should an app present an early cost estimate when some inputs are still assumptions?

In our recorded example, a proposed 227 g sauce bottle has an estimated unit cost of $5.42. That provides a starting point for exploring pricing, but supplier prices, packaging, actual yield and production quantity can change the result. Manufacturing partners still need to confirm feasibility and final pricing.

My view is that a single total is easy to understand, but it can hide uncertainty. I d favor an itemized estimate with editable assumptions and a clear distinction between estimated costs and confirmed quotes. Showing a range is another option, though that range also needs a defensible basis.

Sharing a free, open-source library I maintain for .NET microservices.

The problem: an order DTO has a UserId, and you end up calling the user service, batching the ids and copying Name and Email back by hand, again and again.

How FxMap does it: the service that owns the data says how an entity is exposed. In the DTO you write a profile: this key fills these fields, optionally with a small expression such as Country.Name. Then one call to MapDataAsync on a list sends one request per key, not one per object. It works over gRPC, NATS, RabbitMQ, Kafka, Azure Service Bus and AWS SQS, reads from EF Core or MongoDB, and has a HotChocolate (GraphQL) integration.

Honest limits: .NET only (8, 9 and 10), gRPC calls have a fixed 3 second timeout in the current version, and the test suite is 826 tests with about 62% line coverage. Load test numbers and a benchmark are on the Testing page of the docs.

Hey Product Hunt,

I'm building APILens, a Node.js API observability tool.

I'm an indie developer from Japan, and I just launched Kaikoku.

The short version: I found a notebook I wrote in junior high full of an entire "magic system" I invented (twelve zodiac spells, solar arts, seal-curses). Pure chuuni, that fantasy-prone teenage phase. Instead of cringing, I decided to actually build it.

Kaikoku is an antique pocket watch that lives in your palm. The chain swings on real physics. Snap the hunter lid shut and magic charges; open it and the day unseals. By night you wind the dial to cast one of twelve arcana; by day the sun answers with solar arts. Every hour it checks its keeper via Face ID.

Underneath all that staging, it's a genuinely functional clock app: alarms with six bells, a timer, a chronograph with Live Activities, an Apple Watch companion, widgets, and StandBy. The fantasy is the skin; the timekeeping is real.

Hey, I am a solo maker of Screen Records Mac app.

If you need to record your screen often you know the problems: heavy recorders, monthly subscriptions, need to edit everything separately for each social, then generate captions in another app.
Many recorders are just inconvenient. I tried 9 and bought 1, because I thought making own one is not worth it.
But I had to do it anyway, since app I bought just didn't work right.
So now I'm building a lightweight native MacOS screen recorder with built in editor. One-time purchase. Nothing extra for captions and MCP for your favorite AI subscription to open projects, edit and export them in front of you. Plus a lot more nice convenient features you may expect from screen recorder.
Every change can be undone, app never spoils original footage. Every track can be edited separately (mic, video, voiceover, system sound, camera).
Zooms and background changes are in too. You can even paste media into recording, change places of video parts.
Give it a try: free version available and lifetime deal now is only $29.
Please share, what would make demo recording effortless for you?

I m launching the new version of Inquir Compute on Product Hunt today.

It started as a serverless runtime. This release adds container apps and databases, so a web app, its database and background work can live in one workspace.

• Deploy from GitHub, a Dockerfile or a container image.

• Connect Postgres or Redis over a private network.

• Run functions and scheduled workflows alongside your app.

• Check releases and logs from the console or CLI.

I d like feedback on the first deployment. What would you need to see before trusting a new platform with a small project? A working example, clearer pricing, migration docs, or something else?

Hi everyone. I run PrintSheetLab, a free site for teachers and parents.

It has 1,300+ printable worksheets with answer keys, plus makers for math worksheets, bingo cards, word searches, flash cards, graph paper and calendars. No sign-up and no ads.

https://printsheetlab.com/

Most worksheet sites give you a fixed PDF. Here you pick the number range, print several versions of the same sheet, and the answer key is on page 2.

Hey Product Hunt community

After months of late nights, testing ideas, and rebuilding things more times than I can count, I finally launched something I ve been dreaming about for a while: Vegalyx.

For years, the gold standard in personal finance apps has been linking your bank account, storing data in the cloud, and paying $10/month for a subscription.

But lately, there seems to be a major shift. Many users are experiencing payday friction with traditional apps:

1. Privacy Concerns: Sharing bank credentials with third-party aggregators feels increasingly risky.

2. Over-Engineering: Having a simple payday budget turned into complex setups with forced account creation and endless ads.

3. Data Ownership: If a cloud service shuts down or changes its pricing, your entire history is locked in.

We decided to test a different approach: building a 100% offline, privacy-first mobile budget tracker (Jetpack Compose, native CSV/JSON export, zero cloud tracking).

Per-agent? Per-seat? Per-query? Usage-based? Flat rate?

I've changed my pricing model 4 times in 12 months. Not because

I wanted to. Because the market kept telling me I was wrong and

I kept not listening fast enough.