Platforms and deployment

Only the way of deployment changes. The document itself and the contract with it stay in the Rust core — the same one on every platform.

Profile	How it works	What’s proven today
Inside the desktop app	Your application starts the editor service, opens its address in the system web view, and receives events.	In the macOS web view (WKWebView), the full cycle has been completed: document ready → unsaved changes appeared → saved → reopened. An adapter is provided for the Windows web view (WebView2).
Ready-made app	The SumDoc desktop app (an Electron shell) is delivered as a whole.	The most complete feature set for the user. This application’s internal channels don’t become a public interface.
Headless server	Your service manages the core session and is responsible for storage itself; no interface is needed.	The processor works. Serving many clients at once, access checks, quotas, and fault tolerance are a separate job.
Browser	The browser gets the same editor as in the desktop app, inside your page on your domain. The core on the server computes the document: a separate process is started for every user — Editor in the browser.	Only the page code and rendering go to the browser. SumDoc has no browser build of the core, and this path doesn’t need one.
Android	The core is attached to your application as a library (through JNI) and runs under Android WebView.	The ready-made SumDoc app for Android is published in Google Play. For embedding into your own application, a free viewing kit (view SDK) is built from the same build, with the same version number: the core library, the page, and the bridge; viewing only. Editing inside your application is licensed separately, per application.
iOS	The core is attached to your application as a library (from Swift) and runs under WKWebView.	The ready-made SumDoc app for iPhone and iPad is published in the App Store, and for macOS in the Mac App Store; the minimum iOS version is 16. The viewing kit for embedding (xcframework, the page, and the bridge) ships with every store build under the same version number.

Server variant

[Client: browser or phone] → [Your service: sign-in, storage, audit]
                              | commands and events
                              v
                    [SumDoc session adapter]
                              |
                              v
                       [Rust core]

Important

The SumDoc core as a processor never calls any cloud on our side. Only the ready-made desktop app has outbound traffic — that’s the support channel described in security. If your service faces the internet and serves several clients at once, security, quotas, process isolation, observability, and availability commitments are agreed separately.

Where to read more

• The editor inside a web application, with nothing for the user to install — Editor in the browser.
• For developers: embedding the surface in a WebView or iframe — Embedding Surface, starting it — Web Surface.
• What’s available inside the desktop app window and why it isn’t a public SDK — Internal objects of the application window.
• Managing a session from a headless service — The same contract over WebSocket.
• The overall picture of deployment modes for both products — Embedding modes.