FILTARInspect
Analyse prompts, responses, links and files before they reach the model.
SIGNALS COLLECTEDONE PROTECTION FLOWFOUR LAYERS
Inspect. Understand.
Enforce. Prove.
FILTAR analyses AI interactions and returns structured results your application can enforce and record. Every layer remains visible to developers and security teams.
01 INSPECT — signals collected02 UNDERSTAND — context interpreted03 ENFORCE — policy applied04 PROVE — decision recorded
TRACE COMPLETEDECISION EXPLAINABLE ✓
THE DECISION PIPELINE
From interaction to action.
Each layer has a specific role. Together, they create one consistent protection path.
Understand
Interpret language, intent and business context beyond generic keywords.
CONTEXT IDENTIFIEDEnforce
Allow, block, redact, warn or route the interaction according to policy.
POLICY APPLIEDProve
Keep an explainable record of protection decisions for review and audit.
DECISION RECORDEDREAL PRODUCT EXPERIENCE
See the decision
before the risk spreads.
Explore two example executions captured in the FILTAR test interface. Timings shown are specific to these runs and are not general performance guarantees.
Inference is the model’s evaluation time. Request latency is the measured time for the wider request path, including processing overhead. Values below are individual example runs, not benchmark averages or performance guarantees.
INCOMING PROMPT
What are the key elements of an honest and transparent hedge fund performance report?
✓
FILTAR DECISIONSAFE
ALLOWEDNo threats were detected. This submission would be allowed through.
CONFIDENCE100%Example run
THREATS0 / 11Guardrails flagged
MODEL INFERENCE TIME0.01sExample run
REQUEST LATENCY0.15sMeasured request time
VISIBLE BY DESIGN
Security teams see why. Applications know what to do.
FILTAR returns a structured protection decision while preserving the context needed for review and audit.
{decision: "REDACT",reason: "SENSITIVE_DATA",context: "FINANCIAL_SERVICES",trace: "RECORDED"}
IMPLEMENTATION REFERENCESEE API DOCS ✓