AI governance your regulator will recognise

End-to-end AI governance designed for regulated environments, with full auditability and policy enforcement built in.

Shadow AI is already inside your perimeter

Engineers don't wait for procurement to approve a new model. They use their personal API keys, bypass the approved stack, and start sending production data to unapproved providers. By the time your CISO finds out, there's a live workload processing customer PII on a model your risk team has never reviewed. In APRA-regulated environments, that's not a policy violation - it's a reportable incident.

Unapproved models are already processing production data in most enterprises

API key proliferation means any engineer can stand up a new AI workload in minutes. Without an enforcement layer, your approved-model list is a wishlist, not a control.

PII leakage through AI prompts is the compliance risk no one is measuring

Customer names, tax file numbers, and Medicare numbers flow through AI prompts daily - often without scanning, logging, or consent validation. APRA's CPS 234 and the Privacy Act 1988 require documented controls.

Audit evidence must be produced on demand - and almost no one has it

When a regulator asks for evidence of your AI governance controls, 'we have a policy document' is not an answer. Immutable logs, role-based access records, and model usage evidence are what regulators expect.

Approved-model enforcement and governance policies

SAVI enforces governance policies at the model access layer - not just in the dashboard. Each policy defines which models are approved, which are restricted, and what happens when a boundary is crossed: alert the team, or block the request outright. New models require a documented policy update before they can receive production traffic. Shadow AI is caught at the perimeter, not in a post-incident review.

  • Approved and restricted model lists configurable per team and department - violations are logged immediately
  • Policy mode per workload: alert (log and continue) or block (reject and notify) - no silent pass-through
  • Risk-tier classification on every model - low, medium, and high - so enforcement scales with sensitivity
roleallowedModelsapproval
ML EngineerClaude Sonnet 4GPT-4o-miniGemini FlashSelf-serve (low risk)
Senior ML Engineer+ Claude Opus 4GPT-4oLlama 3.1 70BTeam Lead approval
Compliance AI LeadClaude Opus 4GPT-4o (read-only audit)CISO approval
Data ScientistBedrock TitanGemini 1.5 FlashCohere Command RSelf-serve (low risk)
Contractor / ExternalSandboxed environment only - no production accessCISO + legal approval

Swipe to see all columns →

Governance Policy · Production Environment · Role-based model access

TFN detected in prompt
invoice-processor
critical
Medicare number in prompt
patient-records-query
critical
Email address in prompt
customer-support-bot
warning
Name + phone number in prompt
hr-assistant
warning

PII Scan Events · Last 24 hours · 4 events · 2 critical · 2 monitored

PII scanning on every prompt before transmission

SAVI's PII scanner runs on every prompt inside the SDK - before any data leaves your environment. Sensitive entities are detected and masked client-side, so raw PII never reaches SAVI's servers or your AI provider. Detected PII can be redacted, flagged, or used to block the request entirely based on configurable policy. Every detection event is logged with the entity type and action taken.

  • Australian-specific PII detection - TFN, ABN, Medicare number, and Australian phone number patterns included alongside names and email addresses
  • Configurable policy per workload: redact silently, alert FinOps, or block the request entirely
  • Detection events logged with entity type and action for Privacy Act 1988 compliance evidence

Immutable audit logs for regulatory readiness

Every AI interaction in SAVI's perimeter generates an immutable audit log entry - model used, team, prompt fingerprint, PII scan result, and cost. Logs are stored with WORM (Write Once, Read Many) protection, making them tamper-evident and admissible as governance evidence. When regulators or internal audit ask for evidence of your AI governance controls, SAVI produces a structured export in minutes, not weeks.

  • WORM-protected log entries - once written, they cannot be modified or deleted before the retention period expires
  • 13+ months default retention - configurable to meet your organisation's compliance obligations
  • JSON export via API - structured for compliance reporting and direct regulatory submission
Log retention
13+ months (WORM)
Configurable to support regulatory and internal compliance requirements
Tamper protection
WORM immutability
Write Once, Read Many storage - log entries cannot be modified after creation
Export format
JSON API
Structured compliance export accessible via API - ready for regulatory submission
Access control
Role-based log access
CRO sees risk summary; compliance team sees full trace; engineers see own requests only
Regulatory alignment
Compliance-aligned control framework
A governance-mapped control framework with complete auditability available on demand

Audit Log Controls · Compliance Evidence Pack · Last exported: 1 Jun 2026

1
Deploy in your environment
SAVI deploys entirely within your cloud perimeter. Your prompts, logs, and audit data never leave your network. Environment assessed against applicable hosting and security requirements before go-live.
2
Connect without rebuilding
A single initialisation change is all your engineering team needs. No architectural redesign, no new infrastructure to manage. Existing AI provider calls route through SAVI automatically.
3
Configure your policies
Model access rules, PII scan policies, and budget caps configured in the admin console. Your compliance team reviews and signs off before production traffic is switched over.
4
Compliance evidence from day one
Immutable audit logs start generating from the first production request. Retention configured per your compliance obligations. Test export reviewed by your compliance team before go-live.
5
Go live with confidence
Production traffic switches to SAVI. Full governance, FinOps visibility, and compliance evidence from the very first request.

Private Deployment · Timeline scoped with your team during onboarding

Private deployment for critical infrastructure

For APRA-regulated entities and critical infrastructure operators, SAVI can deploy entirely within your own environment - your prompts, responses, and audit logs never cross your perimeter. Every governance control available in the cloud runs identically on-premises. Your data sovereignty obligations are met without sacrificing a single governance capability.

  • Full feature parity - every governance control, PII scan policy, and audit log works identically in your private deployment
  • Deploys into your existing cloud environment or private data centre - your data never leaves your network
  • Complete operational isolation - SAVI's team has no access to your prompts, responses, or audit data
1
Observability in your existing tools
Point SAVI at your preferred observability platform from the Governance Console. Every AI call - cost, carbon, anomaly score - appears there automatically. No code change required.
2
Your key, your data
Each enterprise customer receives a dedicated encryption key at onboarding. SAVI's team cannot access anything encrypted with it - your data is yours, always.
3
Instant, provable deletion
When you offboard or request deletion, your key is removed. Everything SAVI holds becomes permanently unrecoverable - immediately, and with documented proof.

Governance Console · Observability + Data Control

Works with your tools. Your data stays yours.

SAVI surfaces every AI interaction in the observability dashboards your team already uses - cost, carbon, and anomaly signals alongside your existing infrastructure metrics, automatically. No additional tooling to adopt, no new dashboards to build. And when it comes to your data: every enterprise customer holds their own encryption key. SAVI cannot read your data - not your prompts, not your audit logs, not your agent traces. When your contract ends or you request deletion, your key is deleted. Everything encrypted with it becomes permanently and instantly unrecoverable. Provable to your DPO the same day.

  • Connects to the observability tools your team already uses - AI cost and governance signals appear in your existing dashboards automatically
  • You hold your own encryption key - SAVI cannot access your data, and never could
  • Data deletion is instant and provable - no manual sweep, no waiting period, no exceptions

Governance

Could you produce an AI audit trail tomorrow?

7 questions. Answer honestly.

Can you produce a complete list of every AI model that processed production data in the last 90 days?

Do you have documented evidence of which employees have access to which AI models - and who approved it?

Can you prove that every prompt containing customer PII was either scanned, redacted, or explicitly approved?

If a regulator asked for your AI audit log tomorrow, could you export it in a structured format within 24 hours?

Do you know which AI workloads are operating outside your approved model list right now?

Could you demonstrate to your board that your AI governance controls meet Australia's National AI Plan obligations?

If a customer contract ended today, could you prove their data was deleted - completely and immediately - without a manual database sweep?

This checks one slice of your AI estate. Take the full AI Cost Ownership Assessment →

Govern AI before it governs you.

SAVI enforces approved-model policies, scans every prompt for PII, and produces regulator-ready audit logs - with private VPC deployment scoped for organisations that need it. Book a compliance review call today.