Licensed to be used in conjunction with basebox, only.
// integration
VPN / networking
Applies to
Product: Cloud · Server · Audience: IT / network · Platform Operator · Security reviewer
Network paths between users, basebox and connected systems – including remote maintenance access when basebox is commissioned to operate a server. This page is the template for your firewall rules: it lists every path, its direction and its port.
The paths at a glance
flowchart LR
U["Users / browsers"] -->|"HTTPS 443"| BB["basebox platform<br/>frontend · AISRV · Keycloak"]
API["API clients"] -->|"HTTPS 443"| BB
BB -->|"OpenAI-compatible API<br/>internal or TLS"| INF["Inference endpoint"]
BB -->|"443 / system-specific"| SYS["Business systems<br/>wiki · tickets · IMAP"]
BB -->|"HTTPS 443, provider hosts only"| WEB["Web search provider"]
BB -->|"389 / 636"| LDAP["LDAP / AD"]
BB -->|"443"| IDP["OIDC provider"]
BB -->|"587 / 465"| MAIL["Mail server"]
BB -.->|"443, installation & updates"| REG["Image registry<br/>gitea.basebox.health"]
OPS["basebox operations"] -.->|"PAM / VPN, only if commissioned"| BB
style BB fill:#f4f2ee,stroke:#524e47,color:#1d1e1c
style INF fill:#dbeafe,stroke:#1e40af,color:#1d1e1c| Path | Direction | Protocol / port | Required? |
|---|---|---|---|
| Users → basebox | inbound to basebox | HTTPS 443 | Yes |
| API clients → basebox | inbound to basebox | HTTPS 443 | If the API is used |
| AISRV → inference | internal or to a separate GPU host | OpenAI-compatible API; TLS when crossing hosts | Yes |
| basebox → business systems (connectors) | outbound | system-specific, mostly HTTPS 443; IMAP 993 | Per connector |
| basebox → web search provider | outbound | HTTPS 443 to api.staan.ai (default) or duckduckgo.com, html.duckduckgo.com, lite.duckduckgo.com |
Only with web search |
| Keycloak → LDAP/AD | outbound | TCP 389 / LDAPS 636 | Only with LDAP |
| Keycloak → OIDC provider; browser → provider | outbound / public | HTTPS 443 | Only with SSO |
| AISRV → mail server | outbound | TCP 587 (STARTTLS) / 465 (TLS) | For invitations |
| Cluster → registry and package sources | outbound | HTTPS 443 | Installation and updates; alternative: offline transfer |
| basebox operations → server | inbound, controlled | PAM / VPN, as agreed | Only if operations are commissioned |
The list of domains for installation (Ubuntu, Docker, Kubernetes, NVIDIA, Helm, registries) is in the Server Preparation Guide.
Principles
- Users never talk to inference directly. Only AISRV reaches the inference endpoint; it requires an API credential and is not exposed to end users.
- Connectors reach only their target system. The MCP gateway enforces an egress allowlist per connector. Your firewall should mirror that: one rule per connector, one destination.
- Web search queries leave the environment – without user identity and user IP, via basebox's connection. Everything else stays inside the approved data processing boundary.
- Prompts, retrieved context and document content travel from the application server to the inference server. If both are on separate hosts, both belong in the same data processing boundary and the path is TLS-protected.
basebox Server
In the customer data center: you control all paths. Users access from the company network or via VPN. Restrict outbound paths to what the installation uses; in fully air-gapped operation, web search and online model downloads are unavailable – see Air-gapped environments.
Hosted at basebox: network connectivity and physical access lie with basebox; your users reach the server via HTTPS or VPN. The server remains dedicated – see Hosting at basebox.
Separate application and inference servers: the application server can be CPU-only; only AISRV may reach the GPU host, with TLS and an API key. Guide and verification steps: Deployment topologies.
TLS without internet: Let's Encrypt is not required. global.tls.mode=existing-secret with a certificate from your internal CA or local for evaluation – see Networking (bare metal).
Remote maintenance by basebox
Where basebox is commissioned to install or operate, access takes place via a controlled, agreed path – typically privileged access management (PAM) and/or VPN, time-limited and approved by the customer. Maintenance access is enabled exclusively for support purposes and disabled afterwards. What is logged, who approves and how access is revoked: Remote maintenance.
Without an operations engagement there is no access by basebox to your server.
basebox Cloud
Users reach your environment over the internet via HTTPS. For connectors and mail, the Cloud has to reach your systems from the Noris data center – i.e. inbound into your network. Options for this and the IP/egress aspects are under Network connectivity (Cloud). For identity, OIDC is usually simpler than LDAP because no inbound path into your directory is needed.
Checklist
- Inbound 443 to basebox opened for users (and API clients)
- AISRV → inference allowed, everything else to the inference host blocked
- Exactly one outbound rule to the target system per enabled connector
- Web search: only the hosts of the chosen provider, or none at all
- LDAP 636 or OIDC 443, depending on identity model
- SMTP 587/465 to the mail server
- Registry access for updates or an offline transfer procedure
- Remote maintenance path agreed contractually and technically – or explicitly none
Next: Enterprise integration · Data flows