Welcome, Christian

Choose a console.

Each console is an isolated Meridian workspace bound to one detection source. The demo console below runs against a live pipeline — no mock data.

7,810 artifacts·3 investigations·7,336 writes / 24h

Reference workspaceconsole-id: demo

Meridian Demo Console

A fully wired incident-intelligence workspace running against a live MongoDB Atlas cluster fed by Splunk Enterprise. Five incident archetypes seeded; the Gemini-3 reasoning agent has investigated them end-to-end.

Enter console

Artifacts

7,810

ContextSync URIs

Investigations

in agent_memory

Writes / 24h

7,336

provenance log

Storage

60 / 512 MB

Atlas M0 budget

How it works

Click any card to read the section in the methodology paper.Full white paper →

03Architecture

Five layers — integration, protocol, persistence, compute, surface — each decoupled from the others.

04ContextSync Protocol

Versioned, content-addressed artifacts with default-deny ACLs and immutable provenance.

05USC

Seven-field spatiotemporal coordinate. Cross-tier match formula links events across noisy sources.

06Agent loop

Seven-step investigate() procedure plus agentic-loop meta-tools for free-form questions.

Add a console

Roadmap — additional detection sources Meridian will support in production.

SplunkComing soon

Connect Splunk Cloud

Stream detections and saved searches from your tenant. Inherits ContextSync versioning automatically.

SentinelComing soon

Connect Microsoft Sentinel

Ingest analytic rule fires, incident records, and entity behavior from a Log Analytics workspace.

Org-wideComing soon

Production console

Promote the agent against your live SOC. RBAC, audit export, and SOC2-grade retention.