On-prem connection

In on-prem mode, the same Scenaven Docker image runs inside your network. Data stays on your infrastructure; the viewer and mesh-api behavior match cloud.

Docker Docker
Viewer Viewer
mesh-api mesh-api

What you need

  • Docker (or Kubernetes) running the Scenaven stack
  • A bind-mounted storage volume (typically /data/storage on the host)
  • Browser access to the viewer-ui URL on your LAN or VPN

Starting the stack

Your administrator deploys the image with on-prem environment variables:

  • Local storage instead of GCS
  • mesh-api and viewer-ui on known ports or behind your reverse proxy
  • Optional AntiNode if you still use centralized auth

Open the URL they provide — often https://<host>/ for the shell or https://<host>/embed.html for the viewer directly.

Infrastructure panel

Open Infrastructure in the sidebar:

  • Status should read Connected when mesh-api is reachable.
  • Mode shows on-prem / local storage.
  • mesh-api URL should match your deployment (hostname, not only localhost if you browse from another machine).

Local conversion progress

Volumetric uploads show Local conversion in the sidebar footer with progress percentage — same UX as cloud, but files are written to the Docker volume.

Examples gallery

Examples are seeded into local storage on first start. Use Examples in the HUD the same way as in cloud.

Network tips

Scenario Recommendation
Viewer on same machine as Docker localhost is fine
Viewer on another PC on the LAN Use the server's hostname or IP in the URL
HTTPS termination at proxy Ensure WebSocket and upload paths proxy to viewer-ui

Mixed content (HTTP embed on HTTPS parent) will break API calls — keep schemes consistent.

Data residency

Uploads and compiled assets live on the mounted volume. Back up that volume per your retention policy. Uninstalling the container without backup removes session data.

Troubleshooting

Symptom Things to try
Infrastructure disconnected docker compose ps; restart mesh-api and viewer-ui
Upload fails immediately Disk full on volume; check mesh-api logs
Works on server, not on laptop Use LAN hostname, not localhost
CORS or cookie errors Open viewer through viewer-ui origin, not raw mesh-api port