Upload a clean DOCX
Bring the manuscript text you actually want translated. Remove backmatter, ads, and signup pages unless you want them translated too.
Early access for author-led translation workflows
Project Arachne
A Cassie Alexander Studios project.
Arachne helps authors turn a clean manuscript into a reusable translation workspace: style sheet, glossary, voice profiles, canon facts, translation runs, final review, and series memory for the next book.
From Cassie Alexander Studios
Built inside an author studio that publishes, tests, and learns in public.
Project Arachne is one of the publishing tools growing out of Cassie Alexander Studios: author-led, practical, and built around real books moving into real markets.
Visit Cassie Alexander Studios for Cassie's books, experiments, production notes, and broader studio work.
Built for authors, not engineers
One careful path from manuscript to reviewed files.
Approve the style sheet
Arachne drafts a project style sheet, glossary, voice profiles, canon facts, title notes, and a locked dossier before translation starts.
Use your own keys
OpenAI and Anthropic keys are pasted per job. They are sent only to that worker process and are not saved to your account.
Review the final choices
Translation runs continue on the Project Arachne server. When the work is done, you preview and download the selected final markdown.
Book workspace access
$50 per book workspace.
One-time access for one book. Translate that book into as many target languages as you want using your own OpenAI and Anthropic keys.
What the workspace keeps for you
- The project dossier you generate and approve for that book
- Your approved style sheet, glossary, voice profiles, canon facts, and title precedents
- Reusable series or shared-universe memory when you opt in
- Final markdown previews and downloads for that book
- The ability to come back later and run more languages for the same book
API/model usage is not included. Provider charges are billed directly by your own OpenAI and Anthropic accounts. Arachne does not save your provider keys.
Language defaults matter
Arachne does not treat every language like English with different words.
Spanish is aimed at broadly readable Latin American Spanish, with a Mexican-friendly center of gravity.
Arabic uses generalized Modern Standard Arabic and preserves right-to-left script behavior.
Every language gets its own handling for script, punctuation, formality, and reader expectations, from right-to-left Arabic and Hebrew to CJK layout, Romance-language register, and Brazilian Portuguese market norms.
Idioms, voice, and continuity
The point is not word-by-word translation. The point is carried meaning.
Arachne builds a project style sheet before translation so jokes, insults, endearments, recurring phrases, heat level, and character voice have context.
When an idiom does not survive literally, Arachne can look for the target-language move that carries the same emotional and narrative job.
Approved glossary, voice, canon, and translation lessons can be reused for later books in the same series or shared universe.
Current beta languages
Available language lanes.
Current beta language support includes these target languages. Some lanes have more live book-mileage than others; Arachne keeps improving as books move through the system.
Arabic (ar)
Czech (cs)
Danish (da)
German (de)
Greek (el)
Spanish (es)
Finnish (fi)
French (fr)
Hebrew (he)
Hindi (hi)
Hungarian (hu)
Indonesian (id)
Italian (it)
Japanese (ja)
Korean (ko)
Dutch (nl)
Norwegian (no)
Polish (pl)
Brazilian Portuguese (pt_br)
Romanian (ro)
Russian (ru)
Swedish (sv)
Thai (th)
Turkish (tr)
Ukrainian (uk)
Vietnamese (vi)
Simplified Chinese (zh_cn)
Traditional Chinese (zh_tw)
Current access shape
Early access is open, with beta guardrails.
Project Arachne is still beta software, but authors can open the app and start with a book workspace. Current believer beta testers keep free lifetime beta access while we shake out the workflow.
What testers need to know before they touch the app.
Bring the right file
Use a DOCX that contains only the manuscript text you want translated. Remove backmatter, ads, signup copy, and unrelated bonus material unless those should be translated too.
Use your own provider keys
Arachne asks for OpenAI and Anthropic keys only when launching a live job. Keys are job-scoped and are not saved in project history.
Start with a test chunk
Run one representative chunk first to estimate cost, inspect voice, and make sure the book's style sheet is doing what the author expects.
Queue, then come back
Once a translation job starts, it keeps running on the Project Arachne server. Closing the laptop does not stop the job. Revoking the provider key is the emergency brake.
Pay per book, not per language
The planned paid unit is one book workspace. Your workspace keeps that book's dossier and memory so you can return later and run more languages with your own keys.
Not ready yet?
Get Project Arachne updates.
Use this if you want beta notes, launch updates, or a reminder before you start a book workspace.