Sustainability and services
Starting framework adopted on 8 November 2026. The model will evolve with actual costs, available capacity and practical experience. Changes will be explained publicly and agreed service terms will be respected.
See Support OMI for voluntary EUR contribution suggestions, illustrative EUR institutional deployment and annual care fees, and the linked contribution channel. These figures are planning references, not a checkout or a binding offer. Reference amounts do not create payment-provider tiers or an immediately purchasable service.
What stays free
Open Manuscript Studio remains free and open source. Writing, opening and saving manuscripts, core import and export, open formats and self-hosting remain free. Contributions are optional; they do not change manuscript handling or access to security and data-loss fixes.
Costly shared storage, machine translation, OCR and similar services may have transparent capacity limits. Such limits must preserve downloading and exporting one's own manuscripts. A paid service or contribution does not create exclusive ownership of the open specifications.
Four complementary sources
| Source | Purpose | Commitment |
|---|---|---|
| Individual contributions | Voluntary community support | Common maintenance, testing and development |
| Annual institutional contributions | A predictable maintenance base | Transparent use of contributions and public progress reporting |
| Separately commissioned services | Payment for agreed work and infrastructure | A written scope for deployment, OJS/OMP connection, training or care |
| Grants and funded development | Larger improvements | A defined work plan, budget and deliverables |
Start with three suggested monthly individual levels, optional one-time support and one annual institutional supporter framework. The higher institutional levels shown on the support page are for later expansion. An annual contribution is not a per-user licence or a bundle of support hours.
Free software, optional professional deployment
Using Studio and independently installing the OMI server software remains free. Institutions may deploy, configure, update and operate their own servers without buying a licence, subscribing to OMI or purchasing an installation service. The open-source licence and published distribution terms apply; there is no per-user or per-server licensing charge. Public installation documentation and software updates are available without payment.
Free access to the shared central OMI service may be subject to published fair-use, storage or computational capacity limits; it does not imply unlimited hosted storage, uptime or support. Manuscript portability, download and export must be preserved.
An institution may instead commission professional deployment, which pays for work—not permission to run the server. Indicative one-time fees in EUR (excluding applicable VAT) are:
| Deployment service | Indicative one-time fee | Typical scope |
|---|---|---|
| Basic institutional deployment | €690 | Prepared environment, installation, baseline configuration, handover |
| Standard deployment with OJS/OMP integration | €1,490 | Basic deployment plus assessment and connection of an existing OJS or OMP instance |
| Complex institutional deployment | From €2,990 | Multi-system architecture, authentication/integration requirements and tailored handover after scoping |
These examples are not automatically purchasable packages. Scope and price must be confirmed in a written quotation. Hosting, infrastructure, external APIs, paid third-party licences, migration, travel and bespoke development are excluded unless explicitly included.
Optional annual operational support
Professional care is not required to run a self-hosted OMI server. Where requested, the institution may purchase bounded support independently from the software:
| Care level | Indicative annual fee |
|---|---|
| Basic technical support | €390 |
| Institutional operational support | €990 |
| Priority support with agreed response arrangements | From €1,990 |
The fees indicate service levels rather than unlimited labour. An agreement must state covered systems and hours, response targets, service windows, change approvals, responsibilities for security and backups, incident escalation and exclusions. An annual institutional contribution is a voluntary donation to the common project and does not include any of these operational services.
OMI server updates and security fixes remain available to all installations. Any automated fleet update mechanism must respect institutional opt-in, administrative control, compatibility checks, maintenance windows, backups and rollback; a central service must not silently force a production deployment change.
The starting service pilot is limited to two institutions, with expansion based on measured workload and tested delivery. Contracted care requires verified deployment and restoration of a compatible application and data state, and documented data handling, exit and data return. Institution-owned and managed hosting have different responsibilities. There is no implied unlimited storage, 24/7 coverage or availability SLA.
Prices are non-binding planning examples excluding VAT. A written offer identifies the legal service provider, applicable taxes or exemption, total price, scope, exclusions and performance conditions. The 9 November 2026 clarification supersedes earlier HUF-based individual task, hourly and monthly care examples; those examples are not simultaneous offers.
Payments
The support page links to the project's existing GitHub Sponsors destination. Available tiers, recipient, currency, recurrence and cancellation must be checked at that destination before confirming a payment. GitHub tiers are in USD; the suggested EUR figures are reference amounts, not a guaranteed currency conversion. This website does not collect card details or start payments.
Before activating further payment methods, identify the recipient and provider, clarify accounting and applicable tax treatment, and test payment, cancellation and refund handling. Institutional contributions and commissioned services must have distinct terms and appropriate records. The word “support” alone does not establish a tax exemption.
Transparency and independence
Publish a short quarterly summary of income, operating expenses and completed work. Supporter names and logos appear only with consent. Contributions do not buy editorial, peer-review or scholarly influence, exclusive roadmap control or earlier access to security fixes.
Measure actual recurring income, direct costs, maintenance time and client work separately. Include the value of maintenance work when assessing sustainability, and avoid counting client infrastructure in both the common budget and a service quote. Grant income follows its own permitted purpose and funding period.
First 90 days
| Phase | Focus |
|---|---|
| Days 1–15 | Confirm actual costs, recipient, accounting, payment eligibility and available service time |
| Days 16–30 | Complete public terms, contribution options and payment/cancellation checks |
| Days 31–60 | Run up to two scoped institutional pilots and record actual effort |
| Days 61–90 | Prepare the first public summary and review amounts, capacity and service scope |
The first review follows this rollout rather than an assumed calendar launch. Later reviews use practical evidence. Changes to public reference amounts must not silently alter existing service agreements.
For research cooperation, infrastructure contributions and consortia, see Funding & Partnerships and the Grant Readiness Pack.