Literary · chapter sample
Untangling May — Chapter 1
English
Italiano
Draft under human review — not a signed edition. Page spreads below are the printed interiors these titles ship from.
Poliqa™ Beta
Translate books without losing control of the book.
DOCX or EPUB in. Translation, independent review, deterministic QA and human approval. Publication-oriented file out.
The machine drafts. You edit and sign.
EN IT English → Italian
The problem
A fluent file can still be the wrong book.
Specialist books fail in places a smooth paragraph hides: a term that drifts, a percentage that moves, a date, a currency, a cross-reference, a table that no longer matches the source. Sending the chapter to a model does not show you those differences, and it does not leave a person responsible for the file you publish.
See it
A technical sentence, taken apart.
A real 333-word extract from FX Options Volatility Trading: the source, the first translation, what independent review questioned, what deterministic QA preserved, and the editor’s decision.
Taken from the current print edition and processed through Poliqa. There is no quality score.
1,000 source words · no account
Challenge Poliqa with your own material.
Paste a passage or send DOCX, EPUB, Markdown or plain text. If the extract is longer than 1,000 source words we refuse it and tell you the count. We do not shorten the file. An operator authorises the run. You then get a private read-only link to the real screens — overview, editor, QA, terminology and Translation Bible — not an emailed block of text.
The product is the path, not the model.
Cheap AI book tools sell words. Poliqa™ sells the journal from source to a file a human will put their name on.
- Source Manuscript stays intact — structure, IDs, hashes
- Translate Staged pipeline with a Translation Bible
- Review Independent critic pass, not the same model grading itself
- QA Deterministic checks for numbers, dates, terms, structure
- Approve Editor / reviser signs — not a blank-page translator
- Edition Publication-oriented DOCX or EPUB, written back onto the original file
Human approval
This is not the typical translator.
Typical translation starts from a blank page. Poliqa™ does not. The pipeline writes the first target text; the professional’s scarce time moves to judgement: accept or decline findings, fix meaning and voice, lock terminology, and approve the manuscript under their name.
Not this
- Typing every sentence from scratch
- “AI translates your book for £9.99”
- Accept-all as a policy
This
- Editorial reviser of a controlled draft
- Proof + terminology + voice decisions
- Named human gate before export
Product tour Beta
About a minute in the product — Dashboard → Overview → Editor → Terminology → Translation Bible → QA → Export, then a CTA end card. The site stays in English; pick the voiceover language on the video.
Voiceover: English
Language packs on the floor today.
Rule packs ship for six languages. Priority pairs for Customer Zero and chapter evals:
- EN English
- IT Italian
- ES Spanish
- DE German
- FR French
- PT Portuguese
Priority pairs include EN↔IT, EN↔ES, EN↔DE, EN↔FR, IT↔ES, IT↔FR. Every listed pair is experimental until a benchmark and a reviewer are on record.
Formats
DOCX and EPUB come in, and the export is written back onto the original file in that same format. Deterministic QA can check terminology consistency, numbers, percentages, dates, currencies and source/target structure, including repeated specialist expressions.
EPUB is supported, with output validation particularly important for books with complex styling or structure. That validation checks the file against Poliqa’s own reader. It is not a promise that every EPUB will round-trip perfectly, and it is not epubcheck.
Built for houses that hold dormant rights.
Independent publishers with translation rights they cannot economically exercise. Turn a shelf of foreign-language rights into editions — not another £10 AI dump.
Also fits
Serious authors who need DOCX/EPUB fidelity and an audit trail for one novel — sold as a Book job, not a forced subscription.
Three books. Real pages. Excerpts in four target languages.
Customer Zero titles already on the shelf — interiors below, plus short openings walked EN → IT / FR / DE / ES. Switch book and language; English stays on the left.
-
Literary
Untangling May
Interior pages 36 & 47 · EN → IT / FR / DE / ES
-
Nonfiction
Blood and Bone
Interior pages 98 & 141 · EN → IT / FR / DE / ES
-
Technical
The Coordination Capital Doctrine
Interior pages 73 & 95 · EN → IT / FR / DE / ES
Offers by seats and source-word tokens Beta
Hosted checkout prices are in pounds. The allowance is still source-word tokens and seats. Private stays a licence for your own infra.
Chapter eval
Sample
1 seat · one chapter
Prove the workflow on one chapter — a private, read-only view of your Bible, terms, findings and QA. A shorter first step is the 1,000-word challenge.
1,000-word challenge Request a chapter evalBook job
£49 / £99
one-off · 2 seats
One manuscript, one language pair. Standard is £49 for 100k tokens. Full audit is £99 for 250k tokens.
Studio
£79/mo
250k tokens · 3 seats
Steady pipeline for a micro-publisher: terminology, TM and full QA in the control panel.
Publisher
£199/mo
1M tokens · 12 seats
House scale: shared terms, series memory, API, policy and volume — managed from the panel.
Private
Licence
Your infra · custom seats
Regulated or confidential titles on your network. Indicative Beta licence £7.5–15k / yr — talk to us.
The pounds on these cards are the Stripe checkout amounts. Tokens = source manuscript words processed in the hosted pipeline (not opaque “AI credits”). Unused monthly tokens do not roll forever in Beta; book-job packs are one-off. Seat counts are hard caps in the control panel.
Request a free chapter eval Beta
Send one chapter. Attach DOCX, Markdown, plain text, or EPUB. After we authorise your request we email you a private, read-only link to the real Poliqa screens for your chapter (overview, editor, QA heat-map, terminology and Bible); PDF and other formats get a personal follow-up from info@poliqa.com.
FAQ Beta
Straight answers for publishers and authors evaluating Poliqa™ Beta.
What does “Beta” mean here?
The product is live and usable on real manuscripts. Workflow details, language coverage and list prices may still tighten as we onboard more houses. We will not silently change your signed outputs.
Is this blank-page machine translation?
No. Poliqa™ drafts a controlled target; a named human revises findings, terminology and voice, then approves. Nothing is treated as publication-ready until that gate.
What is a free chapter eval?
You send one chapter of your manuscript. Once we authorise the request we run the pipeline and email you a private link that opens a read-only view of your chapter in the real Poliqa screens — Bible, terms, findings, QA heat-map — so you can judge the workflow, not a sales demo of cherry-picked prose. You cannot edit or download from the demo link; it expires after 14 days.
Can I send every chapter one by one?
Chapter evals are one chapter per email address (and a small number per network) in any 30-day window, so the free evaluation is not a way to translate a whole book. For a full manuscript, see the book job and subscription plans above.
Which languages are available?
Rule packs today: English, Italian, Spanish, German, French, Portuguese. The marketing samples show EN → IT / FR / DE / ES for three Customer Zero titles. Priority pairs for Beta include EN↔IT, EN↔ES, EN↔DE, EN↔FR, IT↔ES, IT↔FR. Ask if you need another direction.
Who sees my manuscript?
Hosted jobs run on our Contabo infrastructure with access limited to your account operators. You can bring your own model keys. For regulated or confidential titles, use Private — your network, your database, your credentials.
What file formats do you support?
DOCX and EPUB are ingested and exported in the same format, using the original file as the template. EPUB is supported, with output validation particularly important for books with complex styling or structure. PDF and legacy DOC are handled manually.
Book job vs Studio vs Publisher — which do I need?
One manuscript → Book job (one-off token pack, 2 seats). A steady trickle of titles → Studio (250k tokens / month, 3 seats). A house with shared terms and volume → Publisher (1M tokens / month, 12 seats). Confidential self-host → Private. Your control panel shows seats, token balance and plan tools for whichever offer you are on.
What is a token?
A hosted source-word token: roughly one word of source manuscript processed through the pipeline. We do not sell opaque “AI credits.” Pack and monthly ceilings appear in your control panel.
Can I export before human approval?
You can download a draft marked for review. The approved Word (or edition) file stays locked until a named person signs the manuscript.
How do I get support or ask a commercial question?
Email info@poliqa.com — support, chapter evals, Private licences and Beta feedback all go there.
What Beta includes today — and what we will not overclaim.
- Staged translation pipeline with separated translator and reviewer providers
- Translation Bible, terminology, translation memory
- Deterministic QA for numbers, dates, currencies, terms and structure
- Human approval gates and export with the original format as template
- Bring-your-own AI keys and allow/block provider policy
Poliqa™ Beta. Workflow, pairs and pricing may tighten as we take on more houses. Feedback and support: info@poliqa.com.
Private is a licence, not a GitHub dump.
Manuscripts never need to touch shared SaaS when confidentiality requires it. Images, upgrades and support on your infrastructure — priced for that burden.
Ask about Private- Deploy inside your network
- Your database and storage
- Your model credentials
- Provider allow/block policy
- Audit logs and upgrades