The SumDoc document editor
A two-page contract: headings, lists, a table with dates and an amount. Open it, edit a paragraph — the document lives in your own sandbox.
Your own office instead of Microsoft Office
DOCX and XLSX editors inside your product and your perimeter, under your brand: what this gives a company, what already works, and how to verify it in an hour.
Business documents still live in DOCX and XLSX: contracts, estimates, deliverables, and reports. Some of them are not documents but applications: formulas, macros, Power Query, form controls. A workbook that calculates is a program, and leaving Microsoft means keeping it running. The choice is usually between bad options: shipping documents to someone else’s cloud, or moving people to an editor that cannot be embedded in your own processes.
SumOffice is an independent office platform whose engines embed in your product. Not another office suite next to yours, but a document and spreadsheet editor inside it: under your name, inside your perimeter, with your access rights and your storage. The platform has no ties to Microsoft.
What you get instead of someone else’s office
Section titled “What you get instead of someone else’s office”| Today, with someone else’s office | With SumOffice |
|---|---|
| The document opens in an external application or someone else’s cloud | The document opens inside your product; files never leave your perimeter |
| The editor carries someone else’s name and interface | The editor carries your name, your colors, and your navigation |
| Permissions and audit live separately from the document | Your system checks permissions; every action goes through the contract |
| “Supports DOCX” is a promise in words | A capability matrix: what’s read, what’s edited, what’s preserved without loss |
| Automation is macros nobody knows about | The agent works through the same contract as a person: preview, confirmation, rollback, log |
| A vendor update can break your integration | A versioned contract and a compatibility period, locked in by the agreement |
Leaving Microsoft: four steps
Section titled “Leaving Microsoft: four steps”Not a feature list, but a check your team will run. Each step is a real file on a real server, and the result says outright what is not there yet.
- Upload a workbook — on the check page or send it to the check bot in Slack or Telegram. Nothing in it is executed; the file is deleted after 24 hours.
- Read the report: every macro with its route, functions known and unknown to the engine, data sources — as “N of M”.
- Open the same workbook in the browser on our server: formulas recalculate, macros follow their routes, nothing is installed.
- Save and open in Excel: the VBA project byte for byte, values in place.
A macro or a Power Query source the engine does not carry yet is a change for your process: 600 € per item, the whole corpus by estimate, price and timeline stated before work starts — Commercial packaging.
You can try this right now
Section titled “You can try this right now”Not a presentation and not a screen recording, but a working program: both editors open right on the site, in the browser, with nothing to install. If the demo environment is down at that moment, a snapshot takes the place of the frame — and the page says so outright.
The SumSheet spreadsheet processor
An office-equipment budget with formulas. Change a quantity or a price — the core recalculates the totals, the shares, and both sums, not the page layout.
For developers, there are worked embedding projects with full code next to it: twenty-three examples for spreadsheets — from a minimal sheet to a million-row workbook, collaboration, and links between workbooks — and a project for documents.
Why this isn’t a wrapper around someone else’s editor
Section titled “Why this isn’t a wrapper around someone else’s editor”The meaning of the document belongs to its own core: it parses the file, computes layout and formulas, keeps the history, and writes the result back. The interface only shows and asks — it has no copy of the document of its own. For you this means the result is the same in the desktop app and in the browser, and that one side is responsible for it.
-
A verifiable boundary. 41 document session commands and 208 spreadsheet contract operations are exposed, each described in the reference, and the reference is checked against the code on every documentation change. Which operations the core of the latest release accepts, and which are described but not yet in the build, is stated separately. For developers — the SumDoc reference and the SumSheet reference.
-
Formats are named one by one. 13 spreadsheet formats, including XLSX, XLSB, XLSM, ODS, and CSV — with a matrix that says for each what can be opened, what can be edited, and where it can be saved. The document side handles DOCX and exchanges eight more formats: PDF, ODT, flat ODT, RTF, HTML, plain text, EPUB, and FB2 — all in both directions except PDF, which is print only. Which files it works with.
-
Refusal instead of silent corruption. An unsupported operation gets an explicit refusal with a reason before the file changes. There is no such thing as a half-written document: the file is published in one atomic action, and the editor refuses to overwrite an edit made by someone else.
-
Preserving what’s not understood. Parts of the file the editor doesn’t parse carry over into the new file as-is, instead of disappearing on save.
-
Speed you can see, not just a promise. A million-row sheet is open right on the site: scroll it, and it shows you the frame cost itself — typical, worst-case, and whether it stayed within budget. The measurement runs on your machine, not in our presentation.
-
Works without a network and without a cloud. A desktop app, a window inside your program, the browser, a server inside your perimeter, a phone — the same contract in every environment. The core never calls out; the only outbound channel is in the ready-made apps — the support assistant with error reports, and it is described under security. The SumDoc and SumSheet mobile apps are released for iPhone, iPad, and Android, and for macOS. For embedding in your own app there is a free viewer kit for Android and iOS — the same engine as in the store builds, under the same version number; editing inside your app is the editing kit, licensed per app (phone and tablet).
What we compare ourselves to
Section titled “What we compare ourselves to”With Word and Excel — there’s nothing else to compare against. They’re what’s already on your people’s desks, your contracts and estimates are written in them, and they’re exactly what the result will be measured against.
But the comparison isn’t about the number of buttons. Office is a finished product for a workstation; you buy it so a person can open a file. You buy SumOffice so that an office appears inside your product: not an application alongside it, but an engine inside it, under your own name.
Exactly what the product does with the file is broken down by task: the SumDoc capability map for documents and the map next to Excel for spreadsheets. What parity means and how it’s confirmed — Feature parity.
How this is verified at your end
Section titled “How this is verified at your end”We don’t ask you to take our word for it. Verification happens on your own files and inside your own perimeter, in steps known in advance:
15 minutes
The core responds, your DOCX is open, a paragraph is changed and saved as a separate file. Step by step, for a developer — in the quick start.
30 minutes
The same document, but now inside your application: the editor in your window, editing, saving, events. The steps are in How to start a pilot.
2 weeks
The full pilot: a check on your document corpus with written acceptance criteria, measurements, and a “take it or not” decision; the report stays with you either way. Stages and timelines — in Pilot and acceptance.
What the contract locks in — the capability profile, the platform matrix, acceptance scenarios, support terms, and security commitments — is gathered in Commercial packaging.
What’s next
Section titled “What’s next”Submit an early access requestThree fields. We will send the builds and tell you outright what already works and what is still rough.
What you get: in shortThe product formula in three parts: what you bring, what the platform does, what comes out.
Risks and honest boundariesWhat isn't covered yet, and what covers it. No rollout conversation is complete without this page.
What embedding gives you that Office doesn'tNot “we're better”, but a list of the places where embedding gives you something a ready-made office suite can't.
What's promised, and what isn'tThe claims we're ready to defend during a pilot, and the ones we deliberately avoid.
VBA, Power Query, and agentsAutomation without losing control: a supported subset, a Power Query ladder, and agent work as a single transaction.
What's coming nextWhere the platform is heading, and what will arrive before the rest.