---
title: "Guide: On-Premise"
description: "Practical guide for on-prem connectivity"
canonical_url: "https://meingpt.com/en/docs/integrations/guide-on-premise"
language: en
---

# Guide: On-Premise

## 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** on a machine in your network. It 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.

What an Outpost is, system requirements, the free preview, and setup: [Outpost overview](/en/docs/admin-guide/outposts).

## 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

1. start with one system and one clear use case
2. align the connection model with IT security — or establish that an Outpost makes it unnecessary
3. expand system by system

## Related

- [Outpost (on-premise)](/en/docs/integrations/vault)
- [Connections (Cloud/On-Prem)](/en/docs/integrations/connections-cloud-on-prem)
- [System Guides](/en/docs/integrations/system-guides/file-shares)