Data & privacy (on-prem)
On on-prem, VTK uploads, conversion, filters, the Python session, and session files are processed on your organization’s Docker stack (mesh-api + viewer-ui). The browser renders surfaces; simulation data remains on that host, not on hosted Scenaven compute for your files.
Backend selection: One address (Infrastructure → On-prem).
Infrastructure · Choose infra
Hosted mesh-api & viewer-ui
Preview · ExamplesDocker on your machine
Full tool setSwitch in the viewer — not a separate browser address.
At a glance
| On Docker host | Hosted Scenaven cloud (preview) | |
|---|---|---|
| Open / convert | mesh-api + disk | No customer upload today |
| Clip / warp / extract · time | Your mesh-api | — |
| Python / simulation skills | mesh-api sandbox | — |
| Sign-in | — | Antinode session |
Diagram: On-prem trust & data flow.
What stays local
Browser ──LAN/VPN──► viewer-ui :8090 ◄──► mesh-api :8080 ──► ./data
| On the Docker host |
|---|
Open — .vtk, .vtkhdf, .vtp, .vtu |
| Clip / warp / extract, dataset info, time |
| Python session (server sandbox) |
| Examples prepared locally when required |
What may use the internet
Identity and application delivery are separate from simulation storage.
| Network use | Simulation VTK? |
|---|---|
| Sign-in (Antinode) | No — account session |
| Hosted shell / Help | No upload |
| Docker pull / kit zip | No — images and scripts |
| On-prem upload · filter · Python | Remains on host |
Optional: amAIra chat
| Mode | Data path |
|---|---|
| Slash skills / Python on the mesh | Your mesh-api (as with filters) |
| Cloud LLM (your API key) | Your provider — Antinode & amAIra |
| Ollama (local) | Local endpoint |
Scenaven does not bundle paid cloud LLM keys.
Storage
Typical mapping: host ./data → container /data/storage.
- Backup and disk capacity on that host are the deployer’s responsibility.
- Retention policy: see On-prem connection.
Cloud preview vs on-prem
| Cloud preview | On-prem | |
|---|---|---|
| Customer VTK | Not offered today | On Docker host |
| Examples | Hosted stack | Local stack |
| Server filters / Python on your simulation | Requires on-prem | mesh-api on host |
Cloud connection · On-prem setup
Roles
| Role | Responsibility |
|---|---|
| Viewer user | Antinode sign-in; Infrastructure → On-prem when the stack is available |
| Docker host operator | Run kit; keep viewer-ui and mesh-api reachable for On-prem clients |
Shared workstations
Docker host operations
- Maintain viewer-ui and mesh-api for On-prem clients (workstation, LAN, or VPN).
- Update images on a schedule.
- Back up
./data. - Optional: network controls on the Docker host when one server serves multiple engineers.
Further reading: Python session · Agentic workflows