Calm over noisy
Tracking should not feel like punishment or homework.
Join betaAbout Basentra
Built from one personal question: is this actually helping me?
Basentra did not begin as a company idea. It began as a personal attempt to understand whether a routine change was making a real difference — or whether the answer was hidden somewhere else in the day.
Where it started
It started with a supplement and a question I could not answer.
I had started a digestion-focused supplement routine and wanted to know if it was actually helping. Some days felt better. Some did not. But I could not tell whether it was the supplement, the food I had eaten, how well I had slept, how stressed that week had been, or just normal variation.
Memory was not enough. Good days and hard days blurred together after a few weeks, and trying to hold all the context in my head meant I was always guessing. I needed a clearer way to record what was actually happening — not just the supplement, but everything around it.
The first problem was not tracking everything — it was understanding what the surrounding day looked like.
What I kept noticing
The answer was never in one log. It was always in the whole day.
When I started capturing the surrounding context — what I ate, how I slept, how stressed I was, what else had changed that week — patterns started to become visible. Not always clearly, and not from one day. But across enough ordinary days, something useful emerged.
That became the core idea: keep the surrounding signals close to the log they may help explain. Not because every signal matters every time, but because you cannot know in advance which ones will matter when you look back.
Who I am
I come from IT and engineering, not medicine.
My background is systems thinking — inputs, outputs, load, recovery, signals and reviewable records. I am not a doctor, dietitian or clinician, and I have never pretended otherwise.
That background shaped how Basentra works. I did not want to build a tool that told people what their numbers meant. I wanted to build one that made their own records easier to return to — so they could notice patterns themselves, with more context and less guesswork.
The body is not a simple machine. But daily life still creates signals worth recording carefully.
01InputsWhat happened: meals, supplements, movement, sleep, routines.
02SignalsWhat you noticed: energy, digestion, mood, cycle context.
03ReviewWhat repeated: patterns that only emerge across days and weeks.
What it became
Basentra is the product that question eventually needed.
After enough time logging ordinary days, something changed. The records stopped being isolated entries and started becoming a reference point — something to compare a new week against instead of comparing it against memory.
That is what baseline means in Basentra. Not a score. Not a target. A personal context that builds gradually from real days — and makes future days easier to understand in comparison.
The app started as a tool for one question and became a product for anyone who has ever wanted to understand whether something they changed was actually making a difference.
What it stands for
Four things I want Basentra to stay true to.
These are not product features. They are the commitments I made to myself when I started building — and the ones I return to when a decision is unclear.
Context over blame
One signal rarely explains a whole day.
Personal over generic
Your baseline should reflect your life, not someone else's average.
Careful by design
Basentra is not medical advice, diagnosis or treatment.
The reason it existsJoin beta
Ordinary logs deserve a clearer place to live.
I built Basentra because I could not find a calm, connected way to record real days and look back at them with context. Not to diagnose. Not to optimise. Just to understand what was actually happening — and whether the things I was trying were making any difference.
If that question sounds familiar, Basentra is for you.