Questions, answered straight.

A private intelligence layer for your Mac: it captures what you say, write and see, connects it into one brain, and puts that brain to work wherever you happen to be working.

No — and the difference matters. A notes app is a place you go to put things, which means it only ever holds the fraction of your day you remembered to file.

Stilou catches things where they already happen: while you are dictating, rewriting a paragraph, taking a screenshot, sitting in a meeting. Nothing needs to be filed, because the connections form on their own.

People holding more than one thread at a time — founders and operators, consultants and agencies, writers, anyone whose work is spread across calls, channels and drafts. If your day is a single task in a single app, you will not get much from it.

No. That is close to the whole design principle. Stilou lives in a keystroke and a bar over whatever app you are already in — you are not being asked to move into a new workspace and maintain it.

It is the unit Stilou thinks in: any moment that carried value. A sentence you said, a line you wrote, a screen you looked at, a decision you made. Dots are close to worthless alone, which is why filing them never worked — and valuable in bulk, once something can connect them.

Dictation, anything you rewrite or act on through the Deck, screenshots, notes and ideas, actions taken through Halo, meetings via Joey, and everything you copy via the Stash. Eight doors, one brain behind all of them.

It is built for real speech rather than dictation-voice — you can talk normally, at pace, and the text comes out punctuated. Private mode transcribes on your Mac; Connected mode uses a hosted model when you want the extra accuracy.

No. Nothing dials into a call on your behalf and no participant sees an extra attendee appear.

Joey captures from your own machine, and only while you have started it. Whether you tell the other people in the room is a decision that stays with you — and in most places, telling them is the right call.

Readable. The text inside a capture is extracted and indexed on-device, so you can later ask for "that pricing table" in plain words instead of scrolling a folder of filenames.

That is the specific failure we built against. Stilou learns your Voiceprint from your own writing, and rewrites aim at the version of the sentence you would have written on a better day — not at generic fluency.

The index underneath everything: your captures, the people and projects they mention, and the links between them. It lives on your Mac and is what makes the rest of the product more than a pile of transcripts.

No. If a system needs maintenance, it eventually stops getting maintained — everyone has learned that the hard way. Entities, projects and relationships are inferred from the material itself.

Slack, Gmail and Read.ai are live today. Calendar is coming. Each one is connected individually, by you, and can be revoked the same way without touching the others.

It means the app pulls the mail into your own local brain so it can be linked to the client and project it belongs to. The index is on your machine. Connected mode sends only the specific slice a request needs — never your mailbox.

From the moment you connect a source forward, plus whatever history that source lets us backfill. The brain gets more useful the longer it runs, which is the honest way of saying week one is the least impressive week.

On your Mac, in a library you own. Your index, embeddings, Voiceprint and captures are local files — searching your own memory does not involve a server at all.

Private mode runs a model on your Mac against your local index. Nothing leaves — it works with the network switched off entirely.

Connected mode sends the specific passage in question to a hosted frontier model when you want more depth than a laptop can give. Which mode you are in is visible in the interface, not buried in settings.

No. Not us, and the providers used in Connected mode are contractually barred from it too. There is no version of this product where your material becomes training data.

No, and we do not intend to. Capture in Stilou is something you do, not a condition you leave running. The always-on recorder has been tried by others, and the reason it kept failing was never technical.

Yes — the app keeps a running egress count. On a Private-mode day it reads zero. A privacy claim you can check beats one you have to believe.

Your library is a folder you control, so removing a single dot, a project or the whole thing is something you can do yourself — no support ticket, no waiting period, no shadow copy retained on our side.

Yes. If you would rather your Connected-mode requests go through your own provider account, you can bring your own key.

Yes, and Private mode is in it. Charging for the privacy floor would mean it was never really a floor.

Depth rather than permission: the full capture toolkit, the Brain with connectors and Signals, Neo everywhere, and Cadence. See the pricing section on the homepage for the current breakdown.

Nothing about your library depends on one — your captures and your index are files on your Mac and stay that way. Where sign-in exists it is there to carry your licence between your own machines, not to hold your content.

Your library is on your disk, so it does not evaporate. What you lose is access to the paid capabilities, not the material you captured with them.

A Mac on macOS 13 or newer. The current build is v0.19.9 and downloads at 47.4 MB.

Not yet. Stilou is deliberately Mac-first — a lot of what makes it feel native is Mac-specific, and a half-ported version would be worse than none. A Windows build is on the map, not on a date.

Not yet. The Mac is where the work and the capture happen, so that is where the whole product lives for now.

In Private mode, completely. Local transcription, local search, local answers — a flight is a perfectly good place to use it.

Yes, current builds update in place. You will be told what changed rather than having it happen silently.

Email hi@stilou.app with what happened and roughly when. Reports from actual sessions are the fastest route to a fix, and they get read by the people writing the code.