Run it on your own machine.
Two builds, and we tell you which one you're on.
KnowMessenger has a desktop build that runs the agent as a process on your own machine, against a folder you pick. On that build the model call is made by your own Claude Code or Codex CLI under your own subscription, KnowMessenger holds no key for it, your conversations are written to files under your home directory, and the file-activity ledger is a local database. Spawning an agent is structurally impossible on a deployed stage — a shell there would be a shell on our infrastructure — so this is a property of where the code runs, not a setting.
The hosted web app is the other build, and it is the one a signup lands on. There, your messages go to our server, on to Amazon Bedrock, and the transcript comes back to be stored in KnowMessenger's database under your account. That is a normal hosted product and the privacy notice describes it in full; it is simply not the same thing as the paragraph above, and this page will not blur the two.
Hosted web app
Live todayYour messages reach our server and Amazon Bedrock, and the transcript is stored under your account. This is what signing up gets you today.
Managed Bedrock backend · stored per account
Desktop build: your machine, your CLI
RoadmapThe agent is a local process against a folder you choose, driven by your own CLI on your own subscription. Conversations are files in your home directory. Built and proven; the download is gated on a distribution certificate.
Reach it from your phone
RoadmapOpt-in outbound relay to reach your home brain remotely. Built only on request; on-machine is the default.
The local-agent backend cannot run on a deployed stage at all — our server has no way to reach a CLI on your laptop. So every claim on this page about things staying on your machine is a claim about the desktop build, and it is labeled that way rather than left to be read as the default.
The verifiability claim is always one click from a way to check it — no account, no trust required.