Revise

Scholarly publishing software

Give every manuscript a clear path to publication.

Revise brings peer review and production together for journal teams of every size. Editors see where every submission stands, authors always know what happens next, and accepted articles come out ready to publish.

Talk to us See how Revise[Submit] works
An author submits a manuscript, an editor carries it to acceptance, a production specialist prepares the article, and the published paper reaches the world, across four rising stepping stones.

Two platforms, one manuscript.

Every journal does two kinds of work: getting a manuscript to a decision, and turning it into a published article. Revise has a platform for each, and they pass the work to each other.

Before acceptance

Revise[Submit]

submit.revise.id

For everything that happens between a new submission and an editorial decision.

Authors submit through a guided portal. Editors triage new manuscripts, invite reviewers from their own contact pool, run as many revision rounds as a paper needs, and send clear, structured decision letters. Your reviewer database and outreach sit right alongside, so there is no spreadsheet to keep in sync.

Submission intake
Peer review
Revision rounds
Editorial decisions
Reviewer database
Email campaigns
Revise[Submit] in detail
After acceptance

Revise[Production]

production.revise.id

For everything that turns an accepted manuscript into a published article.

Content and metadata are structured into valid JATS XML in a visual editor, with references filled in from Crossref DOIs. Authors check their proofs in the browser, corrections and questions stay together in one thread, and you finish with PDF and XML ready to deposit.

JATS XML editing
Metadata & references
Standards validation
Author proofreading
Query tracking
Publication output
Revise[Production] in detail

How it works

One handoff, at the moment of acceptance.

When a manuscript is accepted, it moves into production with all its details attached, so there's nothing to export, re-type, or chase by email.

How a manuscript moves through Revise A flow in two rows. Top row, Revise[Submit]: submission intake, peer review, editorial decision. The flow then passes through an acceptance gate carrying manuscript and metadata, into the bottom row, Revise[Production]: JATS XML production, author proofing, publication output. ACCEPTANCE manuscript + metadata 01 02 03 04 05 06 REVISE[SUBMIT] REVISE[PRODUCTION] Submission intake Peer review Editorial decision JATS XML production Author proofing Publication output
Six stages, one gate. The manuscript passes acceptance once, carrying its metadata with it.
  1. 01 Revise[Submit]

    Submit & review

    Authors submit through a guided portal, with the key details captured up front. Editors triage, invite reviewers, and see at a glance who has responded.

  2. 02 Revise[Submit]

    Decide

    Accept, request revisions, or decline with structured decision letters. Each new version is tracked against the last, for as many rounds as it takes.

  3. 03 Revise[Production]

    Produce

    The accepted manuscript arrives with its metadata intact and is structured into valid JATS XML, with references filled in from Crossref.

  4. 04 Revise[Production]

    Proof & publish

    Authors mark corrections right on the proof and answer queries in the same thread. Final PDF and XML come out ready to deposit.

Built for the three people who keep a journal moving.

Editors

Many editors run a journal alongside their own research and teaching. Revise keeps the queue easy to read in a few minutes: what has arrived, who is reviewing, and what is waiting for your decision.

Publishers

Looking after several titles means consistent standards, the right settings for each journal, and confidence in your data. Your content stays in open formats — JATS XML and PDF — so it is always yours, wherever you take it.

Authors

Authors meet Revise twice: when they submit and when they check their proof. Both are designed to be done in one sitting on a laptop, and authors can always see where their manuscript stands.

Where we stand

The thinking behind Revise.

Accepted work carries its details
When a manuscript is accepted, its metadata travels with it into production. No exporting, no re-typing, and no files sent back and forth.
Works alongside OJS
Many journals rely on Open Journal Systems, and for good reasons. Keep OJS for what it does well, and use Revise for the parts of your workflow you would like to run differently.
Familiar, dependable technology
Revise is built on Laravel, Livewire, and Tailwind — a widely used stack that most university IT teams can host, maintain, and review with confidence. Chosen to last.
Host it yourself, or let us
Run Revise on your own servers or let us look after it for you. It is the same software either way, and you can switch later.
Made in Indonesia
Revise is built in Indonesia, close to the journals it serves. Keeping it practical and affordable to run was part of the design from day one.
Publication-ready output
Valid JATS XML, Crossref-ready metadata, and archive-ready PDF — the same standards the large publishers work to, for journals of any size.

Pricing that fits your journal.

Every journal is different: a society journal with forty articles a year needs something quite different from a press running twelve titles. Tell us a little about yours, and we'll put together a quote that fits.

Based on what you publish

We quote on the number of titles, your submission volume, and which platform you need — not per user.

Start with what you need

Begin with one platform and add the other whenever it suits your journal. Nothing has to change all at once.

Self-hosted or managed

Run it on your own infrastructure under a licence, or let us host and maintain it. We can price both, so you can compare.

Request a quote Prefer to see it first? Book a demo

Questions

Questions we often hear.

Can't find yours? Write to us — we're happy to help.

Software for scholarly journals. Revise helps you run peer review and produce the published article, with two connected platforms that meet at the moment of acceptance.

Tell us about your journal.

Send us a short note about your journal and what you'd like to make easier. You'll hear back from someone who works on Revise — and if it isn't the right fit, we'll tell you honestly.

Start with Revise[Submit] Start with Revise[Production]

hello@revise.id · usually answered within one working day