Managed OJS Hosting — production-ready from $11 a month
Open Journal Systems for managing peer review and publication of scholarly journals. Deployed on your own dedicated instance in AWS, Azure, or GCP, kept patched, backed up, and monitored by ManageStacks — standard OJS, no lock-in.
OJS on ManageStacks is Open Journal Systems, the Public Knowledge Project's software for running a scholarly journal, deployed to your own AWS, Azure, or GCP region — flat per-app pricing from $11 a month ($25 on the Standard production plan). Universities and societies use it to handle submissions, peer review, and publishing instead of commercial platforms like Editorial Manager.
What does OJS do, and why do teams deploy it?
Open Journal Systems, or OJS, is journal management software from the Public Knowledge Project, written in PHP. It covers the editorial workflow of a scholarly journal: authors submit manuscripts, editors assign reviewers, reviewers return feedback, and accepted work moves through copyediting and production to publication. The same installation also publishes the journal website, with issues, articles, and archives. Roles for authors, reviewers, editors, and managers keep responsibilities separate. Running it yourself lets an institution keep control of its publications and editorial records, rather than depending on an outside publishing vendor.
- Online manuscript submission portal for authors and co-authors
- Reviewer assignment and double-blind peer review workflow
- Editorial roles for editors, reviewers, and journal managers
- Copyediting and production stages before publication
- Public journal website with issues and article archives
- Email notifications at each stage of the review process
Open Journal Systems for managing peer review and publication of scholarly journals
OJS as a self-hosted alternative to Editorial Manager and ScholarOne
Instead of paying per-seat fees to a SaaS vendor, teams self-host OJS to keep full control of their data and infrastructure. ManageStacks removes the operational overhead — you get the cost and privacy benefits of open source with the reliability of a managed platform.
What does managed OJS hosting cost?
Flat per-app pricing, in your chosen AWS, Azure, or GCP region. No per-user pricing — a busy deployment costs the same as a quiet one.
Starter
Staging and internal tools. Dedicated instance, TLS, daily backups, managed upgrades.
Standard
Production workloads. Adds monitoring, staging environment, region choice, priority support.
Business
High-traffic and compliance workloads. Adds a high-availability replica and same-day support.
24×7 SRE retainer
Round-the-clock on-call across every hosted application, for teams that need a pager answered at 3am.
When is self-hosting OJS the right answer instead?
“Managed hosting is not always the correct call.”
Self-host when a platform team already runs the infrastructure and on-call rotation to operate OJS at genuinely low marginal cost. Self-host when compliance requires an air-gapped or on-premises deployment that no hosted option can satisfy. And self-host when the deployment depends on heavy customisation with a fast internal build-deploy loop, because an internal release process will beat any managed change process.
For everyone else — teams whose engineers have better things to do than shepherd upgrades — managed hosting is cheaper than the hours it replaces.
Which cloud should OJS run on — AWS, Azure or GCP?
For most workloads, the choice of cloud matters less than proximity: run OJS in the same cloud and region as the applications and data it talks to, because every request between them adds a round trip. The underlying compute performs equivalently across AWS, Azure, and GCP.
In practice, an existing cloud footprint decides it. All plans support all three clouds, and moving regions later is a scheduled migration, not a rebuild.
Deepest managed-service catalog, default when there's no existing footprint
Best fit for teams already on Microsoft 365 or Entra ID
Strongest for data/analytics-adjacent workloads
Every plan supports AWS, Azure, and GCP — region choice included.
Common questions about OJS on ManageStacks
What is OJS on ManageStacks?
It is a managed Open Journal Systems installation in your own cloud account for running a scholarly journal. ManageStacks provisions the database, file storage, SSL, and backups so editors can focus on the journal.
How does OJS compare to Editorial Manager?
Editorial Manager is a commercial submission and review system used by publishers. OJS is free software from the Public Knowledge Project that also publishes the journal site, so one tool covers submission through publication. Large publishers may want features it does not include.
Does OJS support peer review?
Yes. Editors can assign reviewers and run blind review, and reviewers send recommendations through the system. The editor then decides on acceptance, revisions, or rejection, and the full history is kept with the submission.
Can I move an existing journal to ManageStacks?
Yes. A journal can be migrated by restoring its database and uploaded files into the new installation, ideally on the same or a compatible OJS version. Your content stays in your own cloud account, and you can export it at any time.
How are upgrades and backups handled?
Backups of the database and files are part of the managed stack. OJS upgrades are applied for you, but it is wise to test plugins and themes first, since journals often depend on them for their appearance and workflow.
Other devtools tools on ManageStacks
WordPress
Open-source publishing platform for websites, blogs, and online applications
GitLab
Single DevOps platform for Git hosting, CI/CD pipelines, code review, and security scanning
Drupal
Open-source content management platform for structured, multi-author websites
Joomla
Open-source content management system for websites and online applications
Run OJS without carrying the pager
Subscribe through your AWS, Azure, or GCP marketplace. We handle provisioning, SSL, monitoring, backups, updates, and security. From $11/mo.