Console & operations

The Outpost has no web interface and no command line you need day to day. Everything there is to check and to operate sits in the application window on the machine itself — six tabs, and each answers exactly one question.

No window, no console, nothing at all? → Outpost does not start

Two bars enclose them: the tabs on top, and a status bar at the bottom that stays visible — process state with Start/Stop, the tunnel, and indexing progress. Those three values are true on every tab, which is why they live there and not on a page.

Verifying that it works

There is no health endpoint to call and no URL to open in a browser. Verification after setup is three glances:

1. Status bar, bottom left — if it reads Running with a port number, the server is up. If it reads Stopped, nothing is findable; press Start.
2. Connection tab → Run check — six individual checks from DNS to the system clock. All green means this machine reaches meinGPT.
3. Index tab — if the number of indexed documents climbs, the Outpost is working. If it sits at 0 while the Data tab shows a source, something is wrong with the path or the permissions — then go to Logs.

After that, the most honest test is a question in meinGPT whose answer can only come from one of the released documents.

Status — is it running, and what is it doing?

The tab reports state; it is not a table of contents. At the top, whether the tunnel to meinGPT is up and against which instance; below it, how many documents from how many sources are indexed and how many services are connected. While an indexing run is in flight, its progress and a remaining time show here.

If the Outpost halts indexing because the disk is filling up, a red card appears here with the free space, the configured minimum and the number of rejected files. The status bar tints along with it, but the explanation stays on this page — a 32-pixel bar cannot carry instructions.

Data — what does this machine make available?

Two lists on one page. Sources are the folders and shares being indexed; each card shows the path, the linked data source ID, the state and a Sync button for an immediate run. Services are databases and local MCP servers.

• Sync all kicks off a run across every source. Useful after a lot changed on the share.
• Remove drops the link and that source's index. Your original files are untouched — the Outpost only holds a derived index.
• While the Outpost is stopped, the list says so above the cards: the numbers cannot be current then.

A newly created service sits at Being set up until meinGPT has registered it.

Index — is it findable?

This is where you see what became of your files. First the figures — indexed, failed, not findable, vector coverage — then the explanation of how to read them.

More important than any figure is the Skipped by type card:

Skipped files are not indexed and will never be found. This is the most common reason someone concludes the AI is bad: the quote was inside a ZIP, the correspondence was in .msg files. The bars group by file extension, not by reason — "too large", "unknown format" and "no access" all land in the same bar.

At the end of the tab is how text is encoded: the built-in offline model or your own endpoint. That is the one knob on indexing there is to turn — details under Embedding models.

Connection — the network check

Run check walks the chain a pairing needs: proxy, DNS, TCP, TLS, whether meinGPT answers, and the system clock. When a check fails it names the cause and what to do about it — for intercepted TLS, also the name of the appliance doing the intercepting.

Below it, the Network requirements table with Copy: host, port, protocol and purpose, in the form you can hand to IT. Outbound only, no inbound ports.

If your network inspects TLS with its own root certificate, you select it on this page under Custom certificate → Your own root certificate.

Logs — what did it print?

The output of the processes the Outpost starts, filtered by API and Ingest, with Copy and Show in Explorer. The text is selectable.

System — what machine, and how do I get help?

Version and update state, hardware and free space, the deployment mode, and the two paths support asks for first: the configuration file and the data folder. Both live in the application data directory of the user the Outpost runs as → Where the Outpost stores data.

Export diagnostics writes a ZIP with configuration without secrets, logs and system details. It does not collect document files or document content — it does collect file paths, error messages and search queries. That is the file a support case needs; look inside before you send it.

At the foot of the page are the device settings: re-pair, change embeddings, run the wizard again, language, appearance — and, set apart in a red frame, Unpair.

Updates

The Outpost updates itself. It verifies against an Ed25519-signed manifest plus the checksum of the individual artifact; the System tab shows the state ("up to date", "downloading", "available"). There is no manual update step and no package repository for you to maintain.

Because the database is inside the application, an update brings its schema changes along. After an update, glance at the status bar: if the process is running again, the update went through.

Backups — what there is to back up

Nothing. That is the whole answer, and it is deliberate:

• The Outpost holds no original data. Everything it stores is a derived index of your own folders, shares and mailboxes. You back up the originals where they live — that was your job before the Outpost and it is after.
• The search index lives in the application's data folder (System tab, Data folder). It is reproducible: pair, connect the sources, let it index. Which folders exactly, and what is in them: Where the Outpost stores data.
• The credentials do not need backing up. If the machine is lost, issue a new pairing code in meinGPT and pair again; you revoke the old access in meinGPT.

So a rebuild costs the time of a full indexing run, not a data restore. What you should document instead: which path belongs to which data source ID. That is the only information that exists solely on this machine — the Data tab shows it on every source card.

When the machine reboots

After an operating-system restart the Outpost does not come up on its own. Until someone opens the window and presses Start, its sources are missing from answers — and in meinGPT that looks like an outage, because nobody is sitting at the machine.

On a server that is meant to run unattended, plan for it: either someone checks the status bar after a maintenance window, or talk to us (enterprise@meingpt.com) so we can set up start-on-login for your case.

Help

For everything else: export the diagnostics bundle from the System tab and send it to enterprise@meingpt.com. It contains what we need to diagnose the problem — and therefore also paths and error messages from your operation: what it actually contains.