Skip to content
SumOfficeSumOfficeSumOffice
Menu
What SumOffice isProduct and deliveryAI and MCPContact us
Getting started
What SumOffice isAdd the editor without a programmerEmbed into a web applicationEmbed into a desktop applicationEmbed into a mobile applicationHow to read this documentationGlossaryAI tools and MCPContact usEarly access request
Product and delivery
Your own office instead of Microsoft OfficeWhat you get: in shortWhat the delivery includesCustomizing for your brandEmbedding modesFeature parity with Word and ExcelVBA, Power Query, and agentsSecurity, privacy, and operationsPreview without the editorWhat embedding gives you that Office doesn'tWhat's promised, and what isn'tPilot and acceptanceCommercial packagingRisks and honest boundariesWhat's coming next

What the delivery includes

Exactly what you get: engines, a ready-made interface, server images, mobile kits, the capability matrix, the evaluation kit, and the operations package.

You do not get “the editor’s source code” but a developer kit together with a runtime: the contract, examples, the capability matrix, and acceptance scenarios. This means the integration rests on fixed commitments, not on reading someone else’s code.

What’s included What it is What this gives you
Document editor inside an application Surface Host — a local SumDoc service in Rust with a built-in interface; it runs in your program’s window and listens only on a local address. A DOCX editor inside your own desktop program, with no dependency on Electron.
Document editor in the browser The SumDoc server image: each user gets their own core process with their own document. Published separately from the desktop installer — an image on Docker Hub and an archive in the release directory. A DOCX editor in the browser inside your web product — how it works and where to get it.
Spreadsheet processor in the browser The same kind of server image for SumSheet: a process per user with its own copy of the workbook, sign-in through your system, file export and delivery. Published separately from the engine packages. An XLSX editor in the browser when the core computes on the server — the server path.
Mobile apps and the viewer kit Ready-made apps for iPhone, iPad, Android, and the Mac App Store. A free viewer kit for Android and iOS — viewing only, for DOCX, DOCM, XLSX, and XLSM — ships under the same version number as the store build, with a checksum. Editing inside your app is the editing kit, licensed per app. A document or spreadsheet on the phone without your own server and your own screens — phone and tablet.
Spreadsheet engine packages SumSheet builds for the desktop app and for the browser, the operation contract adapter, workbook and session state. The embedding examples are assembled from these packages; they are not published to the public npm registry. Formulas, history, import and save for spreadsheets — and the choice of where the core runs.
A surface under your brand A ready-made interface: the document canvas or the spreadsheet grid, dialogs, commands, theme, and language. A working editor inside your product without building an interface.
A public interface Stable methods for opening, executing, subscribing to events, saving, and closing; types, errors, and declared capabilities. An integration that does not depend on internal names in the code.
Application adapters Examples for a window inside a desktop program, for the browser, for local exchange, and for working with storage. A short path from the first try to a pilot.
Capability matrix Format × runtime × operation × read, edit, save, and markup preservation × limitations. Part of it is open already: 13 spreadsheet formats and what you can do with each file in documents. “We support the format” becomes a verifiable commitment.
Evaluation kit Examples, sample documents, an end-to-end path on a real file, the expected result of each step, notes on logging and security. Your engineer opens their own document in 30–60 minutes, or builds a technical prototype.
Architecture specification A document for architects: protocol, session lifecycle, security, versioning, deployment, and acceptance. Issued together with the evaluation kit. The integration can be designed before the first call — where to start a pilot.
Operations package Signatures of delivery files, component inventory, the vulnerability handling process and response times, migration notes between versions, release and update rules. Which signatures exist in the current release and which do not yet is listed under risks. A runtime that a corporate operations team will accept.

For developers

Section titled “For developers”
  • Server images: docker pull hissih/sumdoc-webhost:latest for documents and docker pull hissih/sumsheet-webhost:latest for spreadsheets. The image archive is in the webhost/ folder of the release directory — https://dl.layers.md/sumoffice/sumdoc/release/latest/webhost/ and https://dl.layers.md/sumoffice/sumsheet/release/latest/webhost/ — together with INSTALL.md and SHA256SUMS.
  • Spreadsheet engine packages — @sumsheet/*; the viewer kit for the phone ships with a sha256 checksum.
  • Where to start checking: installing SumDoc and the quick start, installing SumSheet and the quick start.

Documentation assistant

Answers are assembled from the documentation and may be inaccurate — check the sources.