Shared Hosting vs VPS vs Cloud for OJS Journals: A Practical Guide

Where your journal is hosted affects page speed, whether emails arrive, how the site copes on deadline day and how safe your authors’ files are. Hosting is often chosen on price alone. This guide explains what OJS actually needs and which type of hosting fits which journal.

Altechmind doesn’t sell hosting. We set up and look after OJS on the hosting you choose, so this guide isn’t steering you towards a product of ours.

What OJS 3.5 needs from a server

Requirement	What it means in practice
PHP 8.2 or later	Some hosts still default to older PHP. Check you can select 8.2 or newer.
MySQL 5.7.22+, MariaDB or PostgreSQL 9.5+	Standard on almost all hosting.
A files folder outside the public web folder	OJS stores submissions in a folder that must not be reachable from the web. Some cheap plans only allow the public folder.
Scheduled tasks (cron)	Needed for reminders and, in OJS 3.4 and 3.5, for processing the email and job queue reliably.
Reliable email (SMTP)	OJS sends a lot of email. See OJS email not sending.
HTTPS	Free certificates (such as Let’s Encrypt) are standard now. ORCID and other services expect HTTPS.
Enough storage and memory	Submission files grow every year, and large uploads need generous PHP upload and memory limits.

Requirements change with each OJS version; check them before upgrading. More in the latest version of OJS.

The three options

	Shared hosting	VPS	Cloud
What it is	Your site shares one server with many others	A virtual server with its own guaranteed resources	Resources from a large provider, sized up or down as needed
Relative cost	Lowest	Moderate	Varies with usage
Control	Limited: the host decides most settings	Full (root access)	Full, often more complex
Who maintains the server	The host	You, or the host on a managed plan	You, or a managed service
Good for	Small new journals	Most established journals	High traffic, institutional rules or special needs

When shared hosting is enough

• A new journal publishing a few issues a year with modest traffic.
• A tight budget, where getting online matters more than performance.
• No one on the team to look after a server.

Check before you buy: PHP 8.2 or later, a folder outside the public web folder for OJS files, cron access, and SMTP for outgoing email.

Where shared hosting struggles

• Busy neighbours. When other sites on the server are busy, yours slows down.
• Email reputation. Mail sent from a shared server inherits its reputation, good or bad. Sending through an external SMTP service avoids most of this.
• Limits you can’t change. Upload size, memory, execution time and the PHP version are set by the host.
• Growth. When the journal outgrows the plan, moving is a project of its own.

When a VPS makes sense

• Pages are slow or time out at busy times.
• You need specific PHP settings, larger uploads, or a proper job worker for the OJS queue.
• You run several journals or other PKP software such as OMP.
• Reliability matters more than the lowest price.

A VPS needs looking after: security updates, backups, monitoring. If nobody on your team can do that, choose a managed VPS or arrange support. An unmaintained VPS is less safe than good shared hosting.

When cloud makes sense

• Your traffic has large peaks, such as a widely shared article or a call-for-papers deadline.
• Your university requires a particular cloud provider.
• You already run other systems with the same provider.

Cloud can be as simple as a single cloud server, which is much like a VPS, or as complex as a multi-server setup. Usage-based billing can surprise you, so set budget alerts.

The part people forget: email

Whichever you choose, send OJS email through a proper SMTP service on your journal’s domain with SPF, DKIM and DMARC set up. It does more for deliverability than any hosting upgrade. Background: why journal emails go to spam.

How to decide

Your situation	A sensible starting point
New journal, small budget	Good-quality shared hosting that meets the checklist above, with external SMTP
Established journal, steady traffic	A managed VPS
Several journals or high traffic	A VPS or cloud server sized for the load
University with its own infrastructure	Your institution’s hosting, if it meets OJS’s requirements

Whatever you choose, make sure backups run automatically, are stored away from the server, and have been test-restored at least once.

Need OJS set up on new hosting, or moved to it? Our journal website design and development service covers installation and configuration, and our OJS support plans look after it afterwards.

Questions

Can OJS run on shared hosting?

Yes, if the plan offers PHP 8.2 or later (for OJS 3.5), a files folder outside the public web folder, cron and SMTP. It suits small journals; busy journals usually need a VPS.

Does Altechmind provide hosting?

No. We set up, upgrade and support OJS on hosting you choose and own.

Is a VPS always better than shared hosting?

Only if someone maintains it. An unpatched VPS is riskier than well-run shared hosting.

Will better hosting fix our email problems?

Not on its own. Sending through an SMTP service with SPF, DKIM and DMARC matters more than the hosting type.