Demo Mode
Understand the fictional data, browser isolation, and simulated actions.
The public demo uses the same application with NASDASH_DEMO_MODE=true. Only tracked fictional fixtures are loaded; NASDASH_DATA_DIR is ignored. Visitors receive a synthetic administrator without login. Never enter real credentials or attach production data.
Isolation and limits
Demo changes stay in the current browser tab. With browser session storage available, settings, categories, topology, pages, device choices and simulated Docker state survive a reload and a change of server worker. Resetting the demo clears this temporary workspace and restores fictional fixtures. Clearing browser storage or ending its tab session can discard changes; this is not durable storage or a backup. Never enter real data.
Probes, monitoring, infrastructure APIs and Docker logs are fictional; background monitoring is stopped. Accounts, uploads, backups and real service links are blocked. Demo responses carry indexing restrictions through robots metadata, headers and the robots file; normal instances retain their usual indexing behavior. Calendar trials are part of the isolated fictional workspace; installed calendars remain stored on the server.
The browser carries its snapshot through /api/demo/workspace, enabled only on a server running demo mode, and serializes workspace requests within the tab. It does not need worker affinity or a shared server store. Legacy direct API clients using only the demo cookie still have process-local temporary state; they must not assume distributed persistence.
Local showcase
npm ci
npm run demoOpen http://localhost:2505. Use npm run demo:lan only on a trusted network or NASDASH_DEMO_PORT for another port. Capture assets with npm run demo:capture; the screenshot maintenance procedure remains beside the product’s capture tooling.
Hardened Docker demo
npm run demo:docker
# After visiting http://localhost:2505
npm run demo:docker:downThe docker-compose.demo.yml profile has a read-only filesystem, no host volumes or Docker socket/proxy, no host PID namespace and no Linux capabilities. An internal network isolates NasDash; an unprivileged Nginx proxy publishes the loopback port. Do not turn a real installation into a demo.
Hosted showcase
Vercel hosts the public stateless showcase. Import the same product repository as a separate Next.js project using the repository root and main production branch. Enable the demo flag for production and previews, and use a deployment-only random secret distinct from any real installation. Attach no persistent store, socket, VPN or private infrastructure connector. Server recycling does not by itself clear a snapshot retained in the browser tab. Browser storage remains temporary. Validate health, editing, reset, logs and mobile behavior after deployment. Persistent self-hosted installations require their own durable data store.
NASDASH_DEMO_MODE=true
NASDASH_JWT_SECRET=replace-with-a-demo-only-random-secret