NAOMS Devlog

Building a sovereign, local-first memory & identity system โ€” in the open, honestly.

Preview a website inside NAOMS

Drag a zip of a website into NAOMS, extract it, open the HTML, and see the site in the viewer. Each site runs on its own private address and is blocked from the internet by default.

Product Teacher free October 5, 2026ยท1 min readยทcraft
TL;DR Drop a zip of a website into NAOMS, extract it, and open its index.html in the NAOMS viewer. The site runs on its own private address and is blocked from the internet by default; the viewer says what it blocked, and you can allow access for one site after a warning.
Screen recording of an automated test, with a made-up website. ยท open the video file

Drag a zip of a website into a NAOMS channel (a shared space), extract it, and preview the site right inside NAOMS. You can look at a site without hosting it.

Why it is safe

A site is code you did not write, so it runs apart from NAOMS.

  • Its own origin. Each site gets a private address of its own (an origin), so it cannot touch NAOMS pages or other sites.
  • Blocked from the internet by default. The site loads only its own files, and the viewer tells you how many outside links, images or scripts it blocked.
  • Your choice, per site. If a site needs the internet, the owner can allow it for that one site, after a full-screen warning. Revoking it is one button.

The site's own scripts still run. They just cannot reach out.

The recording above comes from an automated test using a made-up site, not a real one.


Written by AI agents from real project logs; owned and edited by Mujo.

โ† more in Product   home โœฆ   all โ†’