Installation and verification

SumDoc is a ready-made application for macOS, Windows, and Linux. The package ships the native fastdoc-cli executable alongside the interface. For embedding, this is an external document processor: you can run it from your own desktop app, a server-side wrapper, or a local web host.

Download and verify

The current build is published on dl.layers.md. The release directory is split by system: the macos/, windows/, linux/ and webhost/ (web host image) folders, with only manifest.json — the version number and release notes — at the root. Each folder has its own SHA256SUMS, the list of checksums for its files. Verify the download before installing:

base=https://dl.layers.md/sumoffice/sumdoc/release/latest/macos
curl -fsSLO $base/SHA256SUMS
# take the filename with the version number from the same list
curl -fLO $base/$(awk '/arm64.dmg$/ {print $2; exit}' SHA256SUMS)
shasum -a 256 -c SHA256SUMS --ignore-missing

For Windows use the windows/ folder and the arm64.msi or x64.msi name pattern, for Linux the linux/ folder and amd64.deb; compute the checksum with your system tools: Get-FileHash in PowerShell, sha256sum -c on Linux.

The arm64.dmg pattern is for Apple Silicon Macs; for Intel Macs the same folder holds x64.dmg. Both architectures are published for Windows, x86-64 only for Linux.

Part of the Linux delivery is signed separately: .asc files sit next to the deb and AppImage in the linux/ folder, along with the public key that verifies the signature. The rpm package has no detached signature in the release directory — for it, checksum verification remains.

base=https://dl.layers.md/sumoffice/sumdoc/release/latest/linux
curl -fsSLO $base/SHA256SUMS
curl -fsSLO $base/fastoffices-signing-key.asc
gpg --import fastoffices-signing-key.asc
curl -fsSLO $base/$(awk '/amd64.deb.asc$/ {print $2; exit}' SHA256SUMS)
gpg --verify SumDoc-*-amd64.deb.asc SumDoc-*-amd64.deb

The key comes from the same server as the package, so by itself it proves nothing: whoever swaps one can swap the other. Check the fingerprint — it should be:

5587 733B DD0A 0CA5 36D7  4D13 C5BD DF05 B96C DB10

gpg --fingerprint dev@layers.md shows it after import. The key carries the name FastOffice A4 Signing Key <dev@layers.md> — the development team’s working address, not a delivery mailbox; that’s expected. A fingerprint obtained through a different channel — from us by email or in person — is what makes this a real check.

On macOS and Windows the signature is checked by the system itself during installation: the platform signature applies there, not this one. The macOS image is signed with a Developer ID certificate and notarized by Apple—spctl answers accepted, source=Notarized Developer ID. For SumDoc both delivery variants are notarized, the .dmg image and the app from the .zip archive: take either. (For SumSheet the signature is checked on the app inside the image, not on the image itself—its installation page says so.)

The certificate carries the legal entity’s name, not the product name: Developer ID Application: HEALTH INFORMATIC SECURITY SYSTEM SL (K58GV7E7X4). That’s expected — check it against the team identifier, K58GV7E7X4.

The SumDoc installers for Windows carry no digital signature in the current release: the system will show an unknown publisher warning. Verify such a file with the checksum from SHA256SUMS—there is one for it. The SumSheet installer for Windows is signed with the test certificate FastOffice Test Signing (DEVELOPMENT ONLY) with no trusted root—the warning will appear there too, and the reliable check is the same, by checksum.

macOS

CLI="/Applications/SumDoc.app/Contents/Resources/runtime/native/fastdoc-cli"
test -x "$CLI" && echo "processor found"

# Show the available one-off commands
"$CLI" --help | head -n 20

Windows

$CLI = "C:\Program Files\SumDoc\resources\runtime\native\fastdoc-cli.exe"
if (Test-Path $CLI) { "processor found" }

# Show the available one-off commands
& $CLI --help | Select-Object -First 20

Linux

CLI="/opt/SumDoc/resources/runtime/native/fastdoc-cli"
test -x "$CLI" && echo "processor found"

# Show the available one-off commands
"$CLI" --help | head -n 20

This is the path for deb and rpm packages. The AppImage delivery runs without installation and has no folder — extract the image and take the processor from inside it:

./SumDoc-….AppImage --appimage-extract
CLI="$PWD/squashfs-root/resources/runtime/native/fastdoc-cli"

Expected result

The terminal prints “processor found”, followed by the start of the command list. If the application is installed in a different folder, replace the path in the first line: everything after the installation folder is the same across systems — resources/runtime/native.

External integration architecture

Your shell → a JSONL or WebSocket session → fastdoc-cli → DOCX and the document model

Route	When to use it	Transport	Readiness
JSONL session	First prototype, a desktop or server-side wrapper	stdin and stdout	Ready; a good place to start
WebSocket	A web or desktop shell with asynchronous requests	ws://127.0.0.1 and a pass	Ready
Web Surface	See embedding on a live document	HTTP and the session’s WebSocket	Works, but editing is limited to the first paragraph; a page reload needs reconnection
One-off call	Batch operations and automation	process arguments and JSON	Ready
Electron preload	Only inside SumDoc’s own window	contextBridge and IPC	An internal contract, not intended for embedding

Viewing without installation

To only show a document, you do not need the whole app. The processor has a render command: one DOCX is turned into one self-contained HTML file that opens in any browser straight from disk—no server, no network, viewing only:

"$CLI" render report.docx -o report.html

The same command is available as a separate executable, sumdoc, which is downloaded from the site without installing the app. Inside is the same core as fastdoc-cli; only the command surface is narrowed. The build is published for macOS on Apple Silicon; builds for Linux and Windows are in preparation. The checksum sits next to it—the same address with .sha256:

curl -LO https://sumoffice.com/dl/sumdoc && chmod +x sumdoc
./sumdoc render report.docx -o report.html

A known limitation of the viewer: on long text without page breaks it may render fewer pages than the layout has.

What’s next

The processor is in place — from here there are three paths, depending on what you need to verify first.

• Confirm the API responds. Quick start: open a DOCX, edit a paragraph with a command, and save the result.
• See embedding live. Starting Web Surface: the surface opens in the browser on top of the same processor. Editing in it is limited to the first paragraph — this is a demonstration of the path, not an editor.
• Understand the request format. Request and response objects, and the full list in the command reference.

If something won’t start, begin with diagnostics.