Configuration only — no code on your side.

Group-Office ships a community wopi module that lets you register an office service with an arbitrary address. Register SumOffice there and the documents in Group-Office open in our engine. Measured on Group-Office 26.0: a macro workbook and a document with five pictures went through the full round and came back intact.

What was measured

The round	`.xlsm` and `.docx` opened from Group-Office, edited, saved back as a new version.
What came back	VBA byte for byte, all five pictures byte for byte, the edit in place.
What we fixed to get there	Group-Office sends the open request as `multipart/form-data` rather than a plain form post. An editor that does not expect that answers with an error and the frame stays blank. Ours handles it now — worth knowing if you are evaluating any WOPI editor against Group-Office, not only ours.
What this does not say	The round used a fixture workbook from our corpus that asks Microsoft Excel to repair it on its own, before any round — so no silent-Excel claim here. See Nextcloud and Seafile for the measurement on a real workbook.

Setting it up

# the editors, behind your TLS address
git clone https://github.com/SumOfficeApp/sumoffice-docker && cd sumoffice-docker/nextcloud
cp env.example .env    # PUBLIC_URL=https://office.example.com
docker compose up -d

# Group-Office → the community "wopi" module → add a service
# discovery URL:  https://office.example.com/hosting/discovery

Evaluation is free with no time limit; production is the per-application license — per embedding application, with no meter on your users. The other systems we measured →

Then

Check my Excel file — what your workbooks rely on, in seconds.
Tell us your Group-Office version — 26.0 is measured.