versorium Download ES · Leer esta página en español

Limits and details

Everything the home page sums up, limits included. Full technical details are in llms.txt.

What it doesn’t do yet

  • Release 0.1.2 has installers for macOS, Windows and Linux. The app has been tried on an Apple silicon Mac, on Windows 11 and, with 0.1.0’s .deb, on Ubuntu 22.04. The Intel .dmg, the .rpm and the AppImage have never been run.
  • Not signed by Apple or Microsoft: macOS says it’s damaged and Windows shows SmartScreen (see “The first time you open it”).
  • Updating from inside the app, from 0.1.0 to 0.1.1, has been tried end to end on the Mac and on Windows 11; on Linux, not yet.
  • The AI does two things: rewriting, and checking continuity, which reasons over chapter titles and the codex, not the prose. There is no chat, search by meaning, dictation or “Continue chapter” (the button is there, but disabled).
  • The built-in AI runs inside the app: if its engine fails, Versorium closes with it; autosave and snapshots limit what you can lose.
  • GPU: Metal tried on Apple silicon (M4 Max), with about 15 s of compiling the first time; Vulkan, for Windows and Linux, builds, but the built-in AI has not yet been tried on a GPU; there is no CUDA.
  • Going back to an old snapshot or recovering a deleted chapter is done with git, outside the app; the change log can’t be browsed from it.
  • ↩ Restore reaches back to the start of the current session, up to 1000 edits.
  • Opening Settings rebuilds the editor, which loses its undo history.
  • Backups are made by hand; nothing is scheduled.
  • The GitHub repository and remote are set up outside the app, and pulling doesn’t merge diverged histories.
  • DOCX and Scrivener drop scene titles, with a warning; the PDF prints them, except the first scene’s in each chapter, which it drops without one. The PDF is US Letter in Times-Roman and replaces emoji and non-Latin scripts, with a warning. The cover is a typographic title page, not an image.
  • Importing DOCX, EPUB or Scrivener loses bold, italics and scenes; images, DOCX footnotes and comments are not imported. Imported novels are created as English, and a novel’s language can’t be changed.
  • Spell checking uses the system’s checker: it works on macOS and on Windows 11; on Linux it underlines nothing yet.
  • No built-in editors for the codex, plot or research; chapters are reordered with Move earlier / Move later, not by dragging; no downloadable fonts.

Privacy

Your novel stays on your computer unless you ask otherwise. It’s a folder on your disk, and Versorium has no analytics or telemetry.

On its own, the app does one thing over the network: it checks GitHub for updates at launch, with nothing from your novel, and you can turn that off in Settings → Application. Everything else happens when you ask for it: downloading a model from Hugging Face, sending the novel to GitHub or bringing it back, or rewriting with Claude Code, Codex or OpenCode, which send the passage to their own service; that is why the Rewrite dialog labels every provider Local or CLI. If you choose a synced folder such as iCloud Drive or Dropbox as a backup destination, the app tells you that copy leaves the machine. Crash reports are kept on your machine, without prose, and leave only if you press Report.

Crash reports without prose
Kept on your machine with no paths, email addresses or tokens, and no prose: any run of six or more words is removed. They leave only if you press Report, which opens a GitHub issue in your browser.
Credentials in the keychain
Tokens go to your system's credential store (Keychain, Credential Manager or Secret Service), never to a settings file.

This page keeps the theme you pick in this browser (localStorage) and nowhere else. It uses no cookies.

History and snapshots

Every change in the editor is written down as an operation (what was typed or deleted, where, and by whom: you or an AI) in an append-only log kept inside the novel. Every 200 operations the whole chapter is saved as well. Assistants connected through MCP can read the log.

On top of that, every novel is a git repository. Versorium takes a snapshot every minute when something changed, before an AI writes and before a chapter is deleted, and you can save your own with a description.

↩ Restore, in the status bar, puts back the previous text of the selection, or of the word under the cursor.

Quitting with Cmd+Q, the app menu or the Dock waits for the last save; if the save fails, the app stays open and says why.

Today Going back to a snapshot needs git. The other limits are under “What it doesn’t do yet”.

Your folder records who wrote each change: you or the AI.

.versorium/ops/ch-02/2026-10-03.jsonl{"seq":1841,"ts":1791046265874,"author":"human","kind":"delete","from":675,"to":681,"text":"minded"}{"seq":1842,"ts":1791046266503,"author":"human","kind":"insert","from":675,"to":676,"text":"l"}{"seq":1843,"ts":1791046266661,"author":"human","kind":"insert","from":676,"to":677,"text":"o"}{"seq":1844,"ts":1791046266790,"author":"human","kind":"insert","from":677,"to":678,"text":"o"}
Four lines of the log: a word deleted, and the first three letters of the one that replaces it.

AI

Versorium ships with no AI switched on. If you want one, you choose where it comes from: a model that runs inside the app with llama.cpp, Ollama if you already use it, a local OpenAI-compatible server (LM Studio, llama-server), or the tools already in your terminal: Claude Code, Codex or OpenCode.

For the built-in AI there is a catalogue of 11 writing models in four sizes, from 0.58 to 17.4 GB. The app recommends the largest size that fits your machine with room to spare, downloads only when you press Download, resumes what was cut off and checks every file against SHA-256.

To rewrite, you select a passage and see the difference before applying it; Versorium takes a snapshot first and records the change under the AI's name. Each provider is labelled Local or CLI, because a CLI tool sends the passage to its own service.

Assistants connected through MCP (Claude Code, Claude Desktop, Codex and OpenCode set up in one click; Cursor and VS Code by hand) can only read, unless you grant write access to one in particular. Even then, every write first returns the diff and is applied only by a second call that confirms it, after a snapshot.

Today The AI only rewrites and checks continuity. The other limits are under “What it doesn’t do yet”.

Files, export and import

Every chapter is a .md file with a YAML header. The header belongs to the app (title, status, word count) and the rest is your text, in no proprietary format. Renaming a chapter changes its title, not its file; the order lives in versorium.json.

You do not need to install git: it is built into the app. If you already use it, the folder is an ordinary repository.

It exports Markdown, DOCX in standard manuscript format, EPUB 3 (it passes epubcheck 5.2.1 with no errors or warnings), PDF and a Scrivener 3 project. DOCX, EPUB and PDF get a typographic title page and a colophon, and you can turn off either one per project. It imports Markdown, DOCX, EPUB and Scrivener projects, and shows you a preview, with its warnings, before creating the project.

You can send the novel to a GitHub repository and bring it back. The token lives in your system's credential store and only ever travels to github.com.

Today Importing from Word, EPUB or Scrivener loses bold, italics and scenes. The other limits are under “What it doesn’t do yet”.

not-on-the-list/
├── versorium.json
├── manuscript/
│   ├── ch-01-not-on-the-list.md
│   ├── ch-02-the-needle.md
│   ├── …
│   └── ch-08-low-tide.md
├── codex/  plot/  research/
├── style/  prompts/  snapshots/
├── .versorium/ops/
└── .git/
A novel on disk, exactly as Versorium creates it: versorium.json holds the title, the language and the order; .versorium/ops/, every change; .git/, the snapshots. Any text editor opens all of it.
manuscript/ch-02-the-needle.md---
id: ch-02
title: "The Needle"
pov: null
status: "revised"
words: 282
---
She counted the steps on the way up and again on the way down, because the first count came to forty-three and she did not trust herself after the boat. There were forty-two. The extra one was the threshold of the lamp room, higher than the rest, worn in the middle by a hundred years of boots.

Up there, the lens took up all the air. …
The chapter from the capture, as it sits on disk.

The first time you open it

macOS

macOS says the app is damaged. It is not.

The bundle carries no Developer ID signature, so macOS quarantines it and Gatekeeper reports the most misleading message it has. Clear the quarantine flag once, in Terminal:

xattr -rd com.apple.quarantine /Applications/Versorium.app

Only do this with a copy downloaded from the releases page: that flag is the check that protects you from a tampered download.

Windows

SmartScreen interrupts the installer.

The installer is unsigned, for the same reason as the macOS bundle, so Windows shows the blue “Windows protected your PC” screen. Choose More info, then Run anyway. Signed builds need Apple and Microsoft certificates, which do not exist yet, plus changes to the release workflow.

Updates are signed with minisign: the app installs one only if its signature matches the public key built into it and its SHA-256 matches the release's SHA256SUMS. It checks for them once at launch, with no account and no token; you can turn that off in Settings → Application. A GitHub token is optional: it is only needed to read a private repository, or to get past GitHub's limit of 60 requests an hour without one. The update from 0.1.0 to 0.1.1 has been installed from inside the app, end to end, on an Apple silicon Mac and on Windows 11; on Linux it has not been tried yet.

Platforms

macOS

Release 0.1.2 has two .dmg downloads, for macOS 10.15 or later: Apple silicon (11.7 MB) and Intel (11.8 MB).

The app has run on an Apple silicon Mac (an M4 Max), where the built-in AI uses Metal: the first run takes about 15 s to compile, and the app does that ahead of time at launch. 0.1.0’s released Apple silicon .dmg was opened on an Apple silicon Mac on 4 October 2026, and its window checked; with that 0.1.0 installed, the app offered 0.1.1, downloaded it, installed it and restarted into it. The Intel one has never been run.

Windows

Release 0.1.2 has an x64 installer in two formats: NSIS, .exe (11.7 MB) and MSI (23.3 MB).

It has been tried on Windows 11. There, 0.1.0’s .exe and .msi installed; with the Visual C++ runtime, which 0.1.0 needed and 0.1.1 no longer does, a novel was created, typing saved the chapter and the change log, spell checking underlined and the update check answered; then the app updated itself to 0.1.1. It needs vulkan-1.dll, which graphics drivers usually install; a PC without Vulkan drivers has not been tried. The built-in AI uses Vulkan (NVIDIA, AMD, Intel); there is no CUDA, on purpose. It needs an x86-64-v2 processor (SSE4.2).

Linux

Release 0.1.2 has x64 .deb (22.4 MB), .rpm (22.4 MB) and AppImage (99.0 MB) packages, built on Ubuntu 22.04 (webkit2gtk-4.1).

0.1.0’s .deb was tried on Ubuntu 22.04 (amd64): it installed, opened, created a novel without needing git, and typing saved the chapter. That test found that, without the standard XDG folders, the app could not find its projects folder; 0.1.1 fixes it, but no release after 0.1.0 has been run on Linux yet, and neither have the .rpm and the AppImage. The built-in AI is compiled with Vulkan, but it has not yet been tried on a GPU. The .deb declares libvulkan1 and libssl3. It needs an x86-64-v2 processor (SSE4.2). Saving a token needs Secret Service; without it, the app should say so, though that has not been tried either.

Every file has its checksum in SHA256SUMS. The release notes are on the 0.1.2 release page; to hear about the next ones, on GitHub: Watch → Custom → Releases.

Why it exists

Miguel Esparza started it for himself: he wanted to write calmly, with AI on his own terms, from none at all to the tools he already paid for, and above all never to lose a draft, because when you write a novel the backup of the manuscript matters more than anything.

The apps he tried either lacked what a novel needs or charged too much for it. That is why Versorium is free and open source. And he keeps improving it.

In September 2026 he looked for an app like this and found none that brought together the AIs you already have, local models, its own MCP and the history of every change, on a quiet desk. He started it on 14 September; the first release came out on 4 October.

The comparison, with its sources

Credits

Headings use Aguja Display, a modified version of Adobe’s Source Serif 4, under the SIL Open Font License 1.1 (assets/fonts/OFL.txt). The page loads nothing from other servers and uses no third-party libraries. Other names on this site belong to their owners and only describe compatibility or serve to compare.