The one you can tell everything.
Every AI assistant claims to know you. What they mean is that they remember what you typed at them. Neeos has read your documents, your notes, and your health history — the parts of your life that were never a conversation with an AI at all.
Built for iPhone, iPad, and Mac. Beta seats are added by hand — email jake@neeos.ai.
Illustrative screen — not real user data.
Three moves. That's the whole product.
Put your life in
Documents, notes, years of health data — imported once, or flowing in on their own.
Neeos indexes it by meaning
A model running on your own device reads everything you add. Nothing is sent anywhere to be indexed, and nothing trains on it.
Ask like you'd ask a person
It answers from your material — not the internet — with the sources attached so you can check.
Other assistants remember the chat. Neeos has read your life.
The difference is the substrate: a semantic index of your material, built by a model that runs on your own device.
Measured against the running system, August 2026. These are scale numbers from one live deployment — not customer counts.
Your life was never a chat log.
The lease you signed. Years of journal entries. The lab results from the appointment you were nervous about. None of it was ever a conversation with an AI — and most of it never will be. Neeos is built from exactly that material.
"It remembers what you told it" versus "it has read your life."
Watch it gather context, then answer.
This is the actual mechanism, slowed down. Scroll — nothing you haven't already given Neeos, no keyword in sight.
Neeos
Illustrative — a stand-in conversation built to show the mechanism honestly, not a real user's data.
Questions with no search term.
The search is by meaning, not words — so you can ask the kind of question a keyword search cannot even be asked, and get an answer drawn from a document you forgot you had.
Illustrative answers — not real user data.
Four steps, and only one of them is yours.
You add something — upload a document, drag a folder in on the Mac, import your Apple Notes, write a note, or connect your health data once. Neeos extracts the text.
A model running on your own device turns that text into a representation of its meaning. This happens automatically, in the background, on every save.
When you ask a question, the same model finds the passages closest in meaning — not the ones that share words with your question.
Those passages — and only those — go to a model along with your question, and come back as an answer with the sources attached.
The more you put in, the more it can answer. That isn't a slogan; it's the mechanism. Six months in, your Neeos is materially different from a new one — because nobody else has your corpus.
Ask it to update a note. It finds what you meant and writes it in.
The fourth step isn't always an answer — Neeos can act on what it reads, and the edit lands in the actual note, with the source that justified it.
Neeos
Illustrative — a stand-in conversation built to show the mechanism honestly, not a real user's data.
Everything below goes in. Precisely two ways.
Indexed by meaning
- Documents, uploaded from any device
- Folders from your Mac — dragged in, or kept synced to your vault
- Notes you write in Neeos
- Your Apple Notes, imported with their folders
- Documents Neeos writes for you — its own output becomes substrate
- Facts about you, from a screen where you can read and edit every one
Indexing is automatic on save; a sweep catches anything missed.
Answered directly
- Your health data — sleep, recovery, HRV, workouts — from Apple Health, WHOOP and Oura
- Your tasks and goals
- What you actually said in earlier conversations
These are read live rather than through the index — current values on every turn, history one question away.
Seven surfaces. Things go in, answers come out.
Plan a trip, and it connects what else that trip touches.
The same index that answers your question keeps half an eye on what's adjacent to it — nothing hidden, just attached, with its own source.
Neeos
Illustrative — a stand-in conversation built to show the mechanism honestly, not a real user's data.
Three apps, each with its own job.
Real native apps — not one interface stretched across three screens. Each device gets the shape that fits how you actually use it.
Where your material gets in.
- Drag files or whole folders onto the vault
- Keep folders on your Mac synced to your vault
- Import your Apple Notes, with their folder structure
- A menubar item, and ⌥Space for a quick chat over whatever you're doing
- A real word processor — pagination, printing, the works
Ask anywhere.
- Ask from anywhere; dictate instead of typing
- Have a live, full-duplex voice conversation — a real call, not push-to-talk
- Widgets, Control Center, and Siri shortcuts: Ask Neeos, New Note, New Task, Start a Live Call
Kitchen renovation
Contractor meeting, Tuesday — the quote came in at $18,400, about $2,000 over the number we set in March. The overage is the island counter; everything else held.
Timeline slips two weeks if we reorder the counter. Livable — we're out of the house until the 12th anyway.
Next: call Marcus about splitting the electrical into phase two
Read and write.
- The reading and writing surface — full rich text, the word processor, the vault
- Attach a keyboard and the whole app changes shape into a sidebar-and-detail layout
- Detach it, and it goes back to the phone shape
- Everything you write here is index substrate the moment you save
Illustrative screens — not real user data.
Sensitive by definition. Handled accordingly.
The material Neeos is built from is exactly the material you wouldn't hand to a general-purpose chat box. That is why the handling is the way it is:
Neeos reads your documents, your notes and your history, and answers from them. Your data is indexed by a model that runs on your own device, and is never used to train anything. Only what's relevant to your question is ever sent to a model — never your whole library.
The full technical detail — the model that builds the index, exactly what leaves at answer time, and what this architecture is not — is written up for people who will check.
The first day is the worst day.
An empty Neeos is worse than a chat box — the index is only worth what's in it. So the first thing you'll do is put something real in: import your Apple Notes, drag in a folder of documents, connect your health. From there, it compounds. Every document you add makes the next answer better.
What's coming, honestly labeled.
Two tiers, and the difference matters: the first is real code being actively worked on. The second is intentions — and we'd rather label those plainly than let you find out the hard way.
In active development — real code, really moving
"How much did I spend eating out this month?"
Atlas — the money side — already answers questions like this from your connected accounts. It's paused while the core rebuild finishes, not gone: your data is still there and still connected, and it's in testing now. Today, Neeos answers money questions from documents you've uploaded, like a statement PDF.
Write it, don't just type it.
Apple Pencil support across Notes, PDFs, and documents in the vault — handwriting and markup, not just typing and tapping. Being built now.
Add to the vault with no connection at all.
Local models handle the offline half of processing what you add, so getting something into Neeos doesn't require a live connection to start. Being built now.
Ask it something with no connection at all.
Running the language model itself on-device, so Neeos can answer without a round trip to a server. Started, and being built now.
Planned — or, being honest, vaporware for now
Real intentions, zero shipped code. When one of these ships, it moves up a tier and the blog says so:
- Photograph a document straight into the vault
- Index folders on your Mac without uploading a byte
- Obsidian, Day One and Notion importers
- Search as its own screen, reachable from everywhere
- Siri App Intents
- Apple Foundation Models 3.5 Pro and Private Cloud Compute support — waiting on iOS and Xcode 27; expect it in beta mid-September
Curious about any of it? Ask me directly.
I'm Jake — I build Neeos, and I answer my own email. If you want the full technical details on anything here — how the index works, what Atlas will do, or anything else — write me and I'll gladly share specifications, not marketing.
Build notes, posted as they happen.
What shipped and why, drawn from the commit history as the app gets built.
The two-week encryption rework
Why the server holding your key for even one request was ruled out by name, what four phases of rebuilding it actually looked like, and what's still honestly open.
Read the post →Ask it about the thing you would never paste into a chat box.
That's the test Neeos is held to. A small group is running their lives through it now; beta seats are added by hand. Tell us what you'd want it to hold for you.