An engineering review of VBWD Office from its public repos: one storage spine and three products (Space, Docs, Spreadsheets), encrypted at rest, capability-based sharing, and a spreadsheet engine that parses formulas to an AST instead of running eval.
A self-hosted file vault, editor and spreadsheet you can actually audit — and the design choices are more interesting than the features.
"You can't self-host a real office suite — that's why everyone rents Google Docs." A new engineering review of VBWD Office, built from its three public repositories, is a working argument against that: a self-hosted file vault, rich-text editor and spreadsheet that run on infrastructure you control. The design decisions are more interesting than the feature list.
One spine, three products
The suite refuses to build three apps. As the review on VBWD explains:
A document is a single record — an office_node — and its doc_type decides which product opens it
— file is the Space vault, text is the Docs editor, sheet is the spreadsheet. They share one tree, one trash, one version history, one quota and one access-control path, so every "can this person touch this?" question is answered in one place instead of three.
Honest security, and no eval
What stands out is the candour. Documents are encrypted at rest but the suite is explicitly not end-to-end encrypted, because AI, preview and search need to read them — and the review says so plainly:
anyone claiming E2EE while holding the keys would be misleading you
The detail engineers will appreciate is the spreadsheet engine. As the review notes:
A spreadsheet is, functionally, user-supplied code running on your server
— so the naive approach, a language eval, would be remote code execution with extra steps. VBWD Office instead lexes formulas, parses them to an AST and runs them in an interpreter, with a purity test enforcing the boundary in CI. Sharing is a capability (an opaque hashed token with a permission and expiry), not a session, and invalid tokens return a 404 indistinguishable from one that never existed.
The full review is published on VBWD; the code is public across vbwd-plugin-office and its admin and user front-end repos.
Written for Red Robot with AI assistance and human editing. Adapted from an original analysis published on VBWD.
https://redrobot.online/2026/09/09/a-self-hosted-office-suite-with-no-eval-how-vbwd-office-is-built/