Local Environments
Keep your MiddleGround Environment on your Mac or your own Docker host. Work with it through your AI assistant and the MiddleGround web interface.
Find your Connector ↓
The same workspace, stored locally
Your Things, context and artifacts live on your equipment. The Connector makes that Environment available through MiddleGround, so you can open it in the browser or work with it through your connected AI assistant.
The Connector makes an outgoing connection. No port forwarding is needed. Keep your equipment online whenever you want to reach the Environment remotely.
Where your data lives
Use Workspace, Views, Reports and Dashboards with either storage choice. In a Connected Environment, their saved definitions live alongside your local content. Your Connector must be online to use them through MiddleGround.
This overview describes saved data, not just where it is displayed. Local means your Mac or the Docker host you choose; a Docker host can also be a server you rent.
| Data | MiddleGround Cloud | Mac Connector | Docker Connector |
|---|---|---|---|
| Things, Context, Facts & relationsSource records and their saved history. | Cloud | Local | Local |
| Documents & artifactsFiles, Whiteboards and saved outputs. | Cloud | Local | Local |
| Workspace, Views, Reports & DashboardsSaved layouts, definitions and configuration. | Cloud | Local | Local |
| Thing titles & routing identitiesThe Cloud retains the inventory needed to route requests to your Environment. | Cloud | Cloud + local | Cloud + local |
| Environment setupName and identity; an initial purpose supplied at creation also remains in Cloud provisioning metadata. | Cloud | Cloud + local | Cloud + local |
| Accounts, sign-in & assistant consentThe Cloud manages your account, sessions and assistant grants. | Cloud | Cloud | Cloud |
| Permissions & activity recordsCloud access checks and security records; delegated user IDs, display names, permissions and local operation records also persist with the Connector. | Cloud | Cloud + local | Cloud + local |
| Connector credentials & connection stateA local credential (Mac Keychain or Docker private config); Cloud credential digests, pairing and connection records. | Not needed | Cloud + local | Cloud + local |
Requests and responses pass through MiddleGround in memory. Connected content is not kept as a Cloud replica. Content you open reaches your browser; content you share with an AI assistant reaches that provider. Downloads, browser caches and assistant retention are outside this storage comparison.
The Docker package includes PDF and Whiteboard export workers. The current Mac preview does not include those workers. Back up your complete local Environment directory, including hidden metadata and history; protect the Connector credential separately.
Two ways to connect
A Mac app for an easy start, or Docker for a setup you manage yourself. Both connect to the MiddleGround web interface and your AI assistant.
For your Mac
A simple start on your Mac. A small menu-bar app guides you through connecting a local Environment.
Your connection credentials are stored in Keychain. You can choose to start the Connector when you log in.
Request beta access →Requires macOS 26 or later. The Mac Connector is currently a development preview; the public signed download is being prepared. Finder integration is awaiting final distribution testing.
The Mac preview does not yet include the PDF and whiteboard export workers available in the Docker package.
For your own infrastructure
Run your Environment on a Docker host you manage. A natural fit for a home server or a local machine you keep online.
The package includes document and whiteboard renderers. Your Environment lives in a persistent local directory that you manage and back up.
Open MiddleGround to set up →The current package targets Linux amd64. Docker on Mac or Windows needs a Linux runtime; ARM hosts currently need amd64 emulation. Downloads and matching setup instructions appear in your Environment’s connection panel.
Prefer a native Windows app? Windows support is on the way.
Everyday use
Use the MiddleGround TTM web interface to work with your Connected Environment. Both Connector options use the same web interface.
Connect your assistant to MiddleGround and grant access to the Environment. Your assistant can work with the information you authorize, while the source content stays on your equipment.
Connect your AI assistant →Your Mac or Docker host must be awake, online and running the Connector for remote access. When it is disconnected, the local files remain in place, but the Environment is unavailable through the web interface and assistant.
MiddleGround manages accounts, permissions and connection metadata. Requests and responses pass through MiddleGround, and relevant content is shared with the AI assistant you use. Local storage does not mean that processing stays entirely on your device.
Choose Connected when creating an Environment. Setup starts with an empty local directory; it does not automatically move an existing Cloud Environment or import an existing library.
You manage the local storage and its backups. Follow your Connector’s backup instructions and keep the complete Environment directory, including its hidden metadata and history.
Your next step
Choose where your Environment lives. Keep the work connected.
We measure tab sessions, pages, visible time and approximate city/country for 90 days. No cookies or stored IP addresses. Temporary session storage expires after 30 minutes of inactivity or four hours. Do Not Track and Global Privacy Control disable measurement.
MiddleGround