For the complete documentation index, see llms.txt. This page is also available as Markdown.

Status and operations

  • Status page: status.dictum.glbnxt.tech, public. Two monitors: the MCP endpoint every minute, and a deep health check every five minutes that looks at the age of every source's nightly update, failed jobs, search latency, the model hub, the nightly quality run, the last backup and the disk.

  • Uptime target: 99.5 % per month on the MCP endpoint outside announced maintenance, to be confirmed after the first month of measurements.

  • Updates: nightly, per source, around 03:00–07:00 Amsterdam time. A ruling published on rechtspraak.nl is searchable the next morning.

  • Where it runs: one server at netcup (EU), under Coolify, with GLBNXT's model hub for embeddings and reranking. Nightly database backups with a verified restore; off-site copies are on the roadmap.

  • Incidents and changes: the changelog in the repository (CHANGELOG.md) lists every release; the status page carries incidents.

Data handling

Queries are logged with the calling key or user, the tool, the query text, the latency and the identifiers returned, for usage reporting and quality work. Ruling and law texts are public; the queries are not and stay on GLBNXT's infrastructure.

Trust, terms and agreements

DICTUM is an integral part of the GLBNXT platform. It is covered by the GLBNXT Trust Center and falls under GLBNXT's Terms and Conditions, Data Processing Agreement and Service Level Agreement, published on glbnxt.com/legal. A DICTUM-specific list of sub-processors follows (roadmap P1.2b); today they are netcup (hosting, EU), GLBNXT's own model hub and GLBNXT's Zitadel login.

Was this helpful?