- OJS runs on most PHP hosting, but good OJS hosting also gives you cron, SSH, a files directory outside the web root, reliable SMTP and complete backups.
- Shared hosting suits small single journals; VPS or managed OJS hosting suits growing or multi-journal sites; managed is best when you have no server administrator.
- When you move hosts, keep the same domain and URLs so DOIs, Google Scholar and citations keep working.
What good OJS hosting needs
Open Journal Systems is a PHP application with a database, so almost any web host can run it. Choosing the best hosting for OJS is about more than whether the installer runs. A journal stores unpublished manuscripts and reviewer identities, sends hundreds of emails, and must stay online at the same address for years so that DOIs and citations keep working.
Before comparing OJS hosting options, know the essentials:
- A PHP version that matches your OJS release (PHP 8.2+ for OJS 3.5), with the required extensions.
- MySQL/MariaDB or PostgreSQL.
- A files directory outside the web root for manuscripts and review files.
- Cron jobs for reminders, statistics and DOI deposits.
- Authenticated SMTP email that reaches inboxes.
- HTTPS and backups of the database, files directory and
public/folder.
The full technical list, including php.ini values and Apache/Nginx configuration, is in our OJS system requirements guide.
OJS hosting options compared
There are five realistic ways to host an OJS journal. Here is how they compare:
| Option | Control | Skills you need | Who handles OJS updates and security | Best for |
|---|---|---|---|---|
| Shared / cPanel hosting | Limited | Basic (cPanel, file manager) | You (server by the host) | One small journal, simple needs |
| VPS / cloud server | Full | Linux administration | You, entirely | Teams with a capable sysadmin |
| Managed OJS hosting | High, through the provider | Little or none | The provider | Journals without in-house technical staff |
| University / institutional server | Depends on IT policy | Depends on IT support | Institutional IT, often shared with the journal team | University journals with engaged IT departments |
| PKP Publishing Services | Depends on the plan | Little or none | PKP | Journals that want hosting from OJS's developers |
Shared (cPanel) hosting for OJS
Shared hosting puts many websites on one server. The host maintains the operating system, web server and PHP, and you manage your account through cPanel or a similar panel.
Pros
- Quick to start; no server administration.
- SSL, email and databases available through the panel.
- Usually lets you pick a PHP version per site.
Cons
- Resource limits (CPU, memory, processes, file counts) that can slow OJS during traffic spikes or statistics processing.
- Shared IP addresses can hurt email deliverability.
- Some plans have no SSH, restrict cron or cap upload sizes.
- One compromised site on a poorly isolated server can affect others.
Suits: a single journal with modest traffic and someone comfortable with cPanel. Make sure you can create a folder next to (not inside) public_html for the OJS files directory.
VPS and cloud servers
A virtual private server (VPS) or cloud instance gives you your own operating system with guaranteed CPU and RAM. You install and maintain everything: web server, PHP, database, firewall, SSL renewals, backups and OJS itself.
Pros
- Full control over PHP versions, limits and Nginx/Apache configuration.
- Predictable performance; easy to scale up.
- Ideal for multi-journal installations and OJS alongside OMP or OPS.
Cons
- You are responsible for security patches, monitoring and backups.
- Many cloud providers block outbound mail ports by default, so email needs extra setup.
- A neglected VPS becomes a security risk quickly.
Suits: publishers and universities with a Linux administrator. Our VPS installation steps show the basic setup.
Managed OJS hosting
Managed OJS hosting is offered by academic journal hosting services that specialise in Open Journal Systems. The provider runs a server tuned for OJS and usually handles installation, updates, backups, SSL, email configuration and security monitoring, with support staff who understand OJS rather than general web hosting.
Pros
- No server work for the editorial team.
- OJS-specific configuration, upgrades and troubleshooting.
- Faster help when something breaks, from people who know OJS.
Cons
- You depend on the provider's skills and responsiveness.
- Less direct server access on some services.
- Quality varies widely; use the checklist below.
A good OJS hosting service should include, at minimum:
- Installation of an official PKP release, with the files directory outside the web root.
- Prompt security updates and planned upgrades, tested against your theme and plugins.
- Daily off-site backups of the database, files directory and
public/folder, with restores on request. - Working SMTP email, cron jobs and HTTPS from day one.
- Monitoring for downtime, malware and spam registrations.
- A clear way to get your complete data back if you ever leave.
Suits: journals without in-house technical staff, and editors who want to spend their time on editorial work. OJS Academy offers this through our OJS hosting service.
University and institutional servers
Many university journals run on servers managed by the institution's IT department or library.
- Strengths: institutional domain (which adds credibility), long-term stability, existing backup and security processes, and data stays within the institution.
- Weaknesses: IT teams may not know OJS, PHP versions can lag behind, firewalls may block Crossref or ORCID connections, and change requests can take weeks.
Suits: university journals where IT is willing to support OJS. Agree in writing who applies OJS updates, who handles email deliverability and how quickly security patches go in. Upgrades are where institutional setups most often fall behind.
Hosting from PKP itself
The Public Knowledge Project, which develops OJS, runs its own hosting arm, PKP Publishing Services. It hosts journals, presses and preprint servers on OJS, OMP and OPS, and also offers services such as training, theme and feature development, content migration and Crossref-related support.
- Strengths: hosting from the team that builds the software, close alignment with new releases and PKP's documentation.
- Things to check: which plugins and custom themes your chosen plan allows, what level of server access you get, how support works, and what help is included with editorial setup and indexing.
Compare PKP's service with independent providers using the same checklist below. OJS Academy is independent and not affiliated with PKP.
Which OJS hosting option suits your journal?
| Your situation | Sensible choice |
|---|---|
| One new journal, small team, someone comfortable with cPanel | Good shared hosting that passes the checklist, or managed hosting |
| No technical person on the team | Managed OJS hosting or PKP Publishing Services |
| Several journals, growing traffic, an in-house sysadmin | VPS or cloud server |
| Several journals, no sysadmin | Managed OJS hosting on a VPS |
| University with supportive IT and a policy to host internally | Institutional server, with clear responsibility for updates |
| Journal recovering from a hack or repeated downtime | Clean up first, then move to managed hosting or a hardened VPS |
What to check before choosing an OJS host
Ask every provider these questions, in writing if possible:
- PHP versions: Is PHP 8.2 or newer available, with mbstring, intl, xml, gd, zip and curl? Can you switch versions per site?
- SSH access: Is it available? It makes upgrades, command-line tools and troubleshooting far easier.
- Cron jobs: Can you schedule tasks at least hourly (every minute for OJS 3.5's scheduler)?
- Folder outside the web root: Can you create the OJS files directory outside
public_html? - Backups: Are the database and the files directory and
public/folder backed up daily, stored off-site, and kept for weeks? Can you restore on request, and have you tested it? - Email: Is authenticated SMTP available? Is the server IP clean of blocklists? Can you set SPF, DKIM and DMARC?
- SSL: Free automatic certificates (for example Let's Encrypt) with auto-renewal?
- Server location: Close to most of your readers and editors, and compatible with any data-residency rules your institution follows?
- Security: Web application firewall, malware scanning, account isolation, brute-force protection and prompt OS patching?
- Upload limits: Can
upload_max_filesize,post_max_sizeandmemory_limitbe raised to suit your journal? - OJS-aware support: Will support staff recognise problems like PATH_INFO errors, failed scheduled tasks or OJS email settings?
- Upgrade help: Who upgrades OJS when a security release comes out, and who tests themes and plugins afterwards?
- Data ownership: Is the domain registered in your name, and can you export the full database and files at any time?
Red flags in OJS hosting offers
Walk away if you see these
- Promises of indexing in Scopus, Web of Science or Google Scholar as part of hosting. No host can deliver that.
- Old PHP only, or an OJS version that is years behind the current release.
- Files directory inside
public_htmlby default, which exposes unpublished manuscripts. - Backups that skip the files directory, or "backups are your responsibility" with no tools provided.
- The domain registered in the provider's name, or no way to export your data.
- Modified or unofficial OJS packages instead of PKP's official releases.
- No SSH, no cron and no SMTP on the same plan.
- "Unlimited" everything with no stated limits on CPU, memory or processes.
Also be cautious with one-click installers: check which OJS version they install, where they put the files directory, and whether they keep up with PKP security releases.
How much server do you need for OJS?
As a rough guide, which depends on traffic, bots and file sizes rather than any fixed rule:
- Small: one or two journals with modest traffic: 1–2 vCPU, 2–4 GB RAM, 20–40 GB SSD.
- Medium: three to ten journals or one busy journal: 2–4 vCPU, 4–8 GB RAM, 50–150 GB SSD.
- Large: ten or more journals, high traffic or large datasets: 4–8+ vCPU, 8–16 GB+ RAM, 200 GB+ SSD.
Disk usage grows steadily, because OJS keeps every manuscript version, review file and galley. Aggressive crawlers are a frequent cause of slowdowns, so bot filtering often helps more than extra CPU. More detail is in the sizing section of our requirements guide.
Moving OJS hosts without breaking URLs or DOIs
A host move should be invisible to readers, Google Scholar and Crossref. Follow this order:
- Keep the same domain and URL structure
Keep the journal path, the clean-URL setting (
restful_urls) and HTTPS exactly as they were. DOIs and indexed links then keep working without any changes. - Match the OJS version
Install the same OJS version and a compatible PHP version on the new server. Migrate first, upgrade later, so you only change one thing at a time.
- Copy all three parts
The OJS code (including
config.inc.php), a full database dump, and the files directory plus thepublic/folder. Missing the files directory is the most common migration mistake. - Update configuration
Adjust database credentials and the
files_dirpath inconfig.inc.php. Leavebase_urlunchanged if the domain stays the same. - Test before switching DNS
Point your own computer at the new server (for example with your hosts file) and test logins, downloads, submissions and email.
- Pause editorial work and switch
Lower the DNS TTL a day ahead, freeze activity briefly, take a final database and files sync, then update DNS.
- Re-create server-side settings
Cron jobs, SMTP, SSL certificate, SPF/DKIM records and backups do not move with the files. Set them up again and test.
- Keep the old server for a while
Do not cancel it until the new site has run cleanly for a couple of weeks.
If the domain must change
Add permanent (301) redirects from every old URL to the new one, update base_url, and re-deposit all DOIs to Crossref so they resolve to the new addresses. Update the journal URL with DOAJ and any other databases that list it. Expect Google Scholar to take time to pick up the change.
If you are moving because the current site was compromised, clean it first; otherwise you migrate the malware too. See our guide to cleaning a hacked OJS site. For a hands-off move to servers tuned for OJS, our OJS hosting service handles migration, backups, SSL and email setup, and our team has 10+ years of experience with 80+ academic journals.
Frequently Asked Questions
What is the best hosting for OJS?
There is no single best host. A single small journal can run well on good cPanel hosting that passes the checklist in this guide. Several journals, or a journal with heavy traffic, are better on a VPS or managed OJS hosting. If nobody on your team manages servers, choose a managed option with OJS-aware support.
Can I host OJS on shared hosting?
Yes, if the host offers a supported PHP version with the right extensions, cron jobs, a folder outside public_html for the files directory, reliable backups and working SMTP. Check our OJS system requirements before you sign up.
Does PKP offer OJS hosting?
Yes. PKP Publishing Services, part of the Public Knowledge Project at Simon Fraser University, hosts OJS, OMP and OPS sites and offers related services. Details are on PKP's hosting services page.
Will changing hosts break my DOIs or Google Scholar listings?
Not if the domain and URL structure stay the same. DOIs and Google Scholar point to your article URLs, not to a server. Problems start when the domain, journal path or clean-URL setting changes without redirects and updated DOI deposits.
Can a hosting provider get my journal indexed?
No. Hosting affects speed, uptime and security, which matter for Google Scholar crawling, but indexing decisions depend on your journal's editorial quality and policies. Treat any host that promises indexing as a red flag. See our journal indexing guide.
Do I need a dedicated server for OJS?
Rarely. Most journals, including many multi-journal university installations, run comfortably on a well-configured VPS. Dedicated hardware makes sense only for very large sites or strict institutional policies.
Does OJS Academy provide OJS hosting?
Yes. Our OJS hosting service runs journals on servers configured for OJS, with backups, SSL, email setup and support from people who work with OJS every day. Contact us for a free consultation.
