Many open access journals run on open source software. This software is freely available online and needs to be installed on a suitable server to be run. Examples of leading solutions to manage open access journals include the Open Journal Systems, Kotahi, Janeway and PubPub Platform, all of which are open source software.

A software solution might offer a back-end and a front-end. The back-end manages all the journal databases and information, whereas the front-end is the interface where the reader and the author interact with the journal. The Open Journal Systems and PubPub Platform cover both back-end and front-end, whereas Kotahi and Janeway can be back-end only or both.

Choosing the right software for an online journal is critical, as migrating from one to the other can be complicated once a journal has built up a portfolio, and can also require retraining (see section on Training and staff development). Some journals might choose to build their own custom software; this is only recommended if the financial and technical resources are available.

Journals also need to make appropriate decisions in terms of hosting, technical integrations and codebase constraints. These affect the features of the website, its ability to communicate or integrate with other scholarly infrastructures, as well as the capacity to adjust to personalised needs.

Hosting

Although software for creating an open access journal may be freely available, this needs to be run on a server. Journals may choose to self-host the software with Amazon Web Services, Microsoft Azure, Google Cloud Platform, or less known and cheaper providers like DigitalOcean or netcup. Self-hosting means that journals are responsible for software maintenance (including the hiring of the appropriate personnel).

Otherwise, there is an option to buy hosted software as a service. In this case, journals do not need to get involved in server maintenance. If financial resources are available, but technical resources or time might be lacking, hosted software as a service is an effective solution. The Open Journal Systems, Kotahi and Janeway offer hosting services of this kind.

Integrations

Journals will need to integrate with other technical infrastructures, mainly to exchange metadata. This helps embed journals in public databases and maximise its visibility. Potential integrations that most journals need to consider include:

• Crossref or DataCite, to register DOIs
• ORCID, to allow authors to log in more easily
• Research Organization Registry, to include organisational identifiers

Codebase constraints

Sometimes journals have emerging needs that can’t be met by the current software codebase or by any plugin. The codebase is the source code required to run the software. In this situation, the codebase constraints the workarounds for meeting the journal’s needs, since it would imply additional costs, time and expertise. Without a proper handling of these emerging needs, this additional work may show that the chosen software wasn’t the most appropriate solution.

The technical infrastructures, the available integrations and the capacity to meet specific needs are limited by the software choice. It is crucial to identify the needs before selecting the software: some options allow for plugins (e.g., the Open Journal Systems, Kotahi and Janeway) and may be more adaptable to current needs and future landscape changes.