Managed OJS for scientific journals

Server provisioning, OJS 3.5 install and configuration with MariaDB, HTTPS on your domain, scheduler, deployment health checks, on-host and encrypted off-host backups, disaster recovery, linking to the EditorialXML workspace, and ongoing operational support. When the contract includes it, also JATS production and validation for publication on that OJS.

We define the journal domain in the proposal. We coordinate DNS (typically an A record to the managed host IP) and, once it resolves, complete provisioning with valid TLS for that hostname.

We produce backups with a database dump, private and public files, OJS configuration, and a checksummed manifest. We also store encrypted copies off the production server in S3-compatible storage, with restore and disaster-recovery procedures.

The journal runs on the same EditorialXML workspace. We produce JATS from your manuscripts, validate for the agreed destination (including SciELO SPS when applicable), and publish validated packages on the managed OJS — aligning metadata and the end-to-end editorial flow.

It depends on the domain, DNS coordination, and scope (new site vs. migration). After the proposal is agreed, the typical cycle covers infrastructure provisioning, install, TLS, and health checks until go-live; we state concrete timelines in the quote.

Yes. Your editorial team uses OJS for submissions, review, editing, and publication. EditorialXML operates the infrastructure, backups, and XML production integration so you focus on academic and editorial work on a stable install.