Status

Live system status

A real-time view of every part of Clerk — from the agent and jurisprudence search to document ingestion and collaboration. If anything is degraded, you'll see it here first.

All systems operational
Workspace & agentOperational
Jurisprudence searchOperational
Document ingestion (OCR)Operational
Document generationOperational
AuthenticationOperational
Realtime collaborationOperational
How status is reported

What each service covers

Status is reported per service, so you always know exactly which part of the workspace is affected.

Workspace & agent

The agentic workspace itself — reading the case file, running its tools and showing its reasoning at every step.

Jurisprudence search

Search across the full Luxembourg corpus of 45,957 decisions, with each citation linked to its public source.

Document ingestion (OCR)

Ingesting scanned judgments and contracts in French or German, OCRing every page and extracting facts, clauses and dates.

Document generation

Drafting mises en demeure, conclusions and plaidoiries, then exporting formatted .docx or PDF on the firm's own template.

Authentication

Sign-in, firm roles and the row-level access enforcement that gates every matter and document.

Realtime collaboration

Shared matters, real-time multi-user messages and document sharing across lead, contributor and observer roles.

Our approach

One signal per service, not all-or-nothing

We monitor each service independently and report its state here. When a service is degraded, this page is updated so you can see exactly what's affected and act accordingly — rather than guessing from a single overall light.

  • Every core service is tracked on its own, not as a single all-or-nothing signal
  • Each service reports operational or degraded so you know precisely what to expect
  • All monitored services run within EU data residency
6core services monitored independently, each with its own status

Where Clerk runs

EUdata residency for every service above
6core services monitored independently
Per-servicestatus, so you see exactly what's affected

Put a workspace you can rely on on the matter

Operational by default, transparent when it isn't.