Genspark Open Sources GenOffice: A Free, Ad-Free AI Office Suite for macOS and Windows with Docs, Sheets, Slides, PDF

Genspark has released GenOffice as open source under the Apache License 2.0. The repository describes it as an AI-native office suite for macOS and Windows: a word processor, a spreadsheet, a presentation editor and a PDF tool. The implementation is five Electron apps sharing one engine layer, built around AI editing as a first-class workflow rather than a bolted-on chat box. Signed installers ship for macOS (Apple Silicon) and Windows (x64), currently at version 0.4.110. GenOffice is free for everyone, ad-free. All the editing tools you’d expect, no strings attached. The team’s X post is blunt about scope: one engineer, one week, roughly $10,000 in tokens for the Alpha. The product page says free and ad-free, with AI features consuming Genspark credits. Feedback runs through a GenOffice group chat on GenTeam, with 1,000+ credits offered to active contributors. Is it deployable Yes, with conditions. Binaries install today on Apple Silicon Macs and Windows x64, and the source builds with Node 20+, npm 10+ and a Rust toolchain for the Sheets sidecar. But this is labeled an Alpha, and the AI path requires a Genspark account, since model calls are proxied service-side. That maps cleanly to specific buyers. Startups and SMBs are the natural first tier: no license fees, no watermarks, and full .docx/.xlsx/.pptx fidelity. Mid-market teams can fork it, since Apache-2.0 permits commercial modification — although the ee/ directory is reserved for future enterprise modules under a separate GenOffice Enterprise License, and the GenOffice and Genspark names are Mainfunc, Inc. trademarks that forks may not reuse. Regulated enterprises should wait: alpha status plus a cloud-routed AI path means procurement and DPIA work first. The technical core: byte-preserving round trips GenOffice archives the original .docx by hash and never touches it. docx-engine parses the top-level elements of word/document.xml into a block tree, where each block is anchored by a docxIndex plus the original XML slice. Editing happens in a TipTap streaming editor with dirty tracking. On save, only dirty blocks are converted to OOXML fragments — referencing existing styles only — and spliced back into the original document.xml. Untouched blocks keep their original bytes, and every other zip entry is copied verbatim. The stated payoff is that opening and saving never breaks layout in Word. The paginated view reproduces the original line metrics, and tracked changes, comments, styles, equations and ink are supported. Sheets and Slides follow the same philosophy: narrow patches over a source-of-truth file. What sits under each app Sheets builds its UI on the open-source Univer core (Apache-2.0) with a large layer of in-house extensions. XLSX import and export run through an in-house Rust sidecar using calamine and IronCalc. Charts are rendered in-house with Konva, alongside pivot tables, slicers, conditional formatting and formula tracing. Slides uses an in-house pptx parse, render and edit engine covering masters, charts, cropping, ink and text shaping via HarfBuzz metrics. PDF is built on pdf.js and pdf-lib, adding annotations, forms, outlines, stamps, signatures, page operations and print. Shell provides the home screen, tabbed hosting and auto-update. Engine packages are pure TypeScript, unit-tested, with no Electron dependency: docx-engine, pptx-engine, pptx-render, file-parse, agent-core, ai-provider, ai-search. Docs gets block-granular AI editing with snapshots and diffs; the other apps get a tool-calling agent over document state. window.addEventListener("message",function(e){if(e.data&&e.data.gooffice){var f=document.getElementById("mtp-genoffice-frame");if(f)f.style.height=e.data.height+"px";}}); Security posture SECURITY.md section is unusually detailed for an alpha. Every document window runs with contextIsolation: true, nodeIntegration: false and sandbox: true. IPC payloads are schema-checked in the m