Guide: On-Premise
Practical guide for on-prem connectivity
Goal
Connect on-prem systems securely without delaying initial delivery.
The usual path: the meinGPT Outpost
When files or internal systems must not leave the building, you install the Outpost — an application with a graphical interface for Windows, macOS (Apple Silicon) and Linux that runs on a machine in your network. It makes your documents searchable and connects services that are reachable on that machine: databases in your own network and local MCP servers.
The Outpost establishes the connection outward itself. No port is opened in your firewall — what it needs is outbound HTTPS to *.meingpt.com. For this case that settles the question of VPN or allowlisting.
Early Access — free to try
The Outpost is in Early Access and a complete rebuild of the former DataVault — we no longer publish Docker images, existing installations are moved over and the data is re-indexed in the process (Moving to the new Outpost). Trying it costs nothing: 100 documents and one service are free. That is a preview, not a plan — it is enough to verify the installation and watch the Outpost work end to end. To put it into production, talk to us (enterprise@meingpt.com).
Set up an Outpost
Prepare the machine, install the app, pair it, release folders and services.
Moving off the Docker setup
From the previous-generation Outpost to the desktop application.
When meinGPT needs to reach a system directly
Some systems should not run through an Outpost but be reachable directly from meinGPT Cloud. There are three connection models for that:
- IP allowlisting
- Enterprise Connection Network
- VPN
When to choose what
- fast and lean: IP allowlisting
- controlled enterprise connectivity: Enterprise Connection Network
- full tunnel into private networks: VPN
Practical rollout
- start with one system and one clear use case
- align the connection model with IT security — or establish that an Outpost makes it unnecessary
- expand system by system