AIRIX OJS STUDIO / OPEN JOURNAL SYSTEMS

You run editorial.
We run the platform.

We launch, migrate, upgrade, secure and operate Open Journal Systems platforms for journals, universities, societies and publishing teams.

Staging-first change, clear responsibility and long-term technical ownership.

PUBLISHING CONTEXTS

Different publishing organisations need different operating models.

NEW JOURNALS

For teams establishing a new journal and publishing workflow.

ACTIVE JOURNALS

For journals requiring hosting, maintenance, support, design or operational improvement.

MIGRATING JOURNALS

For journals moving from an older OJS release, another host or another publishing system.

UNIVERSITIES AND PUBLISHERS

For institutions operating multiple journals or sub-journals.

ARCHIVED JOURNALS

For dormant or discontinued journals whose public scholarly record must remain available.

SOCIETIES AND RESEARCH GROUPS

For scholarly organisations requiring a reliable publishing platform without maintaining infrastructure internally.

OJS COMMERCIALS

Transparent, regional pricing.

Global Price Book

Archive Journal Hosting

For one dormant, discontinued or closed journal.

Shared Foundation

For one new or small active journal on shared managed infrastructure.

Managed Journal

For one active journal requiring isolated platform management.

Archived Multi-Journal Estate

Technical stewardship for scholarly records.

Multi-Journal Platform

Technical stewardship for scholarly records.

Standalone Managed Infrastructure

Technical stewardship for scholarly records.

Global Launch Packages

Starter

Professional OJS implementation.

Standard

Professional OJS implementation.

Premium

Professional OJS implementation.

Institutional

Professional OJS implementation.

Institutional and Multi-Journal estates require a scoped technical proposal.

Last Reviewed: 4 August 2026

View Full Commercial Directory
PUBLISHING PATHWAY

One connected route through the editorial lifecycle.

PLATFORM LIFECYCLE

The publishing platform has a lifecycle too.

Launch

Configure the platform, roles and publishing route.

Optimise

Improve workflow, metadata, email and usability.

Scale

Add journals, integrations and institutional capacity.

Maintain

Plan upgrades, backups, support and recovery.

QUICK INTERVENTION

Publishing Platform Quick Intervention

Request Scoped Proposal

intake review
affected URL and platform
impact and symptoms
recent changes
backup status
remote access review
up to four engineering hours
pre-change backup
backup validation
isolated recovery trial
diagnosis
one contained repair attempt
verification
findings record
recommended next action
Request Intervention
SECURITY & ASSURANCE

Platform Audit

Request Scoped Proposal

Penetration Testing

Scoped proposal

Forensic Response

Scoped proposal

Penetration testing requires written authorisation and backups.

VERIFIED WORK

Public Scholarly Evidence

OJS Demo

Displays Airix Media footer credit

View Live Platform

KU Journals

Displays Airix Media footer credit

View Live Platform

ASUL Journals

Displays Airix Media footer credit

View Live Platform

AJTMBR

Displays Airix Media footer credit

View Live Platform

EFTBHS PATH

Displays Airix Media footer credit

View Live Platform

Support Targets & Boundaries

Mon–Fri, 9:00 AM – 5:00 PM WAT
Nigerian holidays excluded
WhatsApp during working hours
Acknowledgement within 1 business day
Managed OJS Support: 4 working hours
Priority support: 2 working hours
Emergency reports: 24/7 accepted
No general 24/7 engineering guarantee
Ref: Service Level Standard

"These are acknowledgement targets, not resolution guarantees. We prioritise platform stability and integrity over immediate aesthetic or content changes."

Start a Journal

From concept to the first call for papers.

  • OJS installation and database setup
  • Editorial workflow configuration
  • Submission guidelines and policy setup
  • User roles and permissions mapping
  • ISSN and DOI registration assistance
  • Initial theme branding

Controlled Migrations

Move your record with representative validation and controlled cutover.

  • Protected staging and verified backups
  • Baseline counts and reconciliation
  • Migration from OJS 2.x to 3.x
  • Rollback planning and representative validation
  • URL mapping to prevent 404s
  • Integrity verification post-migration

OJS Upgrades

Keep your platform current, secure, and supported.

  • Minor and major version upgrades
  • Security patching and hardening
  • Plugin compatibility verification
  • Database schema optimisation
  • Custom theme refactoring for new versions
  • Staging-first deployment process
INFRASTRUCTURE

Managed Scholarly Hosting

Managed OJS Hosting

Infrastructure built specifically for PKP software.

High-performance NVMe storage
Daily offsite backups (30-day retention)
SSL/TLS certificate management
Optimized PHP and MariaDB/MySQL environments
WAF and DDoS protection
Automated monitoring and alerts

Archive Hosting

Defined preservation responsibilities for the scholarly record.

Low-cost hosting for dormant journals
Read-only platform hardening
DOI persistence and metadata accessibility
Defined backup and restoration duties
Long-term record stewardship
Public record accessibility

Institutional & Multi-Journal

Unified management for university presses.

Centralized OJS platform management
Sub-journal provisioning
Shared institutional branding
Global user and role administration
Resource allocation and quotas
Aggregated reporting and analytics

DOI, Metadata & Discovery

Be found where scholarly impact happens.

Crossref integration
OAI-PMH metadata harvesting setup
Google Scholar discoverability readiness
ORCID integration for authors
JATS XML and automated metadata export
Metadata reconciliation

Integrations

Connect OJS to your existing ecosystem.

iThenticate/Turnitin plagiarism checks
Payment gateways (Flutterwave, Paystack, PayPal)
Institutional SSO (Shibboleth, LDAP, CAS)
Dropbox and Google Drive workflows
Library Discovery Services
Custom API development

Plugins & Conference Suite

Extend OJS beyond standard limits.

/ Custom plugin development

/ Airix Conference Suite (formerly OCS)

/ Specialized submission forms

/ Enhanced reporting dashboards

/ Multilingual UI and content support

/ Public API extensions

Editorial & Production Services

Human expertise for the publishing pipeline.

/ Layout and galley creation (PDF, HTML, XML)

/ Proofreading and copyediting management

/ Managing Editor assistance

/ Issue composition and scheduling

/ Reviewer database management

/ Author communication templates

Training

Empower your team to own the platform.

/ Editor and Journal Manager training

/ Reviewer workflow workshops

/ Galley production walkthroughs

/ OJS administration for IT staff

/ Custom documentation and manuals

/ Remote or onsite sessions

Free OJS Assessment

A high-level review of your current OJS state.

No credentials required
Collects visible platform information
Recommends a service route
Identifies if a paid audit is needed
Plugin and theme health check
Public interface demonstration
Request Assessment

Public OJS Demo

Experience the Airix OJS foundation.

Public interface demonstration
Test submission and review flows
Preview Airix custom theme features
Explore standard platform capabilities
Zero-risk exploration
No production experimentation
Enter Sandbox

OJS Playbook

The Airix standard for scholarly operations.

Proven workflows and configurations
Standard Operating Procedures (SOPs)
Crisis and recovery protocols
Scaling and growth strategies
Compliance and ethics checklists
Best practices for scholarly record
Request Playbook
TECHNICAL RESCUE

Inherited OJS does not have to stay fragile.

If a journal has missed upgrades, inherited unsupported code or become difficult to operate, we establish the current state, stabilise the platform and define a safe route forward.

A common constraint

An inherited theme, plugin or local modification blocks a safe upgrade path.

The response

We audit the application, database, private files and extensions, then rehearse the upgrade away from production and document the accepted route.

Give the scholarly record a dependable technical home.

From a new journal to an institutional migration, we define the platform, operating responsibility and support route around the publishing work.

Discuss an OJS Project