Platform

The layer that sits in front of the model.

TrustLayer is a gateway: every request passes the same five stages in the same order. None of them can be skipped from your application code.

Stages: 5
PII entity types: 8
Policy format: YAML
Audit targets: 3

Capabilities

Five layers, one gateway.

Each makes its own decision, and each writes that decision to the audit log.

01Data ShieldCatches national IDs, tax numbers, IBANs, card and contact data, and swaps them for format-valid synthetic values before the model sees them.

02Prompt ShieldScores jailbreak and injection attempts with a weighted scorer; anything over the threshold never reaches a model.

03Answer VerificationChecks RAG answers against their source document and flags unsupported claims.

04Access ControlKnowledge base permissions are role-based: a user never sees content from a document they are not entitled to; not even inside an answer.

05Audit & CostWho asked what, when, which rule fired and what it cost; written to an immutable record and exported to your SIEM.

Rule engine

A policy is a file, not a hidden model.

Your organisation's rules live as YAML. Change the switches and the file on the right is exactly what they produce; so policy goes into version control, gets reviewed, and can be rolled back.

Change the switches and the file updates live.

If the policy cannot be read

Answer verification

Entity rules

Turkish national ID

IBAN

Card number

policies/<tenant>.yml

blocked_keywords:
  - rüşvet ve yolsuzluk
  - garanti getiri

competitors:
  - RakipBank

pii_rules:
  TR_TCKN:
    enabled: true
    action: mask
  TR_IBAN:
    enabled: true
    action: block
  CARD_PAN:
    enabled: true
    action: mask

fail_mode: closed

Schema

Supported keys.

key	type
`blocked_keywords`	string[]	A request containing one of these is blocked before the model.
`competitors`	string[]	Not blocked but redacted; the name is removed and the request continues.
`pii_rules`	{ LABEL: { enabled, action } }	Per entity type: off, mask, or block.
`custom_rules`	rule[]	Organisation-specific patterns, marked mask or block.
`fail_mode`	"open" \| "closed"	If the policy cannot be read: let the request through, or stop it. The finance preset is closed.
`token_scope`	string	Lifetime of masking tokens; per request or across the session.
`hallucination_detection`	boolean	Enables the verification pass. Off by default; it is a second model call.

See it with your own data.

In a technical session we run your prompts and your policy through it live.

Book a demo Email the security team