A writing studio for macOS · Windows · Linux

Every wordstillyours.

Perkins is a desktop studio for novelists, essayists, and screenwriters, with an AI editorial team that coaches like a great editor: principles, master examples, hard questions. It never writes your prose. That isn't a setting. It's the product.

Free 14-day trial · $89 once, yours forever · No subscriptions

The editors read. You write. The prose pane is yours alone.
the whole point
The stance

Named for Maxwell Perkins, the editor who made Hemingway better without writing a line of him.

Coaches, never ghostwrites

No “apply rewrite.” Anywhere.

Editorial feedback arrives as a principle, a goal, and a master-author example. Never replacement sentences. There is no mechanism in Perkins that can move AI text into your manuscript. Not a toggle. Not a tier. Structural.

Proposes, never presumes

Your metadata, your yes.

The assistant can draft synopses, link your world bible, infer story dates, and map plot threads, as proposals you accept field by field. Cancel, and not one byte was written. And every project runs at the AI level you choose, with an exportable record of what happened.

Plain files, no lock-in

A folder of Markdown you own.

Every scene, note, and codex entry is a plain text file on your machine. Open the folder in any editor, forever. Perkins organizes it; it never captures it.

Perkins keeps your prose 100% human-authored, so your copyright stays intact.

Copyright protects human authorship. Because the AI in Perkins never writes your expression, your words remain yours in the fullest sense.

Every form of the written word

One studio. Every shape a book takes.

Novels Novellas Short stories Essays Screenplays Your own template

Each format brings its own structure: a novel's chapters and scenes, an essay's sections, a screenplay's acts, with matching metadata, statuses, and compile rules. And if your form doesn't exist yet, define it. Upload a template and Perkins builds the studio around it.

Screenwriters get Fountain, the industry's plain-text screenplay standard: type INT. KITCHEN - NIGHT and Perkins knows it's a scene heading; character cues, dialogue, parentheticals, and transitions format themselves as you write, and compile to a properly measured Courier page. Your script stays a plain text file that any screenwriting tool can read. No lock-in, even here.

The editorial team

Five editors read your scene. None of them touch it.

The Reader

Reads cold, once, forward

Experiences your scene as a first-time reader: what they know, suspect, feel, and carry forward. Deliberately isolated from your voice notes so the cold read stays honest.

The Structure Editor

Counts what critics feel

Exact sentence rhythms, dialogue mechanics, period accuracy, continuity. Quantified diagnostics computed from your actual prose, not vibes.

The Voice Editor

Guards what makes you, you

Protects your voice profile and influence blend, watches prose musicality against your own rhythm system, and flags anything drifting toward the generic.

The Connections Editor

Sees the threads

Finds the linkages you might miss: mirrored scenes, unpaid setups, orphaned payoffs, plot threads drifting apart. It suggests them in the relationship graph for your one-click confirm or dismiss.

The Senior Editor

Synthesizes and prioritizes

Forms an independent view, then weighs every junior's findings into one prioritized editorial letter with a readiness score. The desk where it all comes together.

Every persona is editable. Add editors, remove them, route each to a different AI model: a frugal reader, a premium synthesizer. Your masthead, your rules.

All of them answer to one editorial constitution you can read and rewrite: don't embellish, be factual, be concise, never supply replacement prose. It sits above every editor, so no persona can talk its way out of it. Not even one you invent.

The last pass

And then, the Fair Copy.

Writers have always finished this way. Austen, Dickens, every working novelist once wrote out a fair copy: the final version, fresh, in their own hand. Perkins brings the ritual back. When the editorial letters are read and the notes are addressed, study the scene, then rewrite it from memory beside a brief built from your own notes, with the editors' ideas distilled to bare principles and their words nowhere in the room. A verify stage measures the new draft beside the old, plainly, never as a grade. Then you choose. The coaching survives as craft. The last hand on the page is yours.

The oldest draft

Write it by hand. Perkins will read it back to you.

Some writers draft on paper. Photograph the pages, bring the images to your desk, and Perkins transcribes them into the Desk Drawer, where arrivals wait until you decide where they belong. The photograph stays beside the text so you can check every word against your own handwriting. Words the machine could not read clearly are marked, not guessed.

Nothing reaches your manuscript until you have looked at the page and said yes, and when it does, the words are byte for byte the ones you approved.

The Desk Drawer takes typed notes too, with no machine involved at all: drop a text file in, or let one sync into the folder, and it is waiting when you sit down. Drop a bare text file anywhere in the project folder and Perkins will notice it and offer it to the Drawer; nothing is moved until you say so.

The machine reads. It never writes.

A photographed page of handwriting on the left, its transcript on the right, with an uncertain word marked for review.
The page you wrote, beside the reading of it. Uncertain words are marked for you to settle.
Why Perkins exists

Art is human.

Perkins believes art is created by humans. We believe AI is a tool, and should always be human-first by design. We believe AI should never usurp the creative process or produce creative content.

Perkins does not strive to replace the editorial process. It exists to help a writer bring the strongest version of their art to the table, before a human editor ever enters the process.

Created by writers, for writers.

& it's fast
The studio

Draft, plan, and revise a whole book in one calm place.

Write

  • A serif-first Markdown editor focus mode, typewriter scroll
  • Flow view a chapter as one continuous page
  • Snapshots & version history diff and revert any scene
  • Split pane notes, codex, or an editor's letter beside your draft
  • Read-aloud test the rhythm by ear
  • Images & media on any page
  • Desk Drawer half-formed things wait here until you decide where they belong
  • Your style guide hand the desk a manual you own; editors cite it by rule

Plan

  • Start from an outline import an OPML plan; every heading becomes a scene, ready to write
  • Corkboard & Kanban cards by status, act, or POV
  • Outliner every scene, every field, one grid
  • Timeline reading order and story-world chronology
  • Plotlines & plot grid threads as a subway map
  • Codex & relationship graph your world, cross-referenced
  • Setup/payoff tracker Chekhov's ledger, kept
  • Historical record date a scene and see what your sources say about that day
  • Pacing map the measurable shape of the whole book
  • Submissions tracker where it went, what came back

Coach

  • Full editorial reviews five perspectives, one letter
  • Editorial inbox every note tracked to your line
  • Editorial memory decline a note once; they don't raise it twice
  • Voice Health rhythm, vocabulary, AI-tell checks, offline & free
  • Dialogue analysis does she sound like him? statistically, no
  • Ask about your book “how often do Eve and Remy meet?”
  • Assisted actions codex, dates, synopses, proposed for your yes
  • Readiness scores watch a scene earn its “done”
  • The Fair Copy pass rewrite from memory; end in your own hand
your masthead
Make it yours

Nothing about your studio is fixed. Nothing about anyone else's is yours.

Your editors

Rewrite any editor's persona, clone one, add your own, or retire the whole desk. Route each editor to a different AI model: a frugal reader, a premium synthesizer.

Your voice

A voice profile built from passages of your own writing, with an influence blend you weight yourself. The editors protect it; they never average it away.

Your masters

The reference library maps craft problems to the authors you'd study for them. Curate it. Add the writers who taught you, remove the ones who didn't.

Your rhythm system

Name your prose registers and their rules, or turn the whole system off. The rhythm visualizer colors your sentences by your definitions, not ours.

Your workflow

Statuses, colors, tags, codex categories, review thresholds, banned vocabulary. Every vocabulary in the studio is editable, per writer and per project.

Your studios, plural

A spare thriller and a lyrical memoir shouldn't share an editor. Any project can override your voice, rhythm, and team, without touching your defaults.

Out into the world

Yours to keep. Easy to share.

Sharing sends a copy out; the master stays a plain-text folder on your machine. Perkins never becomes the place your book lives. It's the desk your book is written at.

Local-first · Private by default

Your manuscript never has an account.

Perkins runs on your machine and stores everything in a folder you choose. Version it with your own GitHub repository. Sync it through your own cloud folder. Or keep it on one laptop, off the grid entirely.

Your words leave your computer in exactly two cases, both yours to configure: to the AI provider you choose (bring your own key, or run a local model and send nothing anywhere), and to your own git remote if you connect one. Or set a project to No AI and nothing reaches a model at all. API keys live in your operating system's keychain, never in files. There is no Perkins server, no telemetry on your prose, nothing to breach.
Your call, on the record

Choose how much AI. Then prove it.

Agents, publishers, and contests increasingly ask what part a machine played in your book. Perkins answers with a setting and a record, not a promise. Each project runs at the level you choose, and the level is enforced in the core of the app, not in a menu.

Level one

No AI

Zero model calls. Not a preference, a wall: the code that reaches a provider cannot even be called at this level. You still get the whole studio, because most of it was never AI. The organizer, the codex, the timelines, the pacing map, voice and dialogue statistics, deterministic connection reports, search across everything.

Level two

Organizational

The machine helps with the apparatus and nothing else: scene metadata, codex entries, story dates, chapter boundaries on an import. No editorial reading of your prose, no reviews, no coaching. For the many contracts that ask only about generated text, this is a clean answer.

Level three

Full studio

The editorial team reads and coaches. Everything on this page. And still, at this level as at every other, no AI text can enter your manuscript. That part is not a level. It is the architecture, and it does not have an off switch.

And beneath the levels, a second control: where your words may be sent at all. Set a project to local models only and nothing leaves your machine, a claim Perkins verifies against a live network monitor. Or restrict it to providers whose published terms exclude training on submitted content. The setting is enforced in the same gate as the levels, and the record carries it.

The attestation

A record of how the book was built.

Perkins keeps a tamper-evident log of the things a publisher might reasonably ask about: every file you imported, every large paste that arrived from somewhere else, every metadata proposal you accepted, every editorial review you ran, and the writing sessions themselves, counted by where the words came from. Export it as a document: which level, since when, how many model calls, what came in from outside, how the manuscript accumulated over months of sessions.

The log holds no prose, only counts and fingerprints, so you can show the record without showing the book. And it states its own limits in plain language: it can tell you what happened inside Perkins, it cannot tell you who was at the keyboard. It is the difference between saying no AI wrote this and being able to show it.

You can read the whole record inside Perkins, in plain sentences rather than raw data: every import, every accepted proposal, every writing session, each saying what happened and whether a model was involved. Prefer a spreadsheet? Export the history as CSV, clearly marked as a copy, with the record of authority staying in your project. And the report names the reference material your desk could draw on, style guides and historical records alike, with when it was attached and what you approved.

A project that began as an import says so, in the record and the report: how many words arrived, from which file, on what date, with what came before honestly marked as beyond the record's sight. And wherever words arrived from outside, a paste, a file Perkins found in your folder, even a scene you edited in another app, you can say more. Pasted a paragraph back from a grammar checker? Add a note naming the source and the reason, on the spot or months later. Your note travels with the record, plainly marked as yours, and the report includes it only after you certify it is true. Perkins states what it saw; you state what you know; the reader can always tell which is which.

The studio, as it ships

Five windows into the desk.

Real captures of the shipping app. Nothing mocked, nothing staged, nothing retouched.

The pacing map view: a bar chart of scene pace across five chapters, with per-scene pace scores and word counts listed by chapter
The pacing map. How fast each scene reads and how its shape compares to its neighbors. Two offline signals, computed on your machine. No AI, and nothing about your story is judged.
The relationship graph: characters, places, and items from a novel drawn as a network with reference and cause-effect edges
The relationship graph. People, places, and things from your codex, cross-referenced, with every connection drawn and filterable by kind.
The writing stats view: deadline pacing with words per day required, a sprint timer, a daily writing chart, an activity grid, and a by-chapter table
Deadline pacing. Words per day against the calendar, sprints when you want them, and a by-chapter ledger of where the book stands. On track or not, it tells you straight.
The Editorial Inbox: findings from the editors, each quoting a line from the manuscript, stating a craft principle, citing a master, and offering Addressed, Defer, and Dismiss buttons
The Editorial Inbox. Each finding quotes your line, names the principle, and shows how a master handled it. The buttons say Addressed, Defer, Dismiss. None of them says Apply.
The Record view titled How this manuscript was made: an intact history with counts of sessions, arrivals, and model calls, and dated plain-language entries
The Record. Every session, every arrival, every model call, in dated plain sentences. The history of the book, kept where you can read it and export it.
Pricing

Try it free. Then own it.

Free trial
14 days of actual use

The complete studio, including the full editorial team. We count days you write, not days that pass, so write on weekends and the trial stretches for weeks.

  • Every feature unlocked
  • No credit card, no account
  • Your files are yours from minute one
Start the trial

No subscriptions. One-time purchase. Yours forever.

A one-time cohort

Founding Writers

We are giving free lifetime licenses to a small cohort of working writers. No obligations, no strings. Use Perkins on your real project and tell us where it fails you.

Apply to be a Founding Writer
Questions writers ask

Fair questions.

Will this make my book read like AI wrote it?
The opposite is the design goal. Because Perkins never inserts AI text, your prose stays statistically and stylistically yours, and the Voice Health panel actively screens for AI tells, banned vocabulary, and rhythm flattening. For the writers who want to go further, the Fair Copy pass ends every scene the old way: studied, then rewritten from memory, so the final page carries no hand but yours. The editors make you better; they don't make the page theirs.
What about AI slop?
Slop cannot reach your manuscript from here: Perkins has no mechanism to insert AI text, so the machine's mediocrity is never your book's problem. The editors are held to standards against slop in their own feedback too. Every finding must anchor to a real line of your prose, an author-editable constitution forbids embellishment and empty praise, and responses containing rewritten prose are rejected whole by validators. Much of what Perkins tells you is not generated at all but measured: word counts, rhythm statistics, pacing, whether anything actually changed in a scene. And Perkins can help you spot slop patterns in any draft, whatever its origin, because hollow scenes measure the same whether a machine wrote them or a tired writer did.
Can I make it follow my style guide?
Yes. Add a reference you own (a style manual, a house guide; text, Word, PDF, or epub) or a public source by URL, and Perkins distills it into a compact rulebook you review and approve rule by rule. Every extracted rule is anchored to a verbatim quote from your source; anything the machine cannot quote, it discards before you ever see it. From then on, the editors cite the work and the rule when they flag your prose, and mechanical prohibitions (banned words and phrases) run offline at every AI level, including No AI.
Can it check my story against the historical record?
Yes. Give Perkins a dated source you trust (a weather chronology, a battle timeline, any record with dates) and it becomes part of the book: stored with the project, traveling with the manuscript. Every fact is anchored to a verbatim quote from your source, and a date the machine inferred rather than read is marked so you can confirm it. Then, for any scene that carries a story date, Perkins shows you what your record says about that day, with zero AI involved, at every level including No AI. Turn the editors loose and they check the prose against the record too, quoting the lines that disagree with it. The cold-reading Reader never sees the record; its job is to notice the storm feels wrong, not to know the forecast.
Can I edit my files outside Perkins?
Yes, always. Your manuscript is plain files in a folder you own, and working on them in another editor, on your phone, or through a sync service is normal and supported. When Perkins next opens the project it notices what changed and records it honestly: the record shows those words arrived outside its sight, and a quiet chip offers you the chance to add a note saying where they came from. Add one or don't; nothing blocks, nothing nags, and nothing is ever treated as suspicious. The record simply tells the truth about what Perkins saw, and you can tell the rest.
Does this replace a human editor?
No. It replaces the draft you would have sent them. Perkins finds what careful reading and measurement can find: the sagging middle, the vanished character, the setup that never pays off. What it cannot provide is what editors are paid for: judgment about which problems matter for your book in your market, and the authority to say a manuscript is ready. Perkins refuses to render those verdicts by design, for the same reason it refuses to write your prose. Most writers never get professional editing at all; a developmental edit costs more than a laptop. Perkins is for the revising you do alone, so that if your book does reach an editor, their time goes to the things only a human reader can give you.
Which AI models does it use?
Your choice, per editor: cloud models from major providers on your own API key, or local models via Ollama for fully offline, fully private review. Route a cheap model to the Reader and a premium one to the Senior Editor. The cost meter keeps score.
Can my words stay on my machine entirely?
Yes, and you can make it a setting rather than a habit. Set a project's training posture to local models only and Perkins enforces it: the editorial team runs through Ollama on your own Mac, and no word can leave the machine, a claim verified against a live network monitor. Set a project to No AI and Perkins makes zero model calls while the whole studio keeps working. Every measurement Perkins computes itself, from voice statistics to the pacing map to the record, is offline by nature. API keys, when you use them, live in your operating system's keychain, and a middle posture restricts calls to providers whose published terms exclude training on your words.
My publisher asks about AI. What do I tell them?
The truth, and Perkins gives you both the words and the evidence. Set a project to No AI and it makes zero model calls of any kind, while the whole studio keeps working. Set it to Organizational and the machine touches only apparatus, never your prose. At every level, including Full studio, no AI-generated text can enter your manuscript. Then export an attestation: your level history, the calls made, and everything that arrived from outside the app, including your own certified notes on anything you pasted in or edited outside the app. A guide inside Perkins gives you the exact sentence for each case, and tells you plainly what the record can and cannot prove.
Can I bring my book from another app?
Yes, and it is a front door, not a chore: Import Project sits beside New and Open on the start screen. Scrivener comes in through any of its own exits, the project itself, an exported folder, an OPML outline, or a compiled manuscript. Dabble exports, Word documents, HTML, plain Markdown, folders of text files (an Obsidian vault, a Notion export, an iA Writer library), yWriter projects, and even an epub of your own book all have their own paths. Every import shows you the inferred chapters and scenes for review before anything is written, your words arrive byte for byte, and the record states plainly that the project began by import. Writing in Google Docs? Download as Word or Markdown and import that; Perkins asks for no cloud account. If your tool is not on the list, send us an export and we will add it.
What happens to my files if Perkins disappears?
Nothing. Your project is a folder of plain Markdown and YAML on your own disk, readable in any text editor, versioned in your own git history if you use one. Perkins is a studio built around your files, not a vault built around you.

Write the book. Keep every word.

Free 14-day trial, then $89 once. Yours forever. macOS, Windows, and Linux.