sciflow.org — SciFlow's open-source program. The app and SciFlow Publish are on sciflow.net →
For journal editors, university presses & publishers

Structured publishing, right inside your OJS.

Give authors and editors a real manuscript editor inside Open Journal Systems, and get clean, media-neutral JATS out the other side — no Word cleanup and no typesetter round-trips.

OJS 3.4+works with your version
Open sourceno vendor lock-in
JATSmedia-neutral export
OJS from submission to presentation OJS is present the whole way. A DOCX submission arrives in OJS; OS-APS or SciFlow Publish ingest and structure it; it is edited on the open editor core; OS-APS or SciFlow Publish typeset and render it to a PDF, the Reader and JATS XML; and those finished files live in OJS, the presentation layer for the journal. OJS — the journal, start to finish SUBMISSION ARRIVES IN OJS DOCX manuscript OS-APS · SCIFLOW PUBLISH Ingest & structure DOCX → structured article OPEN EDITOR CORE Edit the structured article one open format · JATS OS-APS · SCIFLOW PUBLISH Typeset & render PrinceXML / Paged.js PDF Reader JATS XML OJS · PRESENTATION LAYER the finished journal lives here
One compatible open format the whole way: OS-APS or SciFlow Publish ingest the DOCX and render the PDF, Reader and JATS XML — and the finished files live in OJS, the presentation layer for the journal.
Supported by
One open editor core

The same editor behind OJS, OS-APS and SciFlow

This is the open-source SciFlow editor — the shared foundation under Open Journal Systems, the Open Source Academic Publishing Suite and the SciFlow platform. Adopt it in OJS and your content stays natively compatible with all three: run OJS as you do today, or grow into OS-APS and a managed platform when you're ready.

Your journal today

OJS

Where your journal already lives. The editor slots into the submission workflow your editorial team uses.

Run it yourself

OS-APS

The publicly funded Open Source Academic Publishing Suite for presses — the same editor, with media-neutral exports to PDF, HTML, EPUB and JATS.

Scale up when ready

SciFlow

The managed publishing platform for live collaboration, manuscript import and hosted exports — without changing the underlying content model.

All three build on one open-source editor core — standards-based and openly licensed, for the long term.

Meets your OJS where it is

Start on any recent OJS — integrate deeper when you can

You don't need the newest OJS release to begin. The open OJS XML format works across current releases today; the SciFlow editor integrates directly into OJS 3.6 and up, and the Reader plugin reaches back to 3.4.

Available now
OJS 3.4+

Exchange via OJS XML

OS-APS and SciFlow both support the native OJS XML format today. Move articles in and out of OJS through the format your installation already speaks — no plugin and no upgrade required.

In development
OJS 3.6+

Edit inside OJS

The SciFlow manuscript editor integrates directly into OJS 3.6 and up — authors and editors write structured, media-neutral content inside the journal, with no separate tool and no Word round-trip.

In development
OJS 3.6+

Push and typeset with the plugin

A SciFlow Publish plugin for OJS 3.6 and newer is in development: typeset finished articles and push them straight into OJS, syncing article metadata both ways — no manual re-keying between your production workflow and the journal.

In development
OJS 3.4+

Read in OJS with the Reader plugin

A Reader plugin brings the accessible SciFlow Reader into OJS — so published articles are read in the browser on the very same structured data, with no re-export.

It's all the same structured data — so as the plugins land, finished articles move into OJS and into the Reader without ever leaving your journal.

What it means for your journal

Structured content, from first draft to archive

Because the article is structured while it's being written, the work you used to do at the end isn't needed.

Structure from the first draft

Authors write with real headings, citations, figures and equations. The article is machine-readable from day one — not reconstructed from a formatted file at the end.

Media-neutral by default

One clean source generates JATS XML and feeds PDF, HTML and EPUB downstream. Publish to the web, to print and to archives from the same content.

No Word cleanup, no round-trips

Editing happens on the structured article itself, inside OJS. Skip the export-to-Word-and-back cycle that loses formatting and quietly introduces errors.

Accessible reader output

Semantic HTML and a built-in reader mean your articles meet accessibility expectations — not just look right on the printed page.

Runs where your journal lives

No new platform to migrate to and no separate login. The editor slots into the OJS submission workflow your team uses every day.

Open source, here to stay

Because the editor is open source, OJS can keep using it indefinitely — no vendor can lock it away. Content stays in open standards like JATS, good for long-term preservation.