epubio.ReleaseTwin
DESign in

RELEASE INTELLIGENCE FOR BOOKS

Your book keeps changing.
ReleaseTwin knows what that means.

A book is more than text. Metadata, design, cover, images, print profile and sales details must belong to the exact same state. ReleaseTwin keeps these relationships visible and verifiable.

7monitored source areas
5connected editions
1unambiguous book state
SOURCES01Manuscript02Book details03Design04Cover05Images06MarketReady07Print profile
RELEASETWINCURRENT BOOK STATE
EDITIONSUniversal EPUBAmazon KDPApple BooksGoogle PlayPrint book
THE REAL PROBLEM

An export can be correct — and already be outdated.

When a title, cover, price or manuscript changes after export, it is not automatically clear which file, approval or platform is affected. ReleaseTwin compares the current book state with every edition and explains the impact.

CHANGE IMPACTOne change. Clear consequences.
01

The cover is replacedReleaseTwin detects a new cover hash.

02

Affected targets are markedStore packages and the print edition are no longer current.

03

Only what is needed is rebuiltThe automation plan combines the required build steps.

04

Approvals remain unambiguousReview, quality check and handoff package belong to the new state.

FROM BOOK STATE TO PUBLICATION

Stop guessing what is still current.

01

Capture

ReleaseTwin represents manuscript, metadata, design, media, market and print data as one book state.

02

Compare

Every EPUB, store and print edition is compared with that exact state.

03

Verify

Quality, review, cover, MarketReady and print preflight form a traceable release gate.

04

Handoff

PublishCenter creates versioned destination packages and guides the external publication.

MORE THAN AN EXPORT

The control layer for the entire book.

01

Change radar

Shows which parts of the book have changed since an edition was built.

02

Dependency logic

Distinguishes whether a change affects EPUB, stores, print or several targets.

03

Release Gate

Connects technical validation, editorial approval and destination requirements.

04

Version-bound reviews

An approval only applies to the book state that was actually reviewed.

05

Destination packages

Creates files, metadata, upload guide, manifest and checksums together.

06

Publication status

Documents handoff, external review, requested changes and publication.

WHY RELEASETWIN

Formatting is a step. Publishing is a system.

TaskDisconnected tool workflowepubio with ReleaseTwin
Changes after exportManually determine which files are affectedAutomatically mark each target as current or outdated
ApprovalsOften detached from the generated fileBound to a specific book state
EPUB, stores and printSeveral exports and checklistsOne dependency and approval process
HandoffCollect files and metadata separatelyVersioned destination package with manifest and checksums
Errors and blockersInterpret a technical messageShow the reason and required next step
HUMAN CONTROL

The author stays in control.

ReleaseTwin never publishes on its own, never stores external store credentials and does not replace legal, tax or publishing decisions. It gives you an unambiguous, verified basis for those decisions.

Frequently asked questions

Does ReleaseTwin replace EPUBCheck?

No. EPUBCheck is an important technical validator. ReleaseTwin additionally connects its result with book state, approvals, print and destination packages.

Will my book be published automatically on Amazon or Apple?

No. EPUBIO prepares the handoff and guides the process. You confirm the binding publication yourself in the destination portal.

What happens after a change?

ReleaseTwin shows exactly which editions and approvals no longer match the current state and which steps need to be renewed.

Is ReleaseTwin only for EPUB?

No. It connects reflowable EPUB, store packages and print-ready output to the same book state.

ONE BOOK. ONE RELIABLE STATE.

From manuscript to publication — without version chaos.

Open existing account

Registration remains paused during the private build phase.