Your press's catalog, website, and digital reading in one place.

For university presses, commercial publishers, and editorial imprints, with a validated EPUB and protected access for classes and groups.

Editorial production schedule in Studio, in light mode
Papo, the Papaya character, reading while walking

What changes in the publishing operation

See the work, not just a feature list.

The captures below show the Studio and real Papaya.Pub operations.

Catalog

Titles and metadata in a trusted source

Books, contributors, formats, covers, ISBNs, and publication status stay organized for use across other channels.

View details for this area about Titles and metadata in a trusted source
Catalog bibliographic record in Studio, in light mode

From preparing a book to reaching its readers.

01Add the title and formats
02Feature it on the website
03Publish news and campaigns
04Provide and monitor access

Each area has its workflow: prepare the book, organize the catalog, publish on the website and manage digital access. The team chooses the modules it needs and who can work in each one.

See who it is for

Frequently asked questions

Privacy policy

How much does Papaya cost?

Plans are tailored to the publisher's operation. The site does not publish prices. The demo starts from the team's routine.

Can I bring the catalog I already have?

Yes. In Studio, someone with permission downloads the template, imports the book spreadsheet, reviews the report, and confirms before anything is saved. New works land as drafts. Covers and files are added later, on the record. Each file accepts up to 200 books.

Does Papaya send books to Amazon, Google Books, or distributors?

No. The record keeps the files and the distribution links. Sending to stores stays with the publisher's distributor.

Does Papaya register DOIs?

No. ISBN and DOI are fields on the work record. Registering the identifier stays with the agency, outside the platform.

Does the AI change the EPUB on its own?

No. Drafts and repairs only enter the EPUB when the team accepts them.

How do I reach the team?

Through the demo form or at contato@papaya.pub. The conversation starts from the publisher's routine.

What about LGPD and data security?

The privacy policy describes the processing. On a publisher's website, the publisher is the controller and Omnidev acts as the processor. Each publisher has its own environment, with roles, permissions, sessions that can be revoked, and a history of published versions.

Can a public institution buy it?

Purchasing is by proposal, on a plan tailored to the institution. Talk to the team to review the purchasing format for your institution.

See how Papaya fits your publishing workflow.

Tell us how you manage your catalog, website, content, and reading today. The demo starts with your real process.

Plans tailored to your press.

Request a demo