Spines restricts production file access

This is the core tradeoff in Spines’ model, it sells convenience by turning publishing files into a controlled asset. Instead of acting like a neutral printer and distributor, Spines handles formatting and production itself, then treats the ebook, audiobook, and POD files it creates as its property until production fees are fully paid. That makes Spines closer to a managed publishing service, while IngramSpark is closer to a distribution utility for authors who already own or commission finished files.1 2 3 4

• Spines separates book rights from production file control. Authors keep copyright in the book itself, but the files Spines creates are restricted materials under its terms until the paid production plan is completed, and Spines says it will release those files within 10 business days after full payment.1 2
• IngramSpark works the opposite way. It does not offer editing, typesetting, or design as a core service, and expects authors to upload print ready files or use its free book building tool. It is also non exclusive, so authors can distribute elsewhere at the same time.3
• Reedsy shows a third model. Authors hire editors, designers, and other specialists project by project, and by default the rights in the delivered work are assigned to the client once the fee is paid. In practice that means buying labor, not entering a gated file system.4

The market is likely to keep splitting between authors who want a done for you path and authors who want portable files and supplier freedom. As more authors learn to compare contracts at the file level, services that bundle production with tighter control will need to prove that speed and handholding are worth more than independent ownership from day one.1 2 3 4