.markwell
03 · Conversation Infrastructure ↗

One core · three shells

Markdown that renders identically — browser, embed, and native Mac.

One pure rendering core; everything else is a thin shell around it. Write once, and it looks the same everywhere. No account, no cloud, no lock-in — your files stay on your machine.

Open the web app → in your browser · one file · no install
Download for Mac — coming soon your whole project · real files · offline

Free · local-first · no sign-up

Markwell for Mac showing a project of 19 linked Markdown files as a graph, with an architecture overview document open in the reading pane.
The Mac appYour whole project as a graph — every .md and the links between them. The web editor is the quickest way in; this is where it leads.

The idea

One pure Markdown core. Everything else is a thin shell.

The same rendering engine runs three ways. They differ only in reach — from a single file in your browser to your whole project on your Mac.

Web app

Open or drop in a .md file, read it cleanly, edit in split-view — all in your browser, nothing to install. Your work stays there between visits.

Native Mac app

Opens your whole project — every .md file and the links between them, as a tree, list, or graph. Real files on disk, offline, and tiny.

Embeddable widget

Drop the exact same renderer into any React app, so authored content looks identical in the editor and on the page.

Write once. Render identically anywhere.

Local-first · by construction

Your files. Your machine. Nothing phones home.

No account. No sync server. No telemetry. Open a file, edit it, save it — done. Plain text in, plain text out; nothing proprietary to trap your work.

  • No sign-in, ever
  • No cloud, no accounts
  • No tracking, no telemetry
  • No lock-in — it's just Markdown
  • TinyBuilt on Tauri — a native shell measured in megabytes, not hundreds.
  • YoursFiles never leave your machine. Sync them with anything, or nothing.

These aren't features we added. They're constraints we kept.

Not just a textarea

Smart where it counts.

Most simple editors give you a box. Markwell adds the few things that actually save time.

Contextual tables

Click into a table for controls to add or remove rows and columns and cycle alignment; columns tidy to even widths as you go.

Undo that survives

Real history with ⌘Z / ⌘⇧Z that restores your cursor, not just the text — and survives the toolbar actions that usually break native undo.

Paragraph reflow

One click unwraps old hard-wrapped Markdown into clean, edit-friendly source, without changing how it renders.

And, quietly

More and more of what we write now is the text around AI work — prompts, context, notes, specs. All of it is Markdown. A calm, portable, honest Markdown tool is a good place for that to live. Deeper AI-workflow support is on the roadmap.

On the roadmap

Starts small and sharp. From here:

  • A richer editorSyntax-highlighted Markdown source (CodeMirror), synced scrolling between panes, and a command palette.
  • More Markdown powerHighlighted code blocks, Mermaid diagrams, KaTeX math, and front-matter awareness.
  • EverywhereWindows and Linux builds, and the embeddable renderer published as a drop-in package for any React project.
  • Content, not just filesLeaning into "author once, render anywhere" — a lightweight, Markdown-native way to drive live, editable content in real products.