---
title: "Enterprise Connection"
description: "Secure reverse proxy connection between local enterprise systems and MeinGPT Cloud"
canonical_url: "https://meingpt.com/en/docs/privacy-security/enterprise-connection"
language: en
---

# Enterprise Connection

The Enterprise Connection enables a secure and scalable connection between your local enterprise systems and the MeinGPT Cloud. At its core is an innovative **reverse proxy process** that securely connects local Outposts, MCP servers, and other enterprise components to the cloud.

**Using an Outpost?** The Outpost establishes its connection to MeinGPT automatically during pairing – no separate request needed; see [Setting up an Outpost](/en/docs/integrations/vault/deployment). Contact our team at [enterprise@meingpt.com](mailto:enterprise@meingpt.com) if Outposts are not yet enabled for your workspace, if you want to connect **additional** internal systems such as databases, local MCP servers or internal applications, or if you still run the former Docker installation.

## How does it work?

**Reverse Proxy Principle:** Instead of MeinGPT reaching into your systems from outside, each local Outpost or MCP server opens an outgoing connection to the MeinGPT Cloud itself and keeps it open. Requests from the cloud travel back over that already-established channel — your firewall never has to open a single incoming port.

- 🔄 **Outgoing Connections:** Your systems establish the connection to the cloud
- 🛡️ **No Incoming Ports:** No firewall opening required
- 🏢 **Local Data Sovereignty:** All data remains in your systems
- ⚡ **Multi-Location Capable:** Any number of locations can be securely connected

## Multi-Location Enterprise

**Cross-Location Intelligence:** Each location stays technically independent but can optionally be included in a shared search: a query can search all connected Outposts at once, or target just one specific location — you decide which per query or assistant. Management is centralized in a single dashboard, while the data itself stays at its respective location.

- 🔍 **Cross-Location Search:** Optionally search all Outposts simultaneously
- 🎯 **Location-Specific Search:** Targeted queries to specific locations
- 🔗 **Central Management:** One dashboard for all locations
- 🏛️ **Compliance-Compliant:** Data remains at respective locations

## Security

**Encryption:**
- 🔐 **TLS:** All connections are encrypted with TLS 1.2 or 1.3
- 🔑 **Perfect Forward Secrecy:** Unique session keys for each connection
- 🔒 **Signed requests:** Every request from MeinGPT to the Outpost is signed and verified by the Outpost

**Enterprise-Grade Security:**
- 🎫 **Device-specific keys:** Each Outpost creates its own key during pairing, and the key never leaves the device
- 📊 **Audit Trails:** Complete tracking of all accesses
- 🌍 **GDPR Compliant:** Data remains at origin location

## Setup

**Contact our Enterprise team for:**
- **Enablement:** Outposts and the services preview for your workspace
- **Setup Support:** Technical consultation for your architecture
- **Compliance Consultation:** GDPR and legal requirements

## Frequently Asked Questions

### How do I get access credentials?

An Outpost needs no credentials from us: the device creates its own key during pairing, and an admin of your workspace approves the pairing in MeinGPT. To connect further internal systems, contact enterprise@meingpt.com.

### Can multiple locations be connected?

Yes, the reverse proxy process supports any number of locations. Each location runs its own Outpost, which pairs with a key the device creates itself (no credentials from us needed), and can be operated independently. By default, a workspace can register one Outpost. Contact [enterprise@meingpt.com](mailto:enterprise@meingpt.com) to raise the limit.

### What happens to my data?

All data remains in your local systems. The Enterprise Connection only transmits queries and responses, never your original data.

## Related

### [Outpost](/en/docs/privacy-security/data-vault-privacy)

The local Outpost the Enterprise Connection connects to — architecture and data flow

### [PII Filter](/en/docs/privacy-security/pii-filter)

How personal data is redacted before processing outside the EU