Bento vs Nextcloud: One-File Office Suite Explained

Wetin Bento be

Bento na office suite wey dey ship as one HTML file. You go download one file, open am for any modern browser, and that file go be both the editor and the document. Installer no dey, and account no dey. MIT license cover am, the source dey for github.com/nyblnet/bento, and the first release wey dem ship come out on 21 July 2026. As dem dey write this on 1 August 2026, e mean say Bento never reach two weeks old. Na the most important fact for this post, and na why the last section dey talk about evaluation instead of migration.

Wetin “fits inside one file” really mean

A self-hosted office suite normally na stack. Nextcloud na PHP wey dey behind web server, plus database, cache and background job runner. The editor na another service beside am, like Collabora Online or ONLYOFFICE Docs, usually for im own container. Browser dey talk to am through HTTP. The document dey inside filesystem and database row, while the editing session dey inside the editor service.

Bento removes the stack. The download na Bento_Slides.bento.html, about 571 KB for release v1.0.11 (27 July 2026). Inside that one file dey:

• the editor, wey still be the viewer
• the presentation runtime wey dey show the deck full screen
• the fonts and images wey the deck dey use, embedded
• the document itself, as readable JSON block near the top of the file

Na saving be the unusual part. The file rewrites im own data block. The page asks the browser for write access through the File System Access API (browser interface wey lets page write back to file wey user pick), and for browsers wey no get that API, you go get download instead. When you edit deck, e produces new copy of the same self-contained file. Nothing dey upload, because nothing dey upload go.

Na this detail people dey get wrong when dem hear “single file”. E no be one server binary wey dey run your office suite as one process for your VPS. No process dey at all. Browser na the runtime, so VPS, if you use one, dey serve static file and nothing else.

Bento office suite wey dey available today

"Office suite" na wetin the project wan become, e never be the full list of wetin e get now. Na one application dey exist: bento/slides, wey be presentation editor. The roadmap list bento/spaces for notes, bento/dash for sheets and tables, and bento/vault. Dem plan each one as separate self-contained .bento.html file. If you need word processor or spreadsheet today, Bento no get am.

Release pace high. v1.0.6 for 21 July 2026 na the first shipping build, and v1.0.11 come out for 27 July 2026: six releases for seven days. This show say the maintainers dey active, but e also warn you about the software. Anything wey dey change that fast still dey find bugs. The release notes show am: fixes for large text wey dey crash live collaboration, stylesheet duplication for saved files, and chart baselines for negative values.

Why one file suit small VPS

To publish a deck, you only need copy one file enter directory wey your web server already dey serve. You no need orchestrate anything. You no need keep container running. You no need migrate database when you upgrade. Compare am with the editor services, using each vendor own published minimum requirements:

[
  {
    "label": "bento/slides (no backend)",
    "min_ram_mb": 0
  },
  {
    "label": "Collabora Online CODE",
    "min_ram_mb": 1024
  },
  {
    "label": "ONLYOFFICE Docs, Debian package",
    "min_ram_mb": 2048
  },
  {
    "label": "ONLYOFFICE Docs, Docker",
    "min_ram_mb": 4096
  }
]

These na vendor-published minimums as of August 2026. Dem no be numbers wey anybody measure for a running server. Collabora publishes 1 GB for the system plus about 50 MB for each user. So 1024 MB na the minimum before your first user connect. ONLYOFFICE Docs needs 2048 MB from the Debian package and 4096 MB for Docker. E still needs 4 GB of swap and 40 GB of disk. Bento editing backend needs 0 MB because Bento no get editing backend. Under either editor service, you still dey run Nextcloud itself with its database and cache. So, for 2 GB VPS, this difference decide wetin else you fit host.

Backups dey simpler for the same reason. To restore Nextcloud, you must restore files and database wey match each other for the same point in time. To restore one Bento deck, you only restore one file. E still need real backup with history, because the editor rewrites the file in place. Any write wey happen in place fit fail: scheduled restic snapshot of that directory go cover am.

One optional server component dey. Live collaboration uses wetin the project calls a blind relay. You fit host am yourself from server/sync-worker/ for the repository. The browser encrypts documents with AES-GCM (Galois/Counter Mode, an authenticated encryption mode). The room key never leaves the file. The relay keeps ciphertext, connection timing and hash of that key. If na only you dey edit, you no need relay.

Wetin You Give Up Compared With Nextcloud and Collabora

Access control na di biggest gap. For Bento, dem dey create di collaboration key together with di document, and e dey inside di file. So, anybody wey get di file na member of di session. To rotate di key na how you revoke person access. Dis model no get accounts, groups, single sign-on or audit trail. Nextcloud give you users, share links wey get expiry dates, quotas, server-side version history and mobile clients. If two people need different access levels to di same document, Bento no fit represent am.

Format interoperability na di second gap. Bento dey store im own JSON, and na exactly why you fit read di file and use script edit am. Collabora and ONLYOFFICE dey support round-trip for OOXML (di .docx and .pptx family) with high fidelity, because na di format wey di rest of di world go send you. Check di release notes to know wetin di version wey you download fit import and export before you build workflow wey assume PowerPoint compatibility.

Maturity na di third gap. Di project dey document im own rough edges plainly, and dis na point for im favour. Undo during live collaboration dey use snapshots, and e fit revert collaborator concurrent edit to di same property. Editing dey focus on desktop first, while phones dey better for viewing and presenting than editing. Di save-as menu never fit well for phone screen. Na dem be di known limitations for v1.0.11. Since e don dey exist for two weeks, unknown limitations still dey.

You fit trust for real documents?

Break the question based on wetin the document need. A conference talk, sales deck, or lecture wey you wan open again in ten years fit well, because the file carry im own editor and e no need the project to still dey exist for 2036. A contract with three reviewers, a retention policy, and a named approver no fit well, because that document need accounts and server-side history.

Two practical protections. Keep decks for version control or backup wey get history, because file wey dey rewrite itself when e save fit also corrupt during save, and you go need yesterday copy. And treat a .bento.html from person wey you no know as program instead of document, because na so e be: web page wey get complete application inside am. Open am the same way you go open any untrusted web page.

The automation matter really useful and e worth mention. Because the document na plain JSON inside the file, coding agent fit edit a .bento.html directly, and the project release a Claude Code skill for that. E work with local open-weight models too, so machine wey already dey run Ollama to serve your own model fit draft slides without sending anything comot from the machine.

Where Bento fit for small server

Bento dey among other single-purpose tools wey fit earn space for small VPS because dem small: RSS reader wey you host yourself or Actual Budget for personal finance. One job, small footprint, and data wey you fit read without the application. People wey dey replace their notes app with one of the Notion alternatives wey you fit host yourself dey make the same trade, and the wider guide on wetin you fit self-host cover the rest of that list.

If you need the complete document platform with users, sharing, and version history, Nextcloud for VPS with Docker, TLS and backups still be the answer. Bento no dey compete for that position. Na the thing wey you send give person outside your server as one file wey go open for dem without login or plugin.

FAQ

Bento na replacement for Nextcloud and Collabora?

No be for the same work. Nextcloud with Collabora or ONLYOFFICE gives you accounts, shared folders, permissions and server-side version history, and e need real server stack to provide dem. Bento gives you one portable file wey fit open anywhere and e no need server. Use Bento when the document suppose dey self-contained. Use the Nextcloud stack when different people need different access to the same document over time.

Bento need server or VPS?

No. A .bento.html file fit open from local disk for any modern browser and e fit edit offline. VPS matter for two optional things: to serve the file over HTTPS make other people fit download am, and to run the sync relay for live collaboration. You fit self-host the relay from server/sync-worker/ for the project repository, and e stores ciphertext plus connection metadata, so e no ever see your content.

Which format Bento dey use save documents?

E get im own JSON, written as readable block near the top of the HTML file, with fonts and images embedded alongside. Open the file for text editor and you fit read the document structure. Na why scripts and AI agents fit edit a deck in place. E also mean say the stored format no be OOXML, so no assume say .pptx workflow go work until you don test import and export for the release wey you dey run.

How collaboration dey work if user accounts no dey?

Dem mint the collaboration key when dem create the document, and e dey inside the file. So anybody wey hold the file fit join the session. Edits merge with a CRDT (conflict-free replicated data type, structure wey dey merge concurrent changes without central authority) and dem travel encrypted with AES-GCM. Presence names na claims, no be proof. So read the participant list as label, no be identity check. To revoke access mean say you rotate the key and redistribute the file.

Bento ready for important documents?

E get MIT license and dem dey develop am openly. E never reach two weeks old on 1 August 2026, and e get six releases for im first week. Treat am as software wey you dey evaluate this month, no be software wey you go standardise on this quarter. Keep every deck for backup with history. Test the export path wey you depend on before you depend on am. Keep anything wey get compliance or retention requirement for system wey get accounts and version history.