01 / FS
Virtual filesystem
An OPFS-backed sandbox filesystem with read, write, move, watch, and local directory mounting. Files are directly addressable by URL.
/nos/fs/
NoneOS Core is a virtual operating system that runs in the browser: a virtual filesystem, decentralized identity, peer-to-peer messaging, and a micro-frontend container. Static files are enough to boot it — apps no longer need a backend of their own.
Open a web page and you have a virtual computer of your own: files, apps, identity, and connections to your other devices, all in one place. Each app gets its own space, so it can be installed and run on its own while sharing the same files and connections.
No server to rent. No backend to install. If you can put a static site online, NoneOS can run there. Apps stay out of each other's way, and your data stays on your device by default.
From interface to app, down to files, identity, and network, every layer runs inside the browser's security model.
Apps running in Mazmot / NoneOS can call these capabilities directly, as naturally as using the browser's DOM.
An OPFS-backed sandbox filesystem with read, write, move, watch, and local directory mounting. Files are directly addressable by URL.
/nos/fs/
ECDSA P-256 key identity, challenge-response authentication, signed profiles, and a certificate system. No central accounts, no password database.
/nos/user/
Peers are discovered over WebSocket, then upgraded to a direct WebRTC connection. Messages are end-to-end encrypted by default; relays only forward ciphertext.
user.connectUser()
DataPublisher chunks and signs files, then distributes them over P2P. An app link carries only the publisher ID and the content hash.
/nos/publish/
A Service Worker intercepts requests and maps apps to virtual directories. Apps publish independently, load on demand, and share one runtime.
sw/dist.js
A localStorage-style async API built on IndexedDB, with structured data, cross-tab sync, and file handles.
/nos/storage/
Install NoneOS Core into any static page and you get in-browser user identity and messaging. No backend to install, no database to migrate.
// Add NoneOS Core to a static page
import { getUser } from "/nos/user/main.js";
const user = await getUser("my-app");
console.log("My ID:", user.userId);
const remote = await user.connectUser(targetUserId);
const [session] = await remote.getSessionIds();
await remote.send(session, {
text: "Hello from the unhosted web.",
});
remote.bind("message", ({ detail }) => {
console.log("peer says:", detail.data);
});NoneOS uses capabilities the browser already has to take a lighter peer-to-peer path: no gas, no node operations, and no handing your data to a platform.
| Dimension | Traditional cloud apps | Blockchain Web3 | NoneOS |
|---|---|---|---|
| Runtime | Central servers + database | On-chain contracts + nodes | Browser-based static runtime |
| Identity | Platform account | On-chain address / wallet | Local ECDSA keys |
| Data location | Platform servers | Public ledger / off-chain storage | User devices / direct transfer |
| Deployment | Build, upload, operate | Contract deploy + gas | Static files / no backend |
| Network path | Every request through a central server | Nodes / RPC | Direct WebRTC + encrypted relay |
| Offline support | Limited | Node-dependent | Local-first / offline-capable |
| Cost model | Ongoing server and bandwidth bills | Gas + infrastructure | Static hosting + optional relay |
NoneOS Core is open source and running today. It can be the infrastructure under your next app, or the best way to understand peer-to-peer networks.