Checking systems.

What this page covers

This page reports the health of the optional encrypted sync service only. It runs a live check against the sync API each time you load it, rather than showing a cached status from an earlier incident, so what you see above reflects the service right now.

Docmancer itself is local-first, which means an outage here does not stop you working. Your canonical memory lives as Markdown on your own disk, and indexing, recall, the MCP server, and every CLI command run entirely on your machine against that local copy. If the sync service is degraded, docmancer ask, docmancer setup, and your installed agent integrations keep working exactly as they do offline. The only affected operations are pushing and pulling encrypted snapshots between your own approved devices, account and billing changes, and recovery.

Anything you write while the service is unreachable stays safely on disk and syncs on the next successful connection, so there is nothing to replay by hand once the status returns to operational. If you are seeing degraded status for an extended period, or your local install is misbehaving in a way this page does not explain, run docmancer doctor for a local diagnosis first.