Why we built Revise
Revise is scholarly publishing software built by people who work inside scholarly publishing, for journals that have been asked to do a lot with very little.
The problem we kept running into
Journals outside the large commercial publishers are expected to run the same workflow as those that have entire production departments: structured submission, rigorous peer review, JATS XML for indexing, author proofreading, archival-quality output. The standards are the same. The budgets are not.
What usually fills the gap is a patchwork — email threads for peer review, spreadsheets for reviewer contacts, an outsourced vendor for XML, and PDFs marked up by hand. It works, but it leaks. Manuscripts stall in inboxes, reviewer records live in one person's laptop, and the same metadata gets typed in four times.
What Revise does about it
Revise splits the workflow where it naturally breaks — at the moment of acceptance — and gives each half a platform built for it. Revise[Submit] covers submission, peer review, and editorial decisions. Revise[Production] covers JATS XML, proofreading, and publication-ready output. Acceptance is the only handoff, and it carries the manuscript and its metadata across.
It is built on Laravel and Livewire — deliberately ordinary, widely supported technology — so a journal can host it on its own infrastructure without needing a specialist to keep it running. No vendor lock-in, and no requirement to migrate off Open Journal Systems if that is what you already use.
Who builds it
Revise is developed in Indonesia by a small team working closely with the journals using it. Both Revise[Submit] and Revise[Production] are live and in production use today, shaped by feedback from those same journals.
Accessible by design
We offer dedicated terms for journals in the Global South and for Diamond Open Access titles. Quality publishing infrastructure should not be gated behind a currency you do not earn in — that principle is why this exists, not a marketing line added afterwards.
Talk to us
We would rather hear about your journal than guess at it. Write to hello@revise.id, or see the contact page for the fastest route to the right person.