EXPLORE BSL

The wider BSL universe.

Machaon is the main behavioral monitoring product. This page provides context on supporting modules, services and future development.

See what Machaon delivers

One universe. A clear path forward.

Machaon is the entry point to BSL behavioral monitoring. The roadmap distinguishes the core product, supporting layers and future development directions.

Machaon / V3

Core product path

Target-specific behavioral monitoring built around AI Probe, Pulse lite, Omission and Asymmetry, with a Behavioral Mesh that brings signals together for review.

Go to Machaon login

Machaon / V3.1

Product extension roadmap

Isolated monitoring targets, bounded scheduling and light diagnostic extensions. Availability depends on the deployed version and validated integrations.

Machaon / V3.2

Governance and review layer

Advisory evidence checks, recorded review decisions and human-review routing around completed monitoring results. Your team retains control of decisions and actions on its systems.

EARL / Level 2

Future monitoring direction

Stronger correlation across runs, richer incident context and customer-specific risk interpretation. Planned capabilities require further validation.

The Mantle / Level 3

Future operational security direction

Future research and development toward near-real-time monitoring, governed intervention and operational response.

Machaon provides evidence for review today. EARL and The Mantle describe future development directions.

Modules that support the BSL product surface.

BSL modules support evaluation, analysis, visualization and customer-facing review. The public website explains their role. The modules themselves belong behind controlled product surfaces.

Eval

Structured behavioral evaluation and reporting for teams reviewing AI system behavior against expected behavior.

Vortex

Behavioral signal analysis and visualization that helps your team inspect changes and understand the results.

The Model

A controlled public calling-card demo that shows how BSL turns model behavior into plain-language signals people can inspect.

Try The Model

Open The Model at the-model.behaviorlayer.eu. Explore a focused demonstration of behavioral signals. Provider credentials, when required, are entered through the demo’s dedicated interface.

Context for a better review.

These supporting layers remain separate from the four behavioral signals.

Semantic twins & style controls

Same task, different wording. Optional diagnostics explore whether results change under controlled paraphrasing or a different presentation style. They use bounded test tasks with additional usage consent. Your team can review the diagnostic findings alongside the original assessment.

Governance

Is the evidence sufficient? Is the baseline still relevant? Is human review needed? Advisory checks and recorded review decisions help teams trace the evidence behind an assessment. Your team gets a traceable basis for review, approval and compliance documentation, while keeping control of operational decisions.

See how this could fit your AI setup →

Expert-led behavioral AI security assessment.

BSL combines software modules with expert-led behavioral security assessment for organizations deploying high-impact AI systems.

Commercial scope depends on the customer's AI system, deployment context, modules, security requirements and review needs. We agree a proposal around that scope.

  • AI system behavioral risk assessment
  • Monitoring target definition
  • Baseline and module fit review
  • Governance and claim review
  • Deployment readiness review
  • Partner/customer technical briefing

Security starts with how data is handled.

BSL works around systems that may contain sensitive customer context. Prompts, logs, baselines, endpoints, configurations, API keys and security setup must be treated carefully.

Initial contact uses high-level business context. Technical access and data handling are agreed separately within the customer’s assessment scope.

  • Customer data and target configuration are sensitive.
  • API keys and secrets must never appear in code, logs or public artifacts.
  • Customer modules belong behind authentication.
  • Internal prompts, baselines and scoring logic stay within controlled product environments.
  • Customer environments require written scope and permission before testing.

Ethics as operating discipline.

BSL works with systems that affect trust, risk and responsibility. We communicate findings and confidence clearly, protect customer context and keep assessments traceable. Your team can review both the evidence and the basis for each conclusion.

We build defensive security around scoped assessments, controlled access and explicit permission for handling customer data.

Separate observation, probability and proof Explain uncertainty when it exists Protect customer data and secrets Build for defensive security Test with permission and scope