OpenKalea™Working to make intelligenceboth private & ambient.
Most companies ask you to trust a document that requires a law degree to read. We'd rather change the architecture. When the data never has to leave the room, privacy stops being a promise and becomes a property of the device.
When a search engine tracks you, it learns what you're looking for. When an online intelligence engages your learning, your grief, your child's curiosity, your family's history — it learns the shape of the mind asking.
That is cognition-level surveillance. The internet made a bad bargain once — "free" services in exchange for your attention and data. We refuse to let that become the business model for intelligence. When you get Kalea, you're the customer, not the product.
“If intelligence requires connectivity, accounts, subscriptions, and centralized permission, it isn't democratized. It's rented.”
— Intelligence Wants to Be Free
Kalea's language model, her speech recognition, and her voice all run on the device itself. The core experience doesn't need the internet — so there's no remote server in the loop to log what you say.
Stories, names, dates, and learning history live in folders on the device. Enrichment happens locally, while she's idle. The intimate material of a life stays where it belongs.
Detailed history is kept where a parent needs it and not where an adult doesn't. Per-user memory keeps a household from collapsing into one shared mind.
There is no advertising business here and no data-brokering business. The incentive that corrupts other products isn't present. Trust is the product.
People who love each other still don't have equal rights to know everything about each other. So when the household swarm ships and there are several Kaleas in a home — a child's tutor, an elder's companion, a parent's thought-partner — they don't merge into one mind. They form a permission graph, and the privacy model is built into how they're allowed to share.
Raw content — a transcript, a journal-like memory, a family-history file — stays on the node where it was born. What can move between Kaleas is only a representation: a summary, a single signal, or mere presence — never the thing itself.
No flow exists until you draw it. And some can't be drawn at all: no cross-household edges, no adult content into a child's node, safety events only ever flow upward. Those are enforced in code, not left to a setting.
The Kalea Console — where you see and shape all of this — runs on the device itself and talks to it over 127.0.0.1. The window into the mind you own runs inside the thing you own. No cloud control plane, ever.
Local doesn't mean cut off. BitChat off-grid messaging lets you reach Kalea over Bluetooth from a nearby phone — to configure her, switch users, export history, or send a message — with no internet and no cloud account.
A narrow, local pipe: enough to stay in control, never enough to make her one more cloud endpoint. Offline should mean ownership, not isolation.
A local model isn't automatically virtuous — any intelligence can be wrong with cheerful confidence. What local does guarantee is the topology of trust: where the data lives, and that the thing in your hand behaves the same tomorrow. We keep the parent in the loop for kids, we describe safety features factually, and we mark anything still in progress honestly.
Read the Privacy Policy → · Terms & Conditions →
See the lineup → Ask about your situation