The ladder

See a document first. Integrate second. Edit third.

Viewing a document is the fast half of office integration — so that's where we start you. Every rung below carries an honest status: what's live is live, what's coming says so. What the engine can't draw yet, it preserves byte-for-byte and tells you — a file always comes back whole.

RUNG 0

Open a document right now

Live

Real SumDoc editor, in your browser, no install and no sign-up — a demo cabin opens one of our real-world sample files. Edits live only inside the cabin and are not saved anywhere.

Honest note, measured today: in the two long reports and the workshop brochure, some captions and headings are still drawn on top of body text — we built a measure for it and it names 19 such places; 17 of them a reader would notice. Text running past the sheet edge — 83 lines this morning — is fixed, and so is the brochure page that drew every glyph twice. No text is lost in any of these files: every word is on the page, and the files are verbatim originals — download them and compare.

RUNG 1

One command, for agents and scripts

Live · macOS (Apple silicon)

No package manager, no install: download one binary from this site and turn any DOCX into a self-contained HTML page that opens with a double-click — offline, view-only, honest about what it didn't draw.

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

145 MB, darwin-arm64 today — more platforms and a slimmer build are coming; sha256. An npm wrapper may follow — it is not required.

Working with an AI agent? Paste this to it

Everything below is on this page already — the block just saves you the explaining.

Show me report.docx as a web page, offline, without installing Office.
Use SumOffice: download the binary, verify the checksum, render the file.

  curl -LO https://sumoffice.com/dl/sumdoc
  shasum -a 256 -c <(curl -s https://sumoffice.com/dl/sumdoc.sha256)
  chmod +x sumdoc
  ./sumdoc render report.docx -o report.html

The result is one self-contained HTML file: no server, no network, view-only.
Machine-readable notes about this engine: https://sumoffice.com/llms.txt

Agents can also read llms.txt directly — it is the machine-readable front door of this site and states plainly what is live and what is not.

RUNG 2

In your product — desktop

Live · ~30 min, measured

One binary, one localhost port, your WebView. The full walk-through with the bootstrap handshake, document events and the headless session protocol is the quickstart.

RUNG 3

In your product — mobile

Apps live in both stores · view-SDK in development

Our own SumDoc and SumSheet apps are exactly this integration, and they are published: both are open in the App Store and on Google Play: a system WebView around the same surface. A packaged view-SDK (engine + page as a drop-in artifact) is in development — this page will carry the 1-2-3 steps when it lands.

RUNG 4

Editing

Same engine, same surface

Viewing and editing are one engine and one layout — upgrading is not a re-integration. Commands run sequentially, every response echoes your id, and a refusal arrives before the change: the document, its history and the file stay untouched. See quickstart, Path B.

Why view-first? Because seeing your files open correctly is the fastest way to trust an engine — and the cheapest way to find out it's wrong for you. Everything else builds on that trust.