Enterprise DNA

Instead of Scholastica

Stop renting Scholastica. Own your peer review desk.

We build your editorial desk around your journals, bring across the agreed Scholastica records and run it for you. Your editors keep their review policies and the history behind each decision.

Scholastica lists US$10 per submission plus US$500 a year. Journals with at least 500 submissions a year qualify for the US$8 submission rate. Compare your agreement and annual volume.

  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What you pay for

Submission volume drives the peer review bill

Scholastica charges an annual fee and a submission fee. Production and journal hosting are separate services. Compare the editorial work you need before replacing a wider publishing arrangement.

file-text

Every new submission

The published rate is US$10 per submission, alongside the annual fee.

calendar

A recurring annual fee

The peer review system carries a US$500 annual fee.

layers

A volume threshold

At least 500 submissions a year qualifies a journal for the US$8 submission rate. Check how the discount applies to your agreement.

users

Assignment and reminders

Reviewer coordination, assigned tasks and reminder automation are part of the peer review service.

bar-chart-3

Journal and reviewer reporting

The service includes analytics. Scholastica also documents exports for further analysis outside its reports.

book-open

Separate publishing services

Typesetting and journal hosting have their own pricing. Define the publishing services you still need alongside the editorial desk.

Your editorial records

Own the work between submission and decision

Monday triage

Find the papers waiting for an owner

Start the meeting with late manuscripts and missing editor assignments. The queue uses your recorded dates and current review round.

  • check Unassigned manuscripts appear by age.
  • check Overdue papers show days past their due date.
  • check Each journal sets its own required review count.
  • check An editor workload summary combines open work and late work.

Reviewer follow-up

See who owes a review and what is missing

Keep deadlines, competing-interest checks and confidentiality evidence with each invitation. An invitation record does not send a message.

  • check Chase outstanding invitations and accepted reviews.
  • check Compare pending assignments with each reviewer’s recorded capacity.
  • check Flag missing interest clearance before using a review.
  • check Keep report references in your approved document store.

Editorial decisions

Carry the evidence into the next round

Editors record their judgement with a reason and evidence reference. Reviews from an earlier round never satisfy a new round’s target.

  • check Show papers with enough eligible current-round reviews.
  • check Surface differing recommendations for an editor to resolve.
  • check Retain the decision history across revision rounds.
  • check Prepare decision letters without reviewer identities.

A desk you can change

Ask the question your meeting needs

Combine your journal’s own fields and rules with the record history. A new reporting question becomes a change to your system.

  • check Keep the original imported values for reconciliation.
  • check Produce an editorial meeting pack in your journal’s colours.
  • check Review personal-information retention dates alongside follow-ups.
  • check Add your own journal-specific report through plain-language instructions.

Make it yours

Design your own Scholastica replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Scholastica. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Scholastica replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Scholastica data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Peer Review for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Peer Review for Claude Code

Connected to your own database

Which reviews need chasing this week?

code | manuscript | reviewer | status | due_on | overdue_days I-102 | M-101 | Asha Patel | accepted | 2026-10-30 | 9 I-101 | M-101 | Lee Morgan | accepted | 2026-11-01 | 7

Ask it anything

Questions your editorial desk answers today

Each question is supported by the working demonstration. These are examples of your own reporting, not claims that Scholastica cannot answer them.

chat_bubble Which overdue papers still have no eligible reviews?
chat_bubble Which reviews are late, and who owes them?
chat_bubble Which papers have enough current-round evidence for an editor to decide?
chat_bubble Which revised papers have missed their return date?
chat_bubble Who has pending reviews beyond their recorded capacity?
chat_bubble Which editor carries the largest overdue manuscript queue?
chat_bubble Which current reviews disagree about the recommendation?
chat_bubble Which review assignments lack interest clearance or confidentiality evidence?
chat_bubble What did the editor decide in each earlier round?
chat_bubble Which editorial follow-ups still need an owner to finish them?

Switching

How to switch from Scholastica

A move involves exporting your editorial records, mapping them to the new desk, checking the import and confirming what you still need from Scholastica.

  1. 1

    Export your editorial records

    Ask Scholastica for its documented CSV export of manuscripts, reviewers, invitations, reviews and decisions. Check what your account allows and confirm any export limits with Scholastica. Keep an unchanged copy of the exported files. Files, messages, author accounts and publishing assets are not part of this desk’s import, so decide separately how you will retain or handle them.

  2. 2

    Map and load the records

    Check the export’s actual column headings and map them to the fields in the new desk. Start with a test run that does not save records. Review the results, correct the mapping if needed, then load the records. The import uses an explicit field map, so do not assume the sample files or their headings match your Scholastica export.

  3. 3

    Review what the import flags

    Check the import results before relying on the records. Historical statuses with missing evidence are checked, not treated as verified decisions. Conflicting repeat records are rejected, so resolve any conflicts before trying again. Also check that your manuscript, reviewer, invitation, review and decision records are present and that the imported history makes sense to your editors.

  4. 4

    Run both desks side by side

    Keep Scholastica available for a short period while you use the new desk for editorial work. Compare the records and current work in both, and confirm that your team can find the information it needs. Check separately that files, messages, author accounts and any publishing services you still use remain accessible, since they are outside this desk.

  5. 5

    Switch off the old desk

    When your checks pass, stop using Scholastica for the internal editorial desk. Before closing or changing your Scholastica account, confirm whether you still need its submission workflows, production or hosting, which are separate services. Agree how you will retain any remaining records and handle the services you keep before ending access to Scholastica.

construction

Where the real effort goes

The import is only part of the work. The real effort is mapping your own fields and editorial rules, then deciding how much historical information to bring and how to handle files and messages outside the desk. Enterprise DNA inspects the export, maps the fields and checks the results when you have them install and run your version.

Not ready for a call?

Get your Scholastica switch plan by email

We will send you the step-by-step plan for moving your business off Scholastica, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Do it yourself, customise it, or have us run it

Open source

Do it yourself

Free, MIT licence

  1. 1 Clone the repo and run npm install, then npm run demo.
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor.
  3. 3 Use the fictional records to try the editorial commands.
  4. 4 Map your Scholastica CSV headers, run a test import and reconcile the results.
Get it on GitHub

Built around your business

We customise it

A setup fee, then a retainer

  • check Your review policies, fields and decision wording.
  • check Your Scholastica export mapping and reconciliation.
  • check A web front end or different stack where you need one.
  • check Your journal’s branded meeting packs and records.
Get your version built

Omni by Enterprise DNA

We run it for you

A setup fee, then a monthly retainer

  • check Installed and operated through Omni by Enterprise DNA.
  • check Agreed connections to your document store and other systems.
  • check Access arrangements, backups and record checks set for your journals.
  • check Ongoing changes as your editorial process develops.
Talk to Sam

Questions

Instead of Scholastica, answered

Is this a replacement for everything Scholastica sells? expand_more

The free version covers the internal editorial desk: manuscript records, review rounds, deadlines and decisions. Scholastica also offers submission workflows, production and hosting. We scope your author and reviewer access, publishing services and connections before building your version.

Can we bring across our existing records? expand_more

Scholastica documents an admin export containing manuscript, reviewer, invitation, review and decision information. We inspect your export, map the fields and check the results. Files, messages and published content need separate handling. The free version includes an explicit mapping process and a test run before records are saved.

Will earlier reviews count toward a revised paper’s decision? expand_more

No. The desk counts eligible completed reviews only for the current round. The editor can see earlier decisions and review references, but a new round must satisfy its own target. Conflicting recommendations remain an editorial judgement.

How do we protect confidential papers and reviewer identities? expand_more

Keep full manuscripts and reports in your approved document store. This desk holds the necessary records and references. Decision letters exclude reviewer identities, and an editor checks the wording before sharing. We agree access, retention and the use of external services when installing your version.

What will Enterprise DNA charge? expand_more

A setup fee, then a retainer, agreed around your journals, migration and operating scope. The free version has no software licence charge. Hosting, agent use and any publishing services you retain have their own costs.

Bring your submission volume and one editorial queue

Book 30 minutes with Sam. Show us what your editors chase each week, the Scholastica services you use and the records you need to keep. We will scope the version Enterprise DNA can build and run for you.

Peer Review for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Scholastica?

Get your version built