A look at the features and infrastructure work we shipped in the first half of 2026 — from transparent proxy support and tool call audit logs to hardened auth and production reliability improvements.
We crossed a meaningful milestone this year: SignalVault went from a narrowly focused audit logging API to a full trust layer you can drop in front of any OpenAI or Anthropic client with a one-line URL change. Here's what we shipped in H1 2026 and why each piece matters.
The original integration path required the SignalVault SDK — you had to import a library, wrap your API calls, and send events explicitly. It worked, but it added friction, especially for teams who didn't own the model-calling code directly.
The proxy changes that. Point your existing client at SignalVault's endpoint, pass your provider API key as usual, and we forward the request upstream while capturing a full audit record. No SDK required. Guardrail rules apply in-path, which means block and redact actions actually prevent bad requests from reaching OpenAI or Anthropic — not just log them after the fact.
Streaming works end-to-end for both providers. Chunks forward in real-time; the audit record is written once the stream completes.
Audit logging tells you what happened. Guardrails let you define what shouldn't. We added four new rule types in March:
When an application uses function calling or tool use, the AI's decision to call a tool — and the result it gets back — is at least as important as the original prompt and completion. We shipped complete tool call capture in two stages.
First, streaming tool calls (v0.10.0): tool names, inputs, and outputs captured in real-time as chunks arrive. Second, non-streaming tool calls (v0.11.0): the same coverage for the batch response path, including Anthropic's structured content blocks — text, tool_use, and tool_result each evaluated independently.
PII and secret detection extend to tool inputs and outputs. The JSON path of any flagged field surfaces in the violation record so you can trace exactly where the sensitive data appeared.
Going into public availability, we added Cloudflare Turnstile bot protection and disposable-email blocking on sign-up, email verification before dashboard access, and per-app API key management with revocation.
Later we tightened app-level access scoping in the dashboard — every app load now verifies account ownership explicitly, removing a class of potential insecure direct object reference issues.
Q3 is the reliability and growth phase. The infrastructure is stable enough that we're focused on making SignalVault easier to adopt, faster to debug, and more useful for the compliance workflows it was designed to support.
If you're evaluating SignalVault or have questions about a specific integration, reach out — we respond to everything.
AI Audit Logging in the Agent Era
Six months ago, logging LLM calls was enough. Now agents invoke tools, chain actions, and operate autonomously - and most audit logs miss the events that matter. Here's what the next version looks like.
The Complete Guide to AI Audit Logging
Learn what AI audit logging is, what to log, encryption requirements, retention policies, and how audit logs enable SOC2/GDPR compliance.
How to Make Your AI Application SOC2 Compliant
A practical guide to SOC2 compliance for AI and LLM applications—controls, audit gaps, and how to build a compliance-ready AI stack.
Get started with SignalVault in under 5 minutes.