kAIndness LLC
kAIndness LLCLos Angeles County, CaliforniaLoneliness is an epidemic. We listen.

Someone should call and ask how they are.

kAIndness LLC builds the voice that does it. We make software that telephones someone every day and holds a real conversation — not a script, not a menu, not a survey. It listens, it remembers kindly, and it calls again tomorrow.

The same technology runs in two places. Senior living communities license it as a product. A charity gives it away free to adults of any age, anywhere. Those two things are deliberately kept apart, and this page explains how.

Entity
kAIndness LLC, a California limited liability company
Based
Los Angeles County, California — building outward
Product
GRACEful CheckIns — pre-launch, enrolling founding communities
Charitable arm
The kAIndness Project — nonprofit in formation

One engine, two very different jobs

The hard part is the same whoever the call is for. What differs is who hears about it afterwards.

Hear an 82-year-old on a landline. Keep a conversation going without sounding like a phone tree. Recognise the sentence that means someone needs help. We built that once.

For-profit · kAIndness LLC

GRACEful CheckIns (opens in a new tab)

A daily wellbeing checkin service for assisted living, independent living and memory care. GRACE calls every resident each morning, has a short conversation, and hands the staff a board sorted by who needs attention first — not a pile of transcripts.

Families get their own limited view. Safeguarding concerns take a separate route that never touches the shared board.

gracefulcheckins.com → (opens in a new tab)

Nonprofit · The kAIndness Project

kAI

The same voice technology, given away. kAI phones adults of any age, wherever they are — no fee, no facility, no dashboard, no one watching. It is a conversation, and nothing more is made of it.

Loneliness is not an old person's problem and we do not treat it as one. kAI never gives advice and never quizzes anyone about what they said last week. If a conversation suggests danger, it asks them to hang up and call 911 — and only if the line then goes quiet does it alert their emergency contact. Otherwise it listens.

California first. Everywhere we can reach after that.

How the two are separated →

A company and a charity, not one or the other

The line running down this page is the wall between them. Here it is drawn at full weight.

Nothing crosses
this line

A company alone would have to charge the people least able to pay. A charity alone would spend its grants rebuilding engineering that already exists. So the company builds and maintains the codebase and sells a product that earns its keep inside a senior living operation — and licenses that same code to the charity for nothing.

That only works if the wall is real. It is not a policy we intend to follow. It is two separate deployments, in two separate sets of cloud accounts, with no shared data store and no money moving in either direction.

One codebase Owned by kAIndness LLC royalty-free licence operated directly NONPROFIT SERVER The kAIndness Project Hosts kAI — free companionship calls for adults of any age. Its own cloud accounts. Its own funding. Conversations never leave it. LLC SERVER GRACEful CheckIns Daily wellbeing checkins for senior living communities. A paid product. Separate agent, separate name, separate rules. HIPAA territory. NOTHING CROSSES THIS LINE
One codebase, two deployments, one wall.

Nothing from the charity feeds the product

No summaries, no flags, no usage counts, not even whether a given person picked up. A conversation held with kAI cannot surface anywhere in a paying customer's dashboard. The two systems share a codebase, never a database.

No payments in either direction

Each entity pays its own vendors from its own accounts. The only thing that crosses is the code licence, and it is royalty-free and one-way. No service fee, no cost allocation, no management charge.

Different assistant, different rules

GRACE is not kAI in a suit. It is a separate agent with a separate name, a structured set of questions, a duty to document answers and a duty to escalate. kAI has none of those. Keeping them apart is what makes each one honest about what it is.

Three things we have not moved on

Decided early, and true of everything we build.

  1. Rules run before the model does.Whether a call escalates is not left to a language model's judgement. Deterministic checks run on every turn, in a fixed priority order, and they can override anything the model wants to say. The model handles conversation. It does not handle safety.
  2. Signals, not transcripts.Nobody should have to read a conversation to find out whether it mattered. What leaves a call is the smallest thing that lets someone act on it, and it is built to be understood in the few seconds the person receiving it actually has.
  3. The system says what it is.It is not a person, it does not pretend to be, and it does not claim a life it has not lived. Disclosure is becoming a legal requirement in more and more settings; we would do it anyway, because someone being deceived by a phone call is the failure mode that would end this whole idea.

Where we actually are

Pre-launch, and saying so.

No community is live yet. GRACEful CheckIns is enrolling founding communities and no resident information is being processed by us today. The kAIndness Project is in formation and has not yet received a determination letter. The voice stack runs end to end on development hardware; the production cluster described in our design work is engineered, costed and not yet deployed.

We would rather say that plainly than have you find it out later. The status table sets out exactly what is running and what is still on paper.