Outpost

Outpost connects selected files and approved services from a local network to meinGPT. The encrypted connection is established outbound from the Outpost device, so no inbound internet port is required. Local folders are indexed on the device and provided as knowledge collections.

PostgreSQL, local MCP servers, and internal HTTP endpoints can be connected as bounded services. These service connections are in private beta and require explicit workspace admin approval. PostgreSQL access distinguishes read-only from read-write, while credentials stay on the Outpost device. A reachable source is not automatically available to every assistant.

Outbound does not mean no data is processed: approved content may be transferred to meinGPT to produce an answer. Data flow, permissions, and permitted actions need documentation for each use case. For supported cloud services, an integration is usually simpler; Outpost remains the controlled path to local sources and services.