A writing app without AI, by construction

Quorly is a static page: plain HTML, CSS and JavaScript with no framework and no build step. When you write, the draft is stored in this browser — localStorage for the open document, IndexedDB for the library and its images. Nothing in that path is a network request.

The product's only server API lives under /api/, and it exists to answer two questions: what plan is this account on, and which features are switched on. It stores subscription state and feature flags. It has no document endpoint and no text field. You can read the shape of it in the privacy page.

That is what makes the claim structural rather than a promise. Adding an assistant would not be a setting; it would mean building a service that receives drafts, and that is a change large enough to show up in the network tab the first time you used it. The full data flow is written out on how Quorly works.

Scroll the table sideways to read every column →

An app that passes the first question can still fail the second, and an app that passes both can still change its mind. The third question is the honest one: it asks what the architecture allows. Quorly's allows very little.

• Focus mode. Press Esc and the interface clears down to the page and the sentence. Press it again to bring everything back.
• Hemingway mode. Write forward without letting yourself rewrite the last paragraph for the fifth time. Part of Quorly Pro.
• Real formatting. Headings, bold and italic, lists, quotes, links, code blocks, tables, images and aligned text — without Markdown syntax in the way.
• Exports that don't need an account. Markdown, PDF with selectable text, plain text and a .quorly package that keeps the images. EPUB for Kindle is part of Quorly Pro.
• Word, Markdown and plain-text import. Open an existing .docx, .md or .txt in the browser and keep working. EPUB import is part of Pro.
• Offline by default. Install it as a web app and it keeps working without a connection, then install the same editor on Windows, macOS or Linux from the download page.

“No AI” would be easy to say and hard to believe if the rest of the page were vague. So, precisely:

• Traffic analytics. The site counts visits with Cloudflare Web Analytics and Google Analytics. They see pages, referrers and browsers; they never see a draft. Google Analytics may set cookies — the privacy page says so in full.
• One event counter. /e receives an allowlisted event name such as first_keystroke, plus at most one short label like the export format. Never document text.
• Pro billing. Subscribing needs a Google account and goes through Dodo, because a subscription has to be tied to something you can cancel. Billing is not writing.
• Sync, if you ask for it. Pro Cloud Sync writes documents to your own Google Drive through a short-lived token minted by /api/sync/token; Quorly brokers the credential and never receives the file. Local Sync writes .quorly files to a folder you pick.
• Agent tools, if you bring an agent. In browsers that support WebMCP, the editor registers tools that a local agent in your session can call. Quorly ships no agent and no model — it only lets one you are already running work against the page, the same way it would against any other tab.

Plenty of writers use a model for research, an outline, or a second opinion on a paragraph. Nothing here argues against that; it argues against the drafting surface being wired to a service by default. Write in Quorly, then take the draft where you want it: Copy to clipboard for a formatted paste into the tool of your choice, Markdown for anything that reads plain text, or PDF for something that has to look finished.

The draft leaves when you take it out. That is the whole difference between a tool that has no AI and a tool that has one turned off.