Why DishKeeper exists

Why DishKeeper exists

I got tired of rewinding recipe videos and scrolling through long websites just to find the ingredients and instructions. So I wrote a script that turned recipes into clean, consistently formatted documents: no ads, no clutter, and the same structure every time.

At first, I printed those documents. Eventually, I no longer wanted to maintain a paper cookbook, so I built an app for my household instead. Making DishKeeper publicly available made it easier for me to access my recipes and share them with friends and family. If it is useful to other people too, even better.

How features are chosen

DishKeeper is a personal project, and I mainly add features that I need myself. If you find the app useful but feel that one important ingredient is missing, let me know. I cannot promise that every suggestion will be implemented, but I am happy to consider ideas when I have the time.

What it costs to run

I cover the basic server and domain costs because I use DishKeeper myself. However, importing and generating recipes from videos and other sources relies on third-party services that charge money, require subscriptions, or both.

Opening the app to more people also increases the cost of maintaining reliable performance, uptime, and output quality. When you purchase tokens, you help cover those usage-based costs and keep the service running.

Advertising

Your cookbook and finished recipes will never contain ads. These are the parts of DishKeeper you use regularly, and they should remain clean and distraction-free. Adding advertisements there would go against the reason I built the app.

The only place where I may consider showing an advertisement is during the recipe-generation step, what I call “Recipe Magic”, to help offset processing costs. If that happens, ads will remain separate from your cookbook and the recipes themselves.