Modified ONLYOFFICE Document Server source

Published to satisfy AGPLv3 §13 for the document editor used by Atlas Office.

Atlas Office serves documents through ONLYOFFICE Document Server, which is licensed under the GNU Affero General Public License, version 3. Our deployment runs a modified Document Server. Section 13 of the AGPL requires that anyone interacting with a modified version over a network be given access to its corresponding source, so the complete modification is published here.

Get the source

Clone the repository, which carries the full history:

git clone https://packages.atlascore.app/onlyoffice/atlas-mods-onlyoffice.git

Or download a snapshot:

Checksums: SHA256SUMS.

Reading the history

The repository is arranged so that the modification is legible as a diff rather than as a finished state. Every file under overlay/ is committed twice: first as an unmodified copy taken from the deployed image, then with our change applied. So

git log -p overlay/apps/common/main/lib/view/About.js

shows exactly what was altered in that file and nothing else. The same holds for each of the ten files.

Rebuilding it

ONLYOFFICE's own Docker build does not compile core, sdkjs, server or web-apps from source; it installs a prebuilt package. We therefore do not recompile Document Server. The Dockerfile in this repository layers the ten modified files onto the official image, pinned by digest:

onlyoffice/documentserver@sha256:3ab6ebc7c605e5a32b7ae3ff19daed4925090245acc8100ce2230bd766c88212
(Document Server package version 9.4.0-129)

docker build --build-arg BASE_DIGEST=sha256:3ab6ebc7c605e5a32b7ae3ff19daed4925090245acc8100ce2230bd766c88212 -t atlas-documentserver .

The build step also regenerates each patched file's precompressed .gz sibling, because the image's nginx serves those in preference to the file itself.

Is this copy current?

This is a mirror, published on 2026-10-20 from commit 0dc525c of master, which is the branch our deployed image is built from. Mirrors can lag the thing they mirror, so rather than asking you to take the date on trust, here is how to check it:

git ls-remote https://packages.atlascore.app/onlyoffice/atlas-mods-onlyoffice.git refs/heads/master

If that does not match the Document Server you are using — or if anything else here looks older than the editor you are interacting with — that is a defect on our side, not an ambiguity in your rights. Tell us (below) and we will republish.

Source for the unmodified remainder

The repository above holds only the files we changed. They are an overlay on a prebuilt upstream image, so by themselves they are not enough to generate, install and run Document Server, and on their own they would not be the Corresponding Source that section 1 defines. The rest is upstream's own code, unchanged. Rather than send you to a third party for it, we serve it ourselves, at the exact tag the deployed build was made from:

Component	Tag	What it is	Size
core	v9.4.0.129	the document conversion and editing engine (C++)	210MB
sdkjs	v9.4.0.129	the editor SDK: the JavaScript that runs inside each editor	51MB
server	v9.4.0.129	the Node.js services: conversion, document command and spell-check	454KB
web-apps	v9.4.0.129	the front-end the ten modified files belong to	505MB
build_tools	v9.4.0.129	the build system that produces the Document Server packages	6.5MB
dictionaries	v9.4.0.129	spelling dictionaries shipped with the editors	56MB
document-templates	v9.4.0.129	the new-document templates offered in the editors	3.4MB
Docker-DocumentServer	v9.4.0.129	the Docker image definition our build starts from	54KB
document-server-integration	v9.4.0.129	upstream's integration examples	5.8MB
DocumentServer	v9.4.0	the distribution repository for the release as a whole	963KB

Checksums for all of them: SHA256SUMS.

Together, these archives and the repository above are the Corresponding Source for Document Server as we deploy it. Upstream publishes the same code at github.com/ONLYOFFICE; our copies are mirrors of those tags and nothing more, served here so that your rights under the licence do not depend on someone else continuing to host them.

How these archives correspond to the running program

The editor files Document Server actually serves are build output, not source: the deployed index.html is roughly five times the size of the one in web-apps, and the deployed SVGs are minified. So you cannot match them to these archives file by file, and we will not claim you can. What ties them together is the build's own version stamp. Upstream source carries a placeholder:

this.txtVersionNum = '{{PRODUCT_VERSION}}';

while the copy taken out of the deployed image carries the version the build substituted into it:

this.txtVersionNum = '9.4.0.129';

That is tag v9.4.0.129, which is what the archives above are cut from, and package 9.4.0-129, which is what the pinned base image contains. The first commit in the repository above is that pristine copy, before any of our edits, so you can read the stamp yourself rather than taking this paragraph on trust.

What is not here

Atlas Office itself — the application that calls Document Server — is separate, proprietary, and not a derivative work of it. It communicates over Document Server's published API with a JWT-signed configuration and does not modify its runtime behaviour beyond the ten files published here. The AGPL's source obligation attaches to the modified Document Server, which is what this page serves.

Requests

If anything required by the AGPL is missing or unreachable here, write to support@hyperionworks.com and we will correct it.