What actually shipped
ArtCraft, a studio run by Brandon Thomas, published three open-source apps modeled on Microsoft's core Office programs: WordCraft, GridCraft and DeckCraft. Startup Fortune reports they shipped on October 7 as clean-room reimplementations written from scratch in Rust that read and write the DOCX, XLSX and PPTX formats. Spiceworks says Thomas built them with Anthropic's Claude Opus 5.5.
"Clean-room" is the developers' description of their method. It isn't a legal finding. The WordCraft repository also states that it is not affiliated with, sponsored by or endorsed by Microsoft Corporation or Adobe Inc.
The licensing is permissive. GIGAZINE notes the code is dual-licensed under MIT and Apache 2.0. The project says WordCraft runs natively on macOS, Windows, Linux and BSD, and in the browser through WebAssembly.
Releases are moving quickly:
- GIGAZINE says version 0.1.0 appeared on October 8, 2026 (Japan time) and had reached 0.6.1 by the 14th.
- Pasquale Pillitteri's coverage says WordCraft was at 0.10.0, GridCraft at 0.11.1 and DeckCraft at 0.10.0 by October 18.
- A software directory now lists WordCraft v0.11.0.
Fast version numbers show activity. They don't show that the files behave like Microsoft's.
The project's own scorecard
The most useful document here is WordCraft's roadmap, which is unusually candid. Its snapshot is dated 2026-10-07, and everything below comes from the project itself. None of it has been independently audited.
- Command coverage: 354 of 405 Word ribbon and menu features have a command, which is 87%.
- Estimated real parity: about 62%. The roadmap says catalog coverage overstates parity because many commands are first versions. The estimate weights depth and how often people use each feature.
- Code and tests: about 44,000 lines of Rust across 12 crates and three apps, with roughly 225 test functions.
- Distance to alpha: about 85% of the way there, by the project's own estimate.
A command that exists is not the same as a command that behaves like Word. If a spreadsheet user says "I need pivot tables," the real question is whether a pivot table built by someone else opens and recalculates correctly.
The compatibility gap that matters most to IT
For a business, the format question comes before the feature list. The roadmap defines alpha as the point where someone can open the .docx files they receive and send back files Word opens cleanly. It marks DOCX fidelity testing against a corpus of real-world files as "not started" and calls it the main alpha blocker.
Other limitations the roadmap lists:
- Charts, SmartArt and OLE objects are dropped from DOCX. The same table puts the Draw tab, SmartArt, charts, 3D models and the equation editor at about 5% parity.
- Footnotes don't continue onto the next page, and columns don't balance.
- Native printing is missing, so printing goes through PDF.
- Signed builds for all platforms were described as a pipeline written but waiting on release secrets and the owner's remote.
The roadmap does say that Word opens files WordCraft produces. That is encouraging, but it was untested against a real-world corpus when the snapshot was taken.
GridCraft's README takes the same cautious tone. It says nothing about this; the quotes below come from its own file. It calls GridCraft alpha, says the core workflow works end to end, and says depth, fidelity and file compatibility are "still rough". It reports coverage of 89% of standard ribbon commands and 513 worksheet functions, then states that this is an inventory and not a count of working implementations. It estimates the app is about 50% ready for real work. Its next priorities include XLSX fidelity on real-world files, very large workbooks, deeper charts and legacy .xls import.
Some of this is already in place. GridCraft says it round-trips styles, formulas including dynamic arrays, tables, conditional formats, charts and pivot tables in XLSX. Whether that holds for your workbooks with their macros, external links and years of accumulated oddities is exactly what hasn't been tested.
Windows-specific notes
GridCraft publishes Windows x86 MSI installers and portable ZIPs, and says installers and executables are code-signed. Its README also documents a Windows graphics quirk. If DirectX 12 finds no graphics card with a suitable driver, it would otherwise fall back to the Windows software renderer. In that case the app uses OpenGL instead. The WGPU_BACKEND environment variable can override the choice for troubleshooting. Logs go to %APPDATA%\GridCraft\logs.
That is good hygiene for an alpha. It also hints at the kind of driver-level edge cases that a mature suite has spent decades shaking out.
Why "AI-built" raises the maintenance question
Spiceworks and other coverage argue that building is cheap and keeping is costly. Independent research on AI-assisted code supports the caution, though neither source measures these specific apps.
- Linux Foundation Research (with Red Hat, Futurewei, OpenSSF and LF AI & Data) is not the source here; its own summary says placeholder
maintainers report roughly one in four incoming pull requests as low-quality "AI slop", that burnout is the top concern for large projects, and that only one in three projects has a formal AI-contribution policy. Developers also report 19%–52% time savings. This describes surveyed open-source workflows in general. - Veracode's 2026 GenAI Code Security Report found that roughly 44% of AI code-generation tasks introduced a risky vulnerability in its tests. The average security pass rate was 56%, barely changed from 55% in the first report. Veracode also says syntax is effectively solved, with models generating correct code nearly 100% of the time, while security isn't. That is a statement about its test tasks, not about WordCraft.
The takeaway is practical. Code that compiles and looks clean still needs review, scanning and an owner who will patch it.
A sensible evaluation plan
If someone in your organization wants to try these, treat it as a lab exercise and not a migration. This is general guidance, not something the projects or sources have tested for you.
- Isolate it. Use a test machine or VM with no access to production file shares.
- Build a representative corpus. Gather non-sensitive documents with tracked changes, comments, tables, footnotes, headers, embedded charts and objects.
- Round-trip them. Open each file in the clone, save it, then reopen in Microsoft 365 and compare layout and content.
- Test the known gaps. Check charts, SmartArt and OLE objects (which WordCraft drops), long footnotes, and printing.
- Check security and supply chain. Verify checksums and signatures, review the dependency tree, and scan the build with your usual tools.
- Decide on ownership. Who patches it, who triages bugs, and what happens if the project stalls?
Success looks like documents that round-trip with no visible loss, a clear support path, and a security review you would accept from any vendor. Today, by the projects' own account, the first of those isn't yet established.
What this means for Microsoft 365
Nothing in the documentation suggests an imminent replacement for Microsoft 365. A suite is more than a word processor. It includes identity, compliance, collaboration, co-authoring, admin controls, support contracts and a decades-long compatibility record. The clones target the editing surface, and even there they are early.
The more interesting signal is the pace. Startup Fortune says WordCraft passed 3,500 GitHub stars within days. Interest in free, scriptable, agent-controllable tools is real. WordCraft and GridCraft both expose CLI and MCP controls for AI agents, which is a different pitch from Word's. For niche uses such as automated document generation, that may matter more than a ribbon lookalike.
Some claims in the wider conversation remain unverified here, including legal opinions on clean-room reimplementation, the "SaaSpocalypse" market narrative, and the REA project's star counts. Reports of REA's popularity also vary between outlets. Treat them as commentary, not settled fact.
Bottom line
- ArtCraft's WordCraft, GridCraft and DeckCraft are real, open-source and moving fast.
- By their own roadmaps, they are alpha software: about 62% estimated real parity for Word and about 50% readiness for spreadsheets.
- Real-world DOCX and XLSX fidelity testing was still outstanding in the project's own documents.
- AI-generated code needs the same review, scanning and ownership you would demand of any vendor.
- The sensible answer to your CFO is to run a contained pilot and keep paying for the suite while you do.