On-prem trust & data flow
This page is for operators and security reviewers: where simulation data moves when you run Scenaven on-prem, and what still depends on the hosted sign-in shell.
Two planes
Scenaven separates:
- Data plane — VTK upload, conversion, filters, Python, and session files on your mesh-api and disk.
- Control plane — Sign-in, entitlements, and (optionally) agent configuration through Antinode, plus delivery of the auth shell and help site from Scenaven hosting.
Your simulation files for on-prem work stay in the data plane on infrastructure you run.
Data plane (simulation stays with you)
┌──────────────────────────────────────────────────────────────────────────┐
│ Engineer browser (Scenaven auth shell + embed) │
│ Three.js viewport · Scene (OpenUSD tree) · Selected prim · Python / amAIra │
└───────────────────────────────┬──────────────────────────────────────────┘
│ HTTPS (your network / VPN)
│ uploads · compile · filters · REPL · sync
┌───────────────────────────────▼──────────────────────────────────────────┐
│ Your machine or server (Docker) │
│ ┌─────────────────┐ proxy/API ┌─────────────────────────────┐ │
│ │ viewer-ui :8090 │ ◄──────────────────► │ mesh-api :8080 │ │
│ │ embed + static │ │ VTK · USD scene · Python │ │
│ └─────────────────┘ └──────────────┬──────────────┘ │
│ │ │
│ ▼ │
│ host ./data → /data/storage │
│ (session + uploads) │
└──────────────────────────────────────────────────────────────────────────┘
Trust boundary: VTK work runs on your mesh-api. Antinode provides sign-in for the Scenaven shell; Docker has no separate user directory. Network access to the Docker host is an organizational control, independent of Antinode.
What crosses this boundary: VTK bytes, filter settings, REPL code, and compiled geometry move between the browser and your viewer-ui / mesh-api endpoints (often localhost or a LAN host) — not into Scenaven cloud storage for on-prem uploads.
Control plane (sign-in and app delivery)
┌─────────────────────┐ ┌──────────────────────┐
│ Engineer browser │ │ Antinode │
│ │ sign-in │ identity · session │
│ Hosted auth shell │ ───────►│ entitlements │
│ (Scenaven URL) │ └──────────────────────┘
└──────────┬──────────┘
│ embed iframe (postMessage auth snapshot)
▼
┌─────────────────────┐ ┌──────────────────────┐
│ viewer-ui embed │ │ Optional: help / │
│ (cloud or :8090) │ │ kit metadata fetch │
└─────────────────────┘ └──────────────────────┘
With on-prem, the embed is served from local viewer-ui; VTK work uses local mesh-api. The auth shell is typically hosted at your Scenaven URL. See One address.
Not in this path for on-prem uploads: Your VTK file content is not sent to Scenaven cloud conversion for the on-prem data plane described above.
Optional: amAIra and LLMs
┌──────────────── Browser ────────────────┐
│ amAIra tab │
└───────┬─────────────────────┬───────────┘
│ │
│ Ollama on your LAN │ BYO cloud API key
▼ ▼
┌───────────────┐ ┌───────────────────┐
│ Local Ollama │ │ Provider you chose │
│ (no Scenaven │ │ (OpenAI, Anthropic,│
│ LLM billing) │ │ etc.) │
└───────────────┘ └───────────────────┘
Simulation slash skills and the Python session use mesh-api on your stack. Chat only leaves your environment when you configure a cloud model or point amAIra at Ollama. Scenaven does not include commercial LLM API keys — see Antinode & amAIra.
Components
| Component | Role in on-prem mode | Holds simulation VTK? |
|---|---|---|
| Auth shell | Sign-in, iframe host, Infrastructure mode | No |
| viewer-ui | Serves embed, proxies API to mesh-api | No long-term VTK store |
| mesh-api | Conversion, filters, time, Python REPL | Yes — active session + on-disk storage |
| Browser | Rendering, UI, probes on streamed surfaces | Only what is needed to draw and probe |
| Antinode | Account session, entitlements | Not your mesh files |
| Docker registry pull | Delivers mesh-api / viewer-ui images | No customer data |
Comparison to hosted cloud preview
Cloud preview (today) On-prem (full tool set)
───────────────────── ─────────────────────────
Examples on hosted stack vs. Your uploads on YOUR disk
No customer Open/upload vs. Open + filters + Python
Learn the viewer vs. Production-style workflows
Hosted customer upload is a future, explicitly enabled offering — not what the preview provides today. See Cloud connection.
Hardening pointers
Hardening targets the Docker host that stores VTK. Sign-in remains Antinode via the Scenaven shell.
| Topic | Guidance |
|---|---|
| Hosting | Deploy viewer-ui + mesh-api on trusted infrastructure; On-prem clients must reach that stack (workstation, LAN, or VPN) |
| Network | Optional: restrict access to the Docker host at the network layer |
| REPL | Sandboxed but powerful — treat mesh-api like internal compute on that host |
| Updates | Re-run kit scripts to pull current images — on-prem updates |
| Backups | Treat ./data (or your volume) as source of truth for session files |