Calk is built for people who want useful answers from calorie tracking without turning food into permanent daily paperwork.
Why Calk exists#
Most calorie counters are designed around a diary that never ends. Calk starts from a different idea: food logging should have a job and an endpoint.
A focused month helps you understand the meals you actually repeat, see what changes their calories and nutrients, and turn the record into a Nutrition Report. After that, the weight trend becomes the quieter signal. If the trend changes, your routine changes or you have a new question, you can return for another short food check — without reconstructing the days in between.
That is why Calk uses editable meal templates instead of asking you to search for the least-wrong database entry or trust a photograph to know a recipe it cannot see. The assumptions remain visible, and the final decision remains yours.
Built by Eli Petukhov#
Eli Petukhov is the founder and developer of Calk. He leads the product design, software development, food-data workflow and the research behind the articles on this site.
His work on Calk brings together three disciplines: building a calm product people can use in ordinary life, making complex food data understandable, and testing the product’s claims against evidence rather than marketing convention.
On GitHub, Eli publishes and maintains open-source work as @ispbox.
How Calk publishes#
The standard is simple: say what is known, show where it came from and make the limits visible.
- Product claims come from the product. Measurements such as logging steps, catalog coverage and food-data accuracy are based on the current app and documented methods. When a version or date matters, it is published with the result.
- Nutrition claims need evidence. Articles prioritize original research, systematic reviews and public scientific or health authorities. Sources appear beside the relevant claim and in the shared reference library.
- Uncertainty belongs with the conclusion. An estimate is described as an estimate. An association is not presented as proof of cause. A food diary is not treated as a diagnosis.
- Comparisons should be reproducible. Product comparisons use public documentation and hands-on checks, name meaningful limitations and distinguish an observed feature from an opinion.
This is Calk’s own website, and that relationship is stated rather than disguised. Comparisons contain no paid placements or affiliate rankings.
The articles are educational. They do not diagnose conditions, prescribe treatment or replace care from a qualified professional.
Corrections#
Apps change, food databases improve and scientific guidance develops. When a substantive correction or update changes an article, its modification date changes too.
If you find a factual error, a broken source or a conclusion that reaches beyond its evidence, email us: support@calk.me.
Documents and transparency#
The practical details behind Calk: where the evidence comes from, how data is handled and the terms that apply.