Loading…
Platform
Each journal runs with its own site, policies, and workflow. You do not need to run a server.
ADYS is built so academic journals can run under their own identity.
Journals set their site, policies, staff, and review model. The article record moves from similarity check through to publication on one record.
Servers, patches, and plugin conflicts are not the journal team’s problem.
Each journal runs with its own data and identity; access across journals is blocked.
Submission, review, decision, and production. Deadlines are a journal setting.
Double-blind, single-blind, or open. In blind review, author and reviewer identity is hidden by role.
Submission and review move through wizards; each role sees its own screens.
Return, resume, one-step revert, and a reviewer certificate of thanks.
A short look versus self-hosted systems, national portals, and global services.
Global SaaS
Offers peer review, typesetting, and publishing as modular paid services with strong interfaces.
ADYS difference: Turkish product; each journal on its own site.
Open source
Broad academic coverage; each journal still owns servers, upgrades, and plugins.
ADYS difference: servers and upgrades are not on the journal team.
Modern open source
Newer stacks with optional cloud hosting.
ADYS difference: Turkish product language and a multi-tenant setup.
Local hub
Central infrastructure. Weak spots: rigid templates and limited customization.
ADYS difference: each journal has its own site and identity.
Each journal runs on its own site and record; you do not need to run a server.
Apply for a journal or explore journals already on ADYS.