The open source home of Kensora
Kensora is an ambient health app that helps people see shifts from their own baseline and understand their own patterns. Project Kensora will open its code so anyone can read it, improve it, and help bring it to more languages and cultures.
Why open source
You will be able to read the code
Privacy claims should be checkable. Open code means the way Kensora stores, syncs, and protects information is something you can read for yourself, not something you have to take on faith. The published tree will omit a small set of third-party materials the project cannot license onward, and will say so.
Languages and cultures need native speakers
Kensora aims to work in the words and norms people actually live in. Community contributors who know a language and a culture from the inside can carry Kensora somewhere no small team could alone.
More hands, faster parity
The Android app is catching up to iOS feature by feature. Contributions are verified against shared behavior contracts, so parity work is checkable, not a matter of opinion.
The license, in plain words
The code will be published under AGPLv3. You can read it, run it, change it, and share your changes. If you share a modified version, or run a modified version as a service that others use over a network, your changes must stay open too.
Before a first change is merged, contributors will sign a Contributor License Agreement. The plan is a license grant, not a transfer: you keep your own copyright and grant Kensora, Inc. the rights it needs to ship the official apps and keep the project's licensing coherent. If you write code for an employer, your employer may own it, so there will be a company form as well as an individual one. The agreement is not written yet. The full text will be published here before any contribution is accepted, and that text, not this page, is the agreement.
The code will be open when the first repository publishes. The Kensora name, mark, and logo will not be. An open source license grants rights in code, not in trademarks, and Project Kensora reserves its marks. Forks are welcome, and they use their own name and their own branding. You can always say truthfully that your project is a fork of Kensora. You cannot call your build Kensora or use the Kensora logo. A TRADEMARK file will publish with the code and will spell this out. The full policy is on the license page.
How contributing works
- Pick an issue. The public repositories will carry labeled issues, including good first issues, translation work, and Android parity tasks.
- Build with the workflow. The repository will ship a public version of the queue driven workflow the core team uses, including the skills for working with Claude Code on your own Anthropic account, at your own cost. Project Kensora is not affiliated with or endorsed by Anthropic. A contributing guide will publish with it and will teach the workflow step by step.
- Tests green, then a pull request. Code standards and test expectations are documented in the repository. Every change runs the same gates.
- Safety surfaces get extra review. Anything touching safety features, crisis related copy, or the logic that notices shifts from a person's baseline goes through Kensora's internal safety review before it ships. Contributors can raise safety findings anytime; final safety determinations always rest with the maintainers.
The full guide, including the ways to contribute without writing code, is on the contributing page.
Translations and cultural adaptation
General interface strings are open to community translation. Crisis related copy is a locked tier: it ships only after the underlying resources are verified for that region and the wording passes Kensora's internal safety and claims review. That slower path is deliberate.
What contributing means
Contributions are public. Merged work publishes under the project's open source license and stays in a public history, along with the name and email in your commits, and we cannot fully remove it later. Contributing is unpaid, and maintainers may decline a change or ask for a different approach. You keep your own copyright under the contributor agreement. The contributor guide and the agreement will cover all of this in full before contributions open.
Found a security problem? Please report it privately rather than in a public issue. How to do that is on the security page.
Status
The program is in its preparation phase: license texts, the contributor agreement, and the scrubbed public export of the codebase are being finalized. The repository links will appear here the day they go public. The full path to publication is laid out on the roadmap page.