A small company with a specific idea.
Two problems have the same solution and almost nobody builds for both. Senior living communities cannot lay eyes on every resident every morning. And outside those walls, people of every age can go a week without a real conversation — a fact the Surgeon General called an epidemic and most of us still treat as a personal failing.
A phone call that listens properly helps in both cases, and the hard part of building one is identical either way. Communities license it because it earns its place in their operation — every resident heard before rounds, concerns surfaced while they are still small. What they pay for is that product and the work behind it.
And because the engineering already exists, the charity can run the same engine without anyone having to fund it twice. One build, doing two jobs, neither at the other's expense.
The company
Facts, without decoration.
| Legal name | kAIndness LLC |
| Form | Limited liability company, organised in California |
| Principal place of business | Los Angeles County, California |
| Founder | Richard Yale |
| What it owns | The voice platform, the conversation engine, the escalation system, and the GRACEful CheckIns product built on top of them |
| How it earns | Licensing GRACEful CheckIns to senior living operators. The technology given to the charitable arm is not a revenue line and never will be. |
| Stage | Pre-launch. Enrolling founding communities. |
| Contact | hello@kaindness.org |
Richard Yale
Founder.
Richard founded kAIndness LLC and built the system himself — the telephony design, the speech pipeline, the conversation engine, the escalation logic, the staff dashboard and the family view. Not a specification handed to an agency. The code.
That matters more than it sounds. Most software sold into senior living is assembled from components by people who have never had to make a language model stop giving advice, or worked out why a synthesised voice hisses in a hearing aid, or decided what a system should do when a resident says something about a member of staff. Those decisions are not configuration. They are the product.
He serves on the board of The kAIndness Project, the nonprofit that distributes the free version.
- Safety is deterministic code, not a model prompt.
- The escalation check runs every turn, not on a summary.
- Memory exists to be kind with, or it is not used.
- Idle cost under a dollar a day is a constraint, not a target.
- Say what is built and what is not.
The kAIndness Project, and the wall
A royalty-free licence crosses. Nothing else does.
Nothing crosses
this line
The kAIndness Project is a California nonprofit, currently in formation, whose purpose is to provide free companionship calls through kAI — to adults of any age, starting in California and going as far as we can reach. kAIndness LLC licenses it the software royalty-free. Beyond that licence, the two organisations share nothing.
What crosses
A royalty-free, one-way software licence, and the trademarks needed to operate under the kAIndness and kAI names.
That is the complete list.
What does not
- Money. No payments in either direction. Each entity pays its own vendors from its own accounts.
- Conversations. Nothing said to kAI — no transcript, no summary, no flag, no usage count, not even whether someone answered — can appear in any LLC system.
- Infrastructure. Two deployments, two sets of cloud accounts, no shared memory store across tenants.
- The assistant itself. GRACE and kAI are separate agents with separate names and separate rulesets, not one system with a flag flipped.
Why we are strict about this. The obvious temptation with a structure like ours is to let the charity feed the business — a referral here, an anonymised insight there. It would be worth real money and it would be a betrayal of every person who called kAI because it was the one place nobody was taking notes. Building the separation into the architecture, rather than into a policy document, is what makes it something we cannot quietly stop doing.
If a senior living community wants to tell a resident's family about kAI, the product can show them a door — a link to the nonprofit's own enrolment form, with the nonprofit's own terms and consent. What comes back is the fact that an account was created, and nothing else. No activity, ever.
Which name means what
Five names, kept apart on purpose.
| Name | What it refers to |
|---|---|
| kAIndness LLC | The company. Owns the technology, employs the effort, sells the product. |
| GRACEful CheckIns | The commercial product for senior living communities. |
| GRACE | The assistant inside that product. Gentle Residential Assistance & Care Engagement. |
| The kAIndness Project | The nonprofit. Separate entity, separate accounts, separate funding. |
| kAI | The free companion the nonprofit offers. Never used for anything commercial. |
A resident in a paying community is talking to GRACE and should know that what they say may be passed to staff. A person at home is talking to kAI, and nobody is listening but kAI. Giving both the same name would blur exactly the line that needs to stay sharp.
Where we are. GRACEful CheckIns is pre-launch and no community is live. The kAIndness Project is in formation and has not received a determination letter. Nothing on this site should be read as describing a system currently handling anyone's information.