ArtCraft, the studio run by Brandon Thomas, has published three free Microsoft Office alternatives on GitHub: WordCraft, a Word alternative; GridCraft, an Excel alternative; and DeckCraft, a PowerPoint alternative, all built as open-source Rust applications, according to Pasquale Pillitteri. The three apps are available right now as free installers for Windows, macOS, Linux, and FreeBSD, with no account or sign-in required.
That availability comes with a catch the download link doesn't explain. The developers describe the software as pre-alpha and alpha depending on the component, and they say they haven't tested document fidelity against an actual corpus of real-world files, according to Pillitteri's report. WordCraft, GridCraft, and DeckCraft can reportedly open Office files. The developers have documented some compatibility limitations, including WordCraft losing certain embedded content during a DOCX round trip, but comprehensive testing of complex real-world files remains incomplete.
That gap decides who should bother downloading this today. Testers curious about a Rust-based Office suite have a low-stakes reason to try it. Readers who depend on reliable document editing, collaboration, or guaranteed file compatibility for actual work have no evidence yet that these apps can deliver that, and should treat Word, Excel, and PowerPoint as the safer bet until the picture changes.
Who built it, and how fast it shipped
Brandon Thomas's ArtCraft studio built the three apps in Rust with help from Claude Opus 5.5, according to Pillitteri's report. Published examinations of the GitHub commit history also identify Claude Opus 5.5 as a co-author, supporting the reported use of AI assistance, though the extent of its contribution is not independently established.
The same report frames this release as a follow-up to seven earlier Adobe-style clones from the same studio, per the report. That history reflects the source's own framing rather than something independently verified elsewhere, so treat it as context rather than confirmed background.
The rollout speed is hard to miss. The GitHub repositories were created on October 6, with first commits landing that same day, and the initial v0.1.0 releases shipped within two days, on October 7 and 8, already bundled with installers for Windows, macOS, Linux, and FreeBSD, according to the report. A v0.4.0 update followed on October 10, and v0.5.0 arrived between October 10 and October 11 across all three apps, with the latest reported builds adding a Linux version for RISC-V processors, per the report.
Attention followed just as fast. As of October 12, WordCraft had collected 7,406 stars on GitHub, with GridCraft at 3,293 and DeckCraft at 2,215, according to Pillitteri. Star counts measure curiosity, not reliability. Plenty of GitHub projects accumulate thousands of stars long before anyone trusts them with daily work, and a week-old repository is not the place to assume otherwise.
None of that speed or popularity answers the question that actually matters: whether these apps can handle a real document without losing something in the process.
What "reads DOCX, XLSX, and PPTX" doesn't confirm yet
Pillitteri's report states that WordCraft, GridCraft, and DeckCraft can open Microsoft's DOCX, XLSX, and PPTX formats. That's a real reported capability, but opening a file is a narrower task than replicating a full Office workflow, and the report doesn't claim otherwise.
A short document with a few paragraphs is a very different test than a spreadsheet full of formulas and pivot tables, a slide deck with embedded video, or a Word file carrying tracked changes and comments. Those workflows need separate validation before users can rely on them. Some limitations are already documented, including the loss of certain embedded Word objects when files are loaded and saved. As the developers themselves put it, real-world fidelity remains the project's central unsolved problem, and they haven't run it against an actual corpus of documents, per the report.
What the available reporting doesn't say matters just as much as what it does. The projects' GitHub repositories document support for saving DOCX, XLSX, and PPTX files, but that doesn't establish whether complex formatting survives export or whether a file saved in WordCraft reopens correctly in Microsoft Word.
Are WordCraft, GridCraft, and DeckCraft ready as free Microsoft Office alternatives?
Based on what's confirmed so far, no, not for anything that matters. The software is roughly a week old as of this writing, sits at pre-alpha or alpha depending on the component, and has no published testing against real-world files, according to Pillitteri's report. That's a reasonable read on the available evidence, not a claim the report makes outright.
The developers' own guidance points in the same direction. Because the software remains alpha at version 0.5.0, they recommend working on copies of files rather than originals, per the report. That's a warning from the people closest to the code, and it's worth taking at face value rather than treating it as excessive caution.
It means the available project documentation and reporting don't establish reliable compatibility across the range of real-world Office files users may need to edit.
How to test them without risking a real file
Turning the developers' copy-not-original warning into an actual test routine isn't hard. Download the installer only from each project's official GitHub releases page, duplicate a simple and non-sensitive file, open the duplicate in WordCraft, GridCraft, or DeckCraft, make a small edit, save it, close the app, then reopen the saved file in the same program. If a copy of Microsoft Office is available, open the saved file there too and compare what changed.
That sequence is this article's recommendation, built on top of the developers' alpha warning rather than a tested outcome reported anywhere. Any result from running it is one data point, not proof of broader reliability either way.
One licensing detail is worth a single line for anyone planning to reuse the code: project READMEs reportedly describe dual MIT or Apache-2.0 licensing, while GitHub's own interface currently shows Apache-2.0 only, according to Pillitteri. Check each repository's LICENSE file directly before commercial reuse. Ordinary testers downloading an installer don't need to think about it.
Who should try these now, and who should wait
Linux and FreeBSD users curious about a Rust-based Office suite have a reason to explore these apps, with RISC-V Linux builds also reported. Check the individual GitHub releases pages for available packages and supported architectures. The same goes for anyone who just wants to see how an early-stage open-source project handles a throwaway file.
Given the lack of published round-trip testing, readers with deadline-sensitive or collaborative files should wait. That includes Microsoft 365 subscribers with established workflows, students submitting formatted coursework, and anyone working with comments, tracked changes, shared formulas, or collaborative editing. Those are exactly the areas the available reporting leaves unresolved.
The supplied reporting doesn't mention an independent security or code-quality review of these apps. That's a gap worth knowing about, not evidence of a specific problem, and it shouldn't tip a decision on its own either way.
A few developments would justify revisiting this advice: independently verified round-trip fidelity for DOCX, XLSX, and PPTX files, broader testing against real-world documents, clearer documentation of compatibility limitations, and a release that moves past alpha status.
What to do next
WordCraft, GridCraft, and DeckCraft are real, free, and downloadable today, with installers covering Windows, macOS, Linux, FreeBSD, and the latest reported builds adding RISC-V Linux support, no account required, according to Pillitteri's report. That makes them worth a look for anyone curious about what a free, open-source Office alternative looks like at this early stage.
What they're not, at least not yet, is proven. Available, early, and untested is the accurate read on where these apps stand, not unsafe or incapable. Test with a disposable file, run it through the open-edit-save-reopen cycle, and keep an eye on each project's GitHub releases page for a version that documents export fidelity before trusting it with coursework, client work, or anything collaborative.
Comments
Be the first, drop a comment!