TrueForge Postgresok
Holds TrueForge's sessions AND its provider credentials
Dropping this volume loses the OpenRouter provider configuration — it lives here, not in the container environment and not in this repository.
- state
- ok for 3d · since 04:10Z
- 24 hours
- 100% 1,413 samples
- 7 days
- 99.99% 10,056 samples · 1 down
- 30 days
- 100.00% 43,178 samples · 1 down
- all time
- 100.00% 43,178 samples · 1 down · observed 56d
- response
- 21 ms now p50 9 ms p95 55 ms · 1,440 samples, 24h
- last failure
- 3d ago · down — [Errno -3] Temporary failure in name resolution
- probe
- tcp · the address is not published on this page
expects a TCP connection
inside the network
TrueForge Redisok
Queues and schedule state for the chat
- state
- ok for 3d · since 04:10Z
- 24 hours
- 100% 1,413 samples
- 7 days
- 99.99% 10,056 samples · 1 down
- 30 days
- 100.00% 43,178 samples · 1 down
- all time
- 100.00% 43,178 samples · 1 down · observed 56d
- response
- 26 ms now p50 9 ms p95 51 ms · 1,440 samples, 24h
- last failure
- 3d ago · down — [Errno -3] Temporary failure in name resolution
- probe
- tcp · the address is not published on this page
expects a TCP connection
inside the network
TAG Staff databasenot checked
A `paperclip` database inside supabase-db, with its own role
NOT a second Postgres. It is a database of its own inside the existing supabase-db service, owned by a `paperclip` role that can reach nothing else — so a Paperclip migration cannot touch the product's tables, and a dump of one is not a dump of the other. Nothing on this page has a credential for it, so this page will not claim to have checked it: the Postgres row in the data tier is what says the server is up. Paperclip runs on 15.8 — established by running its migrations against supabase/postgres:15.8.1.085, not assumed from its compose, which pins 17. See ../paperclip/README.md.
- state
- not checked
- shipped by
- nothing — it is a database inside the Supabase service, created once by hand; paperclip/README.md has the three statements
Never probed, so there is nothing to remember. Its state is read from the catalogue.
TrueForge controllernot checked
Runs the schedule-dispatch loop, out of process
A worker with no listening port and no health endpoint. Nothing on the network can observe it, so this page will not pretend to: if schedules stop firing, read its container log. Reporting a guess as green is the failure this page is built to avoid.
- state
- not checked
- shipped by
- this repository, pinned to the same image as /chat
- depends on
- TrueForge PostgresTrueForge Redis
Never probed, so there is nothing to remember. Its state is read from the catalogue.
Xero MCP servernot deployed
Xero sign-in and the books, for TRUSS, the gateway, both portals and /chat
This environment uses the shared server in Azure, which this page does not probe: it is not on this edge.
- state
- not deployed
- shipped by
- xero-mcp-server's Build & Publish workflow publishes the image from its main; infra/ovh pins it and runs it on the apps server
Never probed, so there is nothing to remember. Its state is read from the catalogue.
Hydra (OAuth)not deployed
Issues the OAuth tokens the MCP clients, the Harness and TrueForge present. It holds clients, consents and keys, and no people
This environment runs no OAuth server: sign-in is Dynamic alone.
- state
- not deployed
- shipped by
- this repository: hydra/ publishes the image, and infra/ovh pins it and runs it on the data server where auth_host is set
Never probed, so there is nothing to remember. Its state is read from the catalogue.
Kratos (identity)not deployed
Holds people's identities, their passkeys and security keys, and their sessions, behind self-service registration, login, verification and recovery. No sign-in is wired to it yet
This environment runs no identity server: sign-in is Dynamic alone.
- state
- not deployed
- shipped by
- this repository: kratos/ publishes the image, and infra/ovh pins it and runs it on the data server where kratos_host is set
Never probed, so there is nothing to remember. Its state is read from the catalogue.
TrueForge (per organization)not deployed
One instance per organization, reached only by the Harness
This environment runs no TrueForge behind a Harness. /chat's TrueForge is the web row of that name.
- state
- not deployed
- shipped by
- infra/ovh, with the Harness: one TrueForge, Postgres database and Redis per organization, on the TrueForge pin in trueforge/VERSION
- depends on
- TAG Harness
Never probed, so there is nothing to remember. Its state is read from the catalogue.
Aletia MCPnot deployed
The Aletia connector for AI clients, on the MCP host
Defined and not applied in this environment: /mcp is a route nobody has applied (docs/mcp-public-path.md), so there is no connector URL to probe. The handler itself answers under Origin's prefix.
- state
- not deployed
- shipped by
- the app behind Origin's address (aletia, which replaced tag-mvp-ux), routed by infra/ovh where mcp_host is set
- depends on
- Origin (the TAG app)
Never probed, so there is nothing to remember. Its state is read from the catalogue.
TAG Back Office MCPnot deployed
The TAG Back Office connector for AI clients, on the MCP host at /tag
This environment runs no TAG Back Office, so it has no MCP of its own.
- state
- not deployed
- shipped by
- tag-backoffice, on its own merge; routed by infra/ovh where mcp_host is set
Never probed, so there is nothing to remember. Its state is read from the catalogue.