EDIT 2026-05-03: v1.0.0-rc.14 is out and adds a native Android app.
Full announcement: https://lemmy.world/post/46382994
(original post below)
Hey all, sharing what I’ve been working on. NutriTrace is a self-hosted nutrition and wellness tracker that runs entirely on your own server in a single Docker container.
I built it because every commercial nutrition app has the same shape. You hand them years of food data, body measurements, and biometrics, and your data is held hostage when they pivot or paywall. I wanted to track macros and pull in my Fitbit data without participating in that.
Daily food diary with multi-ingredient meals, recipes, body stats, water tracking, day-level notes. Personal food database, barcode scanner, imports from Open Food Facts and USDA, plus optional Mealie integration. Statistics with trend charts, full backup, exports as CSV / JSON / full ZIP.
Optional wellness device sync from Fitbit, Withings, Garmin, and Android Health Connect. Sleep / readiness / stress scores computed from your data.
Optional AI assistant where you bring your own Claude / OpenAI / Gemini key. It queries your real data via tool use so it can answer things like “what was my average protein this month” without making numbers up. There’s a voice food logger too. Both fully optional, off by default.
Tech: Svelte 4 + Express + better-sqlite3, multi-stage Dockerfile, AGPL-3.0. Native Android app is in active development; PWA installs to home screen on any modern browser today.
Repo and docker-compose example: https://github.com/TraceApps/nutritrace
Happy to answer questions.
This sounds great. How does the device support work? What do you think of GadgetBridge support?
I have exports of my nutrition and weight info from other apps as csv files, and I’d like to import that data if I can. It looks like Nutritrace can export to csv but not import that. There is the option to import from a json backup though. If I can massage my data into that json format, does it seem reasonable to use that as a way to import my historical data?
If the answer isn’t “omg don’t do that”, then I have a couple of questions about the json:
- Does each item in the diary array require a matching foodList/meals/recipes entry? Or could I just generate items in the diary array?
- How much do I need to worry about IDs? The “import JSON” option says that it merges with existing data; how would it handle ID conflicts (which I assume could happen normally when exporting and importing anyway)?
- Are there any gotchas you can think of that I should watch out for?
The JSON-massage route may work. Diary items are self-contained snapshots, IDs in your file are ignored on import, and the only real catch is that re-importing a date overwrites the existing entry. Happy to drop the field-by-field shape if you want to go that route.
That said, native CSV importers for the popular apps (MFP, LoseIt, Cronometer, etc) are now on the near-term roadmap (thanks to your suggestion) as the proper path for this. If you can hold off a bit (and use one of the above), that’ll be much easier.
If you’re going to work on CSV import anyway soon, then I’ll just wait. Thanks!
Import feature has been added to app as experimental in latest build (1.0.0-rc9). Please test and let me know how it works for you.
I gave this a shot, but when I press the “preview” button I just get a little popup that says “Invalid CSRF token”.
I gave this a shot, but when I press the “preview” button I just get a little popup that says “Invalid CSRF token”.
Hmm… i think i see the issue. The preview / commit upload was missing the CSRF token, so the server was rejecting it before it even read the file. Just pushed a fix. Once you pull it down, hard-refresh the page (Ctrl+Shift+R / Cmd+Shift+R) to grab the new bundle and try again.
Ok, I can import the file now, but some entries are getting messed up. This line, for example, shows up in the diary with the amount “NaNg · 722903 kcal”. And as much as I would like to eat Ginger Peanut Chicken until numbers fail to describe my gluttony, I just can’t afford that many calories.
Day,Group,Food Name,Amount,Energy (kcal),Alcohol (g),Caffeine (mg),Oxalate (mg),Phytate (mg),Water (g),B1 (Thiamine) (mg),B2 (Riboflavin) (mg),B3 (Niacin) (mg),B5 (Pantothenic Acid) (mg),B6 (Pyridoxine) (mg),B12 (Cobalamin) (µg),Folate (µg),Vitamin A (µg),Vitamin C (mg),Vitamin D (IU),Vitamin E (mg),Vitamin K (µg),Calcium (mg),Copper (mg),Iron (mg),Magnesium (mg),Manganese (mg),Phosphorus (mg),Potassium (mg),Selenium (µg),Sodium (mg),Zinc (mg),Net Carbs (g),Carbs (g),Fiber (g),Insoluble Fiber (g),Soluble Fiber (g),Starch (g),Sugars (g),Added Sugars (g),Fat (g),Cholesterol (mg),Monounsaturated (g),Polyunsaturated (g),Saturated (g),Trans-Fats (g),Omega-3 (g),ALA (g),DHA (g),EPA (g),Omega-6 (g),AA (g),LA (g),Cystine (g),Histidine (g),Isoleucine (g),Leucine (g),Lysine (g),Methionine (g),Phenylalanine (g),Protein (g),Threonine (g),Tryptophan (g),Tyrosine (g),Valine (g),Category 2026-04-20,"Lunch","Ginger Peanut Chicken","750.00 g",963.87,0.00,0.00,202.97,411.64,438.18,0.54,0.84,24.82,1.63,1.88,1.54,142.39,1074.55,62.64,2.52,4.13,39.04,547.85,0.77,12.70,252.20,1.97,913.92,2259.83,76.25,1861.40,6.73,38.20,55.08,16.50,12.52,1.88,9.13,17.86,7.79,45.73,236.74,16.68,10.61,7.96,0.08,3.19,3.15,0.02,0.01,6.92,0.05,6.82,0.88,1.93,3.15,5.60,5.57,1.68,2.96,85.62,3.14,0.78,2.56,3.38,"Meals, Entrees, and Sidedishes"Also, there’s a bit of layout weirdness when reimporting days:
Thanks for catching this. The Cronometer adapter was treating the parsed gram count as a serving multiplier, so a 750g entry got its calories multiplied by 750. The “NaNg” had the same root cause: the portion was stored as the raw string “750.00 g”, which JS coerces to NaN when the diary tries to multiply it for display.
The layout overlap on the duplicate-day dialog is should now be fixed too (added a divider so the buttons have proper visual separation from the radio options).
Both are hopefully now fixed and pushed in rc.14. Grab the latest package, delete the affected day from your diary, and re-import. Items should hopefully now come in with the right values.
Thanks again for the detailed report.
Thanks for sharing! I’m so annoyed of Yazio, that I was close to start developing a simple calories tracker myself. Glad I can just use this instead.
You asked for feature ideas in a comment. How about OIDC support? My wife is good at forgetting (to add) her passwords (to a password manager). So instead of resetting password xyz each week, i installed pocketid and integrated it to every app I host, that supports OIDC.
OIDC has been planned, but since now i have had multiple requests, i have started working on it. Will be implemented most likely in next RC release. Keep an eye out!
Awesome! Thanks
OIDC feature has been added to app in latest build (1.0.0-rc9). Please test and let me know how it works for you. I successfully tested with Authentik.
Thanks for implementing it that fast! Unfortunately I wasn’t able to test it.
I found the new section in the readme. So I followed it. I created an admin account (which confused me a bit - my user already had admin permissions. So why is it necessary to create another admin user?). Then I wanted to logout and login with the admin again. But I wasn’t able to figure out how to log out. So I just deleted the cookies and local storage.
After that I was greeted by the login page. So I logged in as admin, entered the User Management - and found an interface to manage users. Ok, sounds logic to find a user management tool in the “user management” menu entry. But the readme said, that there should be oidc settings. Maybe they got lost in a merge conflict or something like that. I was testing on rc12.
Anyways I would prefer an env variable to configure oidc. I like to separate the technical configuration (like credentials, etc) from the user space configuration.
This comment may sound super negative, but I’m actually very grateful you addressed this feature. Thanks!
Hey, can you make a much simpler version of this? Just a static site of the USDA data?
The USDA nutrition site went down at some point during Trump’s term. and I was afraid that information was lost forever.
I wish we just had a simple way for folks to clone this website. Literally just that. It would be much simpler than what you’ve already done, and extremely useful.
Sqlite only? Edit: confirmed. And it’s written in a way that it will likely only support sqlite in the near future
Ooh, I’ll definitely give this a try.
This looks very interesting. I’ll have to load up the container and give it a try at some point in the future. Big fan of the mealie integration since I use that for all my recipes.
This is wonderful!
Going to set it up tomorrow and give it a go!
Is there a place where we could help with translation ?
I know a few people that would want an app like that but English is not their primary language and won’t bother checking it out at all without some kind of translation.
Is there a place where we could help with translation ?
I know a few people that would want an app like that but English is not their primary language and won’t bother checking it out at all without some kind of translation.
Great question, and not yet. NutriTrace is English-only right now, and the UI strings are hardcoded throughout the Svelte components. To accept translations I’d first need to wire up an i18n layer (svelte-i18n is the obvious pick) and extract strings to per-locale JSON files. Then translation contributions become straightforward via PRs or something like Weblate/Crowdin. I will add this to my roadmap. Any languages in particular we should prioritize?
Personally I’m more than happy to cover the Dutch translation if you have the time to get translations working. Thanks for the project!
Happy to help with German. I used to get the LoseIt premium for free but haven’t used it in many years. I just assume it’s a privacy nightmare so haven’t bothered opening it. But I like the concept, just tracking helped me improve my diet and health.
Thanks for the offers to help with translations. Wanted to share the plan.
I’m wiring up the translation infrastructure now: svelte-i18n with one JSON file per locale in the repo. The workflow once it’s ready is straightforward. There’ll be a single English source file at src/i18n/en.json, contributors copy it to their locale (fr.json, nl.json, de.json, etc.), translate the values, and open a pull request. Keys stay untouched, only values change.
Nothing to do right now. I’ll open a GitHub tracking issue once the source file is stable enough to translate against. A short contributor guide will land with it covering workflow and conventions.
One thing worth flagging early: for nutrition labels specifically, please plan to use the regulatory terms that appear on food packaging in your country rather than the literal English equivalents. So Glucides / Lipides / Protéines for French, Koolhydraten / Vetten / Eiwitten for Dutch, Eiweiß rather than Protein for German, and so on.
More soon.
What does the mealie integration enable? I assume it’s providing foods that can be logged, but can you also pull stuff from mealies meal planning section & populate it into the diary?
Mealie integration allows you to pull in your Meal/Recipe from your self hosted instance of Mealie via api. If you have nutrition facts set there by the recipes total weight, it will pull in that data and then you can set your serving size accordingly so it calculates properly. It also pulls in the recipe pic if set in Mealie.
Great project. Looks like a lot of time went into it. I may give it a spin later on this evening. You included screenshots. Thank you for that.
Vibe coded, innit?
Yeah, the first commit is 47k SLoC, and Claude is mentioned as a “co-author”.
Yes, vibe coded and proud of it. This is a labor of love that I genuinely don’t think I could have completed without Claude Code. The first commit is large because I was working out of a private dev repo and synced everything to the public repo just before the 1.0 RC release. Hope you give it a chance and that it suits your needs. Thanks!
How well would this work internationally? More a question on the resources but does open food facts log international barcodes? I knowour stuff is way different to the same product stocked in the US.
Barcodes work internationally. i can confirm because i have used in both europe (italy) and africa (south africa). Only difference between nutrition facts i see is that the US uses Sodium and i want to at least Europe uses Salt. I have a built in conversion where when one is used the other is automatically calculated.
This is perfect, thanks for sharing.
As this is a new project, have you considered hosting your code somewhere other than GitHub? Codeberg and GitLab are similarly user-friendly platforms without the many downsides of supporting Microsoft.
At least a clone. GitHub is authwalled even for GET requests more and more these days
