On-prem connection

On-prem runs mesh-api and viewer-ui on your Docker host while the viewer remains at your Scenaven URL. Select Infrastructure → On-prem when the stack is available. VTK and session files reside on that host. The full tool set is available: uploads, clip/warp/extract (compile), dataset info, Python, and amAIra.

See One address and Data & privacy (on-prem).

Docker Docker
Viewer Viewer
Server Server

Why on-prem

This is how you use Scenaven on your own simulations today.

For where your files stay and what still uses the internet, read Data & privacy (on-prem) and On-prem trust & data flow.

Hosted cloud is a preview on prepared Examples. The full tool set on your VTK files runs on on-prem Docker (workstation, lab server, or VPN-reachable host).

Switch from the viewer

  1. Click Infrastructure (top right) — see One address for screenshots.
  2. In Choose infra, select On-prem.
  3. Open Self-hosted setup. That panel lists the Docker setup in order. Follow those steps on the machine that will run Scenaven. You need Docker there before the later steps can succeed.

When Docker setup from that panel is finished, stay in Choose infra with On-prem selected and complete the connect step the panel shows. Infrastructure then reads Connected and On-prem. Uploads, server-side clip/warp/extract, Python, and amAIra in this viewer use that machine.

Choose Cloud in the same panel to switch back to the hosted preview.

Local viewer-ui is not running

If you select On-prem in Choose infra while the Docker stack is not running on this machine, the auth shell replaces the 3D viewer with a setup card instead of leaving you on a blank frame.

Local viewer-ui is not running — Docker stack unreachable on this machine
Local viewer-ui is not running — Docker stack unreachable on this machine

What it means

  • The auth shell session remains active. The embedded viewer is paused until local mesh-api (:8080) and viewer-ui (:8090) respond.
  • The health line lists which ports did not answer — typical when Docker Desktop is stopped or run-on-prem has never been run on this PC.

What to do

  1. Download scenaven-on-prem-setup.zip from the card (or use the kit you already extracted).
  2. Run run-on-prem.sh / run-on-prem.bat on the machine that should host Scenaven.
  3. Click Retry (refresh icon) or select On-prem again in Choose infra once both services are up.

Use the cloud button on the card to return to the hosted preview without starting Docker.

What you need

Viewer users

  • Antinode sign-in (standard for cloud and on-prem)
  • Infrastructure → On-prem and Connected when the stack is running

Who runs Docker (IT / lab admin)

  • Docker on the host that will run mesh-api and viewer-ui
  • That host reachable from browsers using On-prem (often the same workstation, or your network / VPN)
  • Disk space for session files and examples

After it connects

Infrastructure should say Connected, with on-prem selected.

  • Uploads show Local conversion at the bottom of the sidebar. The file stays on that machine.
  • Examples works as it does in the cloud. Datasets are prepared the first time the stack starts.
  • Open is available for your own .vtk, .vtkhdf, .vtp, and .vtu files.

Stay in sync with cloud releases

Cloud — ships each release Cloud — ships each release
On-prem — images you last pulled On-prem — images you last pulled
Viewer — compares & warns Viewer — compares & warns
On-prem viewer update banner in the signed-in embed
On-prem viewer update banner in the signed-in embed

How releases flow

  • Cloud updates on every Scenaven deploy and publishes the current on-prem kit + fresh :on-prem-latest images.
  • Your machine keeps running whatever Docker pulled last time — until you run the kit update script again.
  • Lag is normal; staying current is your refresh step (not automatic).

When the banner appears

  • You are signed in on the Scenaven site and Infrastructure is Connected · On-prem.
  • The viewer compares two build revisions (not something you type by hand).
Banner row What it means
Running on this machine (Docker viewer-ui) Revision in your local stack
Published by cloud deployment Revision cloud expects for on-prem right now
Action line Pull images + restart containers

What to do (same as first setup)

  1. Open the folder from Infrastructure → Self-hosted setup (your kit).
  2. Run run-on-prem.sh (macOS/Linux) or run-on-prem.bat (Windows).
  3. Wait for Docker to pull and restart mesh-api + viewer-ui.
  4. Confirm Infrastructure shows Connected · On-prem again.

Good practice — refresh on a schedule

  • Re-run the update script periodically (e.g. monthly or after a Scenaven release note), not only when the banner shows.
  • Treat cloud as the rolling latest line; on-prem matches it after you pull.
  • Dismiss hides the banner for this browser tab only — it can return while you are still behind or after a newer cloud publish.

No banner?

  • You may already be current, or the viewer could not compare (network / kit fetch).
  • When unsure, run the update script anyway — safe if images are already up to date.

Where the files live

Uploads stay on the machine running Scenaven. Back that machine up the way you back up other data there.

See Data & privacy (on-prem) for storage layout and who does what (users vs Docker host).

Troubleshooting

What you see What to try
The download in Choose infra fails Sign in on the cloud home page first, or leave the viewer and open it again from the home page
Local viewer-ui is not running Docker is not up on this machine. Run the kit’s run-on-prem script, then Retry or select On-prem again — see above
Infrastructure stays disconnected Docker setup in Self-hosted setup is not finished. Follow those steps again, then switch to On-prem
The connect step fails This browser must be able to reach the machine where Docker is running. Finish the panel’s setup steps, then switch to On-prem again
An upload fails Check free disk space on the server, then the server logs described in the kit README
On-prem viewer update available Your Docker images are behind the latest cloud kit. Run run-on-prem.sh or run-on-prem.bat in your setup folder, then confirm Infrastructure is Connected again