Zeno is a client-side game launcher and dashboard that runs entirely in your browser — part of the Eclipse Family. There is no backend, no database, and no server-side logic. Games are intercepted and served by a Service Worker, stored in IndexedDB, and survive browser restarts without re-uploading. You decide how many games to store; Zeno does not impose a fixed limit.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/xXmizzeryXx/zenodeployment/llms.txt
Use this file to discover all available pages before exploring further.
Core architecture
Zeno is built on three browser primitives working together:- Service Worker (
zeno-game-sw.js) — intercepts all fetch requests to/zeno-games/{gameId}/*and serves files from an in-memoryMap. When you load a game, its files are transferred to the Service Worker viapostMessage. The SW responds with aGAME_REGISTEREDconfirmation before the game iframe opens. - IndexedDB (
zeno-games-db) — stores game metadata and all file buffers for uploaded and Git-imported games. On the next page load, games are automatically restored and re-registered with the Service Worker — no re-uploading required. - No server — once Zeno’s static files are served over HTTP or HTTPS, everything else happens in the browser. There is no API to call and no data leaves your machine unless you use R2 import.
Pages and apps
| Page | File | Description |
|---|---|---|
| Dashboard | index.html | Home screen with clock, greeting, app grid, and cloak system |
| Game Library | games.html | Upload, import, search, and launch games |
| Terminal | — | Built-in terminal emulator accessible from the dashboard |
| Movies | — | Movies browser accessible from the app grid |
| AI assistant | — | AI assistant accessible from the app grid |
What makes Zeno different
No server required
All game files are served by a browser Service Worker. No backend, no database, no hosting costs beyond a static file server.
Persistent library
Uploaded and Git-imported games are saved to IndexedDB and automatically restored the next time you open the page.
Multi-source import
Load games from local folders, GitHub, GitLab, Forgejo/Gitea instances, or Cloudflare R2 buckets — all from the same interface.
Tab cloaking
Disguise the browser tab with preset identities — Google Classroom, Khan Academy, Desmos, and more — with a single click.
Where to go next
Get started with Zeno
Deploy Zeno and launch your first game in four steps.
Game Library overview
Learn how to add, manage, and play games.
Dashboard overview
Explore the dashboard, cloak system, and app grid.
Service Worker reference
Understand how the SW intercepts fetches and handles restarts.
Zeno requires an HTTP or HTTPS origin. It will not work when opened directly from the filesystem using a
file:// URL, because browsers do not allow Service Worker registration on that scheme.