RoastRecipeAdvisor public beta is now open

Roasting on the Bullet
1

We’ve been working on a new web app called RoastRecipeAdvisor, built for Aillio Bullet users who roast from RoasTime recipes and want a more practical way to review repeat roasts.

The app connects to your Roast.World account with your API token, syncs your roast history and bean information, and lets you import your local RoasTime recipes. From there, it compares the roast curve against the recipe context and looks for practical recipe adjustments, such as moving a Power or Fan step earlier or later.

The goal is not to replace your judgment. It is to give you a clear second set of eyes on recipe-driven roasts and help answer:

  • Did this roast look stable?
  • Was first crack timing reasonable?
  • Was DTR in the intended range?
  • Did the curve show a meaningful dip, crash, or late flick?
  • Is there a specific recipe change worth testing next time?
  • Or does the curve look good enough that no recipe change is recommended?

A few important notes:

RoastRecipeAdvisor is focused on recipe-based Bullet roasting. If you roast manually without a saved RoasTime recipe, the app will not be able to do its main job because it needs recipe steps to connect curve behavior to a repeatable change.

The app is intentionally conservative. It may say no recipe change is recommended. Small RoR wiggles that recover quickly are treated as normal unless the broader roast context suggests a real problem.

RoastRecipeAdvisor does not change anything in Roast.World. The Roast.World connection is read-only. Recipe edits are still made by you in RoasTime.

The beta is free. There is no payment setup. The purpose of this stage is to let real Bullet users try the workflow, report rough edges, and help refine the app before any broader release decisions are made.

You can try it here:

https://app.roastrecipeadvisor.com

Basic setup:

  1. Create an account.
  2. Verify your email.
  3. Connect your Roast.World API token.
  4. Sync your roasts.
  5. Import your local RoasTime recipe folder.
  6. Open a roast from the dashboard and review the graph, whole-curve analysis, and recommendation.

There is also a Support page inside the app. Please use it for questions, bugs, confusing results, or suggestions. If something does not make sense, we would rather hear about it than have anyone assume the app is “just doing something weird.”

Thanks to everyone willing to test it. The best feedback will be specific examples: the roast name, what the app said, what you expected, and whether the recommendation made sense based on your own roasting experience.

Happy roasting,
The RoastRecipeAdvisor Team

3 Likes
2

That’s a coool idea. I’ve created something similar for me personally, based upon a Claude Code Project. It’s working but the scope is different.
Like your idea! Will try that.

3

I encountered that the analyser is only suitable for batch sizes up to 850 grams. The R2 Pro is easily capable of 1,2kg (1200 grams).

4

@secuspec
You are right — thank you for pointing that out.

The analyzer engine limit was set conservatively during early testing on the R2, but we have updated RoastRecipeAdvisor so R2 Pro batch sizes are not blocked simply because they are above 850g.

The analyzer may still be cautious with larger batches while we gather more beta data, but you should now be able to review and get recommendations for those roasts instead of being stopped at the 850g limit.

We appreciate your feedback!

Happy roasting,
The RoastRecipeAdvisor Team

5

That’s great and highly appreciated! :pray:
Let’s see to what conclusions it comes when comparing it with my own analyses.

6

Quick update to RoastRecipeAdvisor:

We made a refinement to how the app handles setup and preheat guidance.

Previously, when the analyzer believed the first thing to review was setup/preheat rather than a recipe step, the message could be too general. It might tell the user that setup review was suggested, but not clearly explain what to do next.

The app now gives more concrete next-roast setup guidance when the roast context supports it. For example, if the roast appears to have reached first crack much earlier than the active target, the app can recommend a more specific preheat/baseline adjustment instead of simply saying that setup should be reviewed.

We also added guardrails because first crack marking is somewhat subjective. The app now weighs the marked first crack against the estimated first crack and the strength of the curve signal. If the curve does not strongly confirm the marked first crack, the app avoids making an overly aggressive recommendation. The goal is to give a useful target correction without wasting multiple roasts on repeated small adjustments.

This is a setup/preheat guidance improvement only. It does not change the basic recipe-edit workflow or the broader recommendation structure.

Happy roasting,
The RoastRecipeAdvisor Team

1 Like