mdai isn't open source. Here's everything instead.

Last updated: November 14, 2026

It's a fair question, and it deserves a straight answer rather than a page of adjectives. So: mdai is closed source, it is going to stay that way, and this page says why — and then does the thing you probably wanted open source for in the first place.

Why it's closed

On mdai.me, mdai costs €14.99 once. There is no subscription, no server you rent from us, no cloud tier, no upsell inside the app. That is the whole business — one payment, and then the app keeps working forever, offline, on your own machine.

A licence check is a small piece of code. Published, it is an afternoon's work to remove, and nothing else is holding the lights on. For a program with a server behind it, open source is survivable, because the paid thing isn't the code. For this one, the code is the paid thing. Opening it wouldn't make mdai more trustworthy — it would make the next version not exist.

This is not an unusual position. Every Markdown editor that writers actually pay for is closed source. The open-source alternatives are free forever, which is exactly why there is nobody whose job it is to keep them going.

What you wanted from open source, you get anyway

When people ask for open source, they usually mean two specific worries. Both of them have an answer here that doesn't depend on reading the source.

“Will I lose my writing if this app dies?”

No, because mdai never holds it. Your vault is an ordinary folder on your own disk and your notes are ordinary .md files — the same files any other editor, any other operating system, and any plain text window can open, today and in twenty years. There is no database, no proprietary container, and no export step. The format is open even though the app isn't, and the format is the part you can't afford to lose.

If the trial ends and you don't buy, mdai locks editing and nothing else: reading, copying, exporting and opening your folders keep working. Your files are never held hostage.

“How do I know it isn’t watching me?”

Because you can watch it back. You don't need the source code for this — you need the list below, and a way to check it, and both are here.

Every network request mdai makes

This is the complete list. It was read out of the code of mdai 1.2.7 on October 10, 2026, request by request, and there is nothing else in it. The publishing section below, added in 1.3.6, lists requests mdai makes to a server you run; those are not requests to us, and the count of five above is unchanged.

To us — five requests, and that's all of them

Two addresses belong to us: license.mdai.me, a small Cloudflare Worker, and dl.mdai.me, the bucket the downloads sit in.

None of the five is periodic, scheduled, or made in the background beyond the two throttled checks described above. There is no mdai account to make them about. Publishing, described further down, is not one of them: it goes to a server you run, not to us.

The five requests carry the four things described in the privacy policy: activating and deactivating a device are two requests for one of them, the device registration.

Mac App Store build only — one request, only when you press it

The copy from the Mac App Store makes none of the five requests above; the App Store handles its trial, purchase and updates. It makes one request of its own, POST license.mdai.me/apple/claim, and only when you press the button for using mdai on Windows or Linux in Settings → License: it sends the email address you type in and the record of your App Store purchase that Apple signs, and gets back a licence key for that address.

To an AI provider — only the one you chose, only with your key

The assistant is off until you paste in an API key of your own. When you then run an AI action, your instruction and the whole document — or only the section you selected — go straight from your machine to that provider, under your account, and never through us. When you use Ask vault with a cloud provider, the passages it found in your notes, with their file names, are sent to that provider the same way. We have no proxy to log it with and no key of yours to read it with.

The first time you use AI with a given provider, mdai asks for your permission and names the provider and what will be sent. The answer is recorded on your computer, in mdai's own settings file, and is never sent to us or to the provider. You can withdraw it in Settings → AI; the next AI request asks again. Ollama runs on your computer, so it is never asked.

Two of them are also asked to count tokens before you spend any, at /v1/messages/count_tokens and :countTokens — but only when you press Count exactly, never while you type.

To your own site — your document goes out only when you press Publish

mdai 1.3.6 adds publishing: it can send a finished document to a site you run — WordPress or Ghost. When you open the publish dialog, mdai asks your site which categories and tags exist and what your account may do. Your document and images are sent only when you press the publish button. Nothing is published in the background, on a schedule, or as a retry you did not ask for.

Your content and images go directly from your computer to the server you entered — never through mdai.me. The post is built on your machine and sent straight there. We run no proxy for it, we log none of it, and we have no way of seeing the address, the credentials or the post. The address lives in mdai's local settings file; the password or application token lives in your operating system's system keychain.

Images stored as files in your vault are uploaded to that same server at the moment you publish, and to nobody else — this applies to WordPress and Ghost. Images embedded directly in the document (data: images) are not uploaded separately; they go out inside the post's HTML. Images that are already web links (https://) stay links to wherever they are hosted; mdai does not download or re-upload them.

Links that point to files on your computer keep their text, but the link itself is removed before the post is sent.

mdai remembers which images it has already sent to each of your sites, so updating a post does not send them again. That list stays on your computer and holds a fingerprint of each image, its address on your site and which of your accounts it belongs to, never the image itself, your password or the text of your document.

If an upload fails, you are asked before the post is sent — skip that image and continue, or cancel the publish. When you cancel, no post is sent — but images that were already uploaded before you cancelled stay on your server.

mdai also keeps a small publishing log on your own disk — the time, the account id, the platform, the action, the outcome, and the post id when the server returns one. It holds no document content, no path, no password and no token. The post id and the address of the site you published to are also written into the document's own front matter, so that publishing the same document again updates that post instead of creating a second one.

On your own computer — Ollama and connected tools

Local AI (Ollama). If you choose Ollama as your provider, mdai talks only to Ollama running on your own computer, at 127.0.0.1:11434 — /api/chat, and /api/tags to pick the installed model — and no key is needed. Ask vault also uses that local Ollama, at /api/tags and /api/embed, to find the passages that match your question. These requests never leave your computer.

Connecting other AI tools (MCP). Off by default. When you turn it on in Settings, mdai opens a connection point on your own computer only (127.0.0.1), for tools you connect with your access token. It cannot be reached from the network, and mdai sends nothing out through it.

Google Drive and OneDrive

If you go looking through the app you will find Google and Microsoft sign-in addresses in it. They belong to a cloud-vault feature that is declared but not finished: no application id is configured for either provider, so the code fails before it can open anything, and the app shows both options as coming soon. Nothing is sent to either of them today.

What isn't on the list, because it doesn't exist

No analytics. No usage tracking. No crash reporting. No telemetry of any kind. Which files you open, what you write, how long you work and whether you use the app at all are never transmitted anywhere. The editor window itself is locked down by a content-security policy that permits no remote connections and no remote images — it can talk to the program it lives in, and nowhere else.

This describes the application; the website's own visit counting is explained in the privacy policy.

Don't take our word for it

This list is checkable without us, and checking it is the point. Put mdai behind any network monitor — Little Snitch, a proxy, your router's log — and compare what you see against the five requests to us above, plus the publishing traffic to a site you run. It should match exactly. If it doesn't, that is a bug and we want to hear about it.

Every release is published with its SHA-256 so you can confirm the file you downloaded is the file we built, before you ever run it.

The legal version of all this, including what our licensing service stores and for how long, is on the privacy page.