Software was designed for a brain that doesn’t exist.
Hours present do not equal work possible. When software assumes steady attention, people with variable capacity have to do the adapting themselves: mute the noise, simplify the view, and decide what can wait.
That extra work consumes the same capacity that was already limited. Most software never notices it.
Needing a different interface is not a discipline problem. It is a design requirement.
Energy is not time.
Seventy-five focused hours can produce more than a hundred and sixty depleted ones.
A calendar tells us how much time is available. It does not tell us how much cognitive capacity is available inside it. Every Kumbatio tool starts with that difference.
- wh · work hours
- time you were present
- ph · productive hours
- hours when focused work was possible
ph ≤ wh
AlwaysThis page is already doing it.
Everything you are reading runs on energy-system - the same open-source engine that ships in our apps. No settings page, no account, no demo video. The page you are on is the demo.
Try the levels and watch what changes. The same state and strategies are available to any app that builds on it.
Set it here - we’ll wait
What moves when you do
- type weightfollows your level, 900 down to 400
- palettedims toward candlelight as you deplete
- density & motionreduces at lower levels
Nothing is dropped. At low energy the page says less - it never says it worse.
One model. Different tools.
The products do different jobs. What they share is one energy state and the same rule: the person sets their capacity, and the software responds.
Anasa
A local-first workspace whose interface adapts to the energy you bring to it.
MPath
Project and work coordination that plans against actual human capacity.
Nami
A cognitive support copilot for the days executive function runs low.
energy-system
What our apps run on. Open source, free to build yours on.
The engine runs outside this product line too, at entro314 labs, the studio behind Kumbatio: Meltemi, an email client in private beta, plus Entromail and Equidock, both pre-release. Each uses the SDK without adopting the rest of the Kumbatio product line. Ask for an invitation.
What we commit to.
Trust does not come from a promise on a landing page. These are product choices you can check in the source and in the software itself.
- 01
An open foundation.
The energy-system SDK and specification are open source. You can inspect, test, and fork them.
- 02
Your data is not for sale.
We do not sell personal data. You can ask to access, correct, or delete the data we hold.
- 03
AI that asks first.
AI features are opt-in. Anything that speaks or acts for you requires your consent.
- 04
No hidden energy scoring.
You report your own capacity. Software must not infer it unless you explicitly opt in.
Kumbatio · available now and in development
Rest is not a bug.
Join the waitlist for release updates and invitations to products that are still in development.
The energy setting stays in this browser. This page does not need an account to adapt.
