The questions you're actually asking.

You could. I did, over two years. Here's the trap: the memory part is the easy part. Anyone can bolt a notes database onto a chatbot in a weekend, and that is exactly what you get, a memory system that needs babysitting. The two years is turning that into a clone that thinks like you and stays sharp on any machine without rotting. You want to run your business, not become the maintenance engineer of your own brain-in-a-box. And you'd need the machine: 16 GB of RAM is the floor to even install the local stack, not comfort. Nice results take an Apple Silicon Mac with 64 GB, or a serious NVIDIA GPU. Hosted, the heavy models run on datacenter hardware, and your machine does none of the lifting. Klyr is the two years you don't spend.

A file is a dead snapshot. It doesn't remember last week's call, doesn't grow when you decide something new, doesn't follow you across machines. You would spend your evenings feeding it by hand until it rots. Klyr isn't a file you maintain. It's a second you that shows up already up to speed and gets sharper as you work.

Built-in memory is real, and good: it learns your preferences from your chats, inside one app. Klyr goes two layers deeper. One, it doesn't just note a few preferences, it builds a living model of how you actually think and work, on top of the identity you author yourself, so it acts like you, not like a tool that caught a few facts about you. Two, the part built-in memory has no answer for: your whole past, carried with you. Import your history from ChatGPT, OpenClaw and your other AIs, add the work you do with your clone, and your own notes vault, all kept on a timeline so last year and last week never blur into one. That's your second brain, not a chat summary. And it's yours: self-host it, take it anywhere, it never lives locked inside one app.

I ran both, for months, so this is my experience, not a spec sheet. OpenClaw started brilliant, then for me it rotted: pile on enough memory and it began hallucinating, mixing up my clients, contradicting decisions I'd made the week before. And I became its full-time babysitter, pruning, patching, restarting, a second job I never asked for. Hermes "fixed" that by capping its own memory, which to me is just a goldfish with a smaller bowl: it stays sane by staying dumb, forgetting you on purpose. Both buried me in flashy features that looked powerful in a demo and did no real work for me. And there's a structural risk worth knowing: an AI vendor has already restricted third-party tools on its subscriptions once, and could again. Klyr doesn't run as an outside harness that pipes your subscription out. It runs inside the AI vendor's own app, the supported path.

It's yours, and you can see it. Klyr only remembers what you give it inside Klyr, never your whole machine or your files behind your back. You can read, edit or wipe any memory, anytime, it's not a black box. It lives on your own machine, or your own private space in your region if we host it. When your clone thinks, it sends only what that question needs to your AI, on the AI subscription you already pay for. No extra AI bill. We never read it, never train on it, never sit in the middle. You're the customer, not the product. Nobody gets a window into your head but you.

In your own private space, hosted in your region. One space per person: your memory is never pooled with anyone else's, never shared, and never used to train any model. We run the servers so you have nothing to install or maintain; what's inside stays yours. The fine print is on the privacy page.

Yes, and that's the point: Klyr keeps a searchable copy of your working sessions with your clone in its long-term memory. That's how it recalls the call from three weeks ago instead of asking you to repeat it. Secrets like passwords, keys and tokens are redacted before anything is stored, and the copy lives wherever your memory lives: on your machine if you self-host, in your private hosted space if we host you.

Don't want it? One setting turns conversation storage off entirely, whether you self-host or we host you. Off means off.

You leave with it. Your identity files are plain text you can open, edit and copy; nothing proprietary. Self-hosting, one command exports your memory to a plain, open file you keep. Hosted, you export it yourself, anytime while your subscription runs: ask your clone. When your subscription ends (the end of your paid billing period, not the moment you cancel), a 30-day grace window opens and we email you the date it closes; during it, you get your full export on request, by replying to that email. When it closes, your data is permanently deleted, automatically. Deletion on request works too. Day to day you can already wipe any single memory yourself, anytime. Your clone is yours, not a hostage.

Requirements today: Klyr runs as a plugin inside Claude Code, on Mac, Windows, and Linux. On Windows, plain Windows is enough, no WSL needed. (That covers hosted memory, which is the usual choice. Self-hosting your memory needs Docker on any platform; on Windows that means Docker Desktop, and Klyr itself still runs natively.)

No. Klyr lives mainly on your machine, but your clone's memory is hosted, so you can reach it from elsewhere too. Today that means the Claude apps: add Klyr as a custom connector in claude.ai and the same memory is there from your browser, your phone, or Claude Desktop, even where Klyr can't see a single file on your machine. You ask, it recalls. What stays on your machine is the always-on part: context injected on every message, conversation capture, and the /klyr commands. Setup is on the connector page.

Pick monthly (500€ HT / excl. VAT) or annual (5,000€ HT / excl. VAT) in the offer and check out on Stripe. Your welcome email follows at the address you paid with. Setup takes minutes: follow the get-started page.