Elo AI is a small company by deliberate choice. The kind of software we are trying to build does not benefit from a fifty-person engineering org racing to ship the next surface. It benefits from three people who have read the same papers and disagree about the right ones.
Inventor of record on U.S. Provisional Patent App. No. 64/041,821. Architect of the substrate-locality covenant that runs underneath every Elo AI product. Writes the Rust core, the Swift bridges, and most of the marketing copy you read here. Lives in Greeley, Colorado. Has been doing this kind of work for long enough to have opinions about how AI eats data, and small enough to do something about it.
Information security and compliance. Owner of the SOC 2 Type II posture, the HIPAA strategy, and the threat-model lens that gates every release. Doug is the reason "we cannot read your data" is a cryptographic property and not a marketing posture — he asks the dumb question in the security review that makes the smart answer real.
Brand voice, narrative, revenue. Garrett brought the streaming-creator-economy lens that shaped how we talk about ourselves — calm-direct, no exclamation points, the pull-quote earns its weight. Owner of the marketing surface, the founders pre-sale narrative, and the social-media presence as it stands up.
The provisional bundle (parent + P1–P7 + design patent + trademark) is being filed pro se to preserve priority and minimize spend in the early window. Counsel review is engaged at non-provisional kickoff Q4 2026 ahead of the April 16, 2027 conversion deadline.
In late 2025 it became clear that "AI assistant" was going to be the next phase of personal computing — every major operating system, every productivity suite, every consumer app would have one. It also became clear that "AI assistant" was being built, almost universally, in a way that required uploading the user's entire life to someone else's server.
We watched the early rounds — the breaches, the data leaks, the surveillance scandals, the bankruptcy fire-sales of intimate genetic data. We watched the apologies. We watched the next iteration repeat the same mistakes with a new logo. We came to the conclusion that the architecture itself was wrong, not the people running it.
The right architecture is not hard. It just requires choosing inconvenience for the operator over inconvenience for the user. Per-app HKDF-derived encryption boundaries on the user's device. The operator does not hold the keys. The operator never sees the bytes in the clear. The Coach AI works against categorical aggregates, not raw content. The math closes. The privacy promise becomes a property of the file format.
We started Elo AI to ship that architecture. Cognielo is the first place it lands. The Elo SDK is how it spreads. The books are how we explain what we found.
As of April 2026 we are pre-launch. The patent provisional is filed. The non-provisional conversion is on a clock. The first Cognielo build is in TestFlight. The Founders Lifetime pre-sale opens June 24, 2026. Public launch July 15, 2026. The SDK platform follows in Q3.
Every page on this site, every line of code in the repo, every patent claim in the ladder is part of the same project: ship software that lives up to its privacy promise because the math forces it to.
Press, investors, prospective SDK customers, journalists, and people who want to argue with us — all welcome. We try to answer mail.