HAOS — Briefing Deck
High Assurance Object Storage · Confidential Briefing

Governed storage
for the age of AI agents.

HAOS lets AI agents work with your most sensitive data — enforcing who sees what at the data itself, not the app. One governed copy, every interface your stack already speaks.

Clients & AI agents Open API surfaces S3·Iceberg·Vector·LLM·SQL Governance RBAC·ABAC·ACL·Labels Encrypted store EC shards · FIPS
HAOS Secure storage · built for AI · sovereign by default
The Problem

Your best data is also your most sensitive —
so you can't hand it to an AI.

Agents need real dataAn AI agent is only useful if it can reach the data that matters.
Rules live in the appAccess control sits in applications — not in the data itself.
All-or-nothing keysCopy the data out, or hand over a key, and control is lost.
control boundary — rules stop here Application holds the access rules Sensitive data ungoverned at rest rules enforced here only AI agent one key → sees EVERYTHING Exported copy no rules travel with it
The Solution

Put the rules inside the data.

Every request runs a four-layer gauntlet at the storage layer. Both role and attribute checks must pass, an explicit deny always wins, and restricted fields are redacted on the way out.

Request agent / user LAYER 1 RBAC role LAYER 2 ABAC attributes LAYER 3 ACL per-item LAYER 4 Label clearance→redact GOVERNED RESULT name rev SSN redacted both RBAC + ABAC must pass · an explicit deny always wins · enforced at the storage layer
How It Works

One governed copy. Checked on every request.
Every decision logged.

Caller person · app · agent HAOS gateway S3 / REST / … Policy engine RBAC·ABAC·ACL·Label Encrypted store EC shards Audit & policy stream every decision, in real time LOG return path — only the rows & columns the caller is cleared for
Why HAOS Is Different

One governed copy of the truth.
Many doors — every door governed the same.

GOVERNANCE · RBAC / ABAC / ACL / LABELS One governed copy Amazon S3 Iceberg Vector DB LLM chat Governed SQL REST + File
Governance travels with the dataCopy-proof, app-proof.
One copy, many interfacesNo second ungoverned copy to protect.
Purpose-built for AIAgents you can actually trust with data.
Sovereign & self-hostedYour hardware, your keys, air-gap capable.
How HAOS Compares

Storage, governance and AI —
in one product.

Capability HAOS Plain object storage
MinIO · S3		 App-layer governance
add-on tools
Governance enforced in the data (block level)✓○◐
One governed copy across many interfaces✓○○
Automatic row & column redaction✓○◐
Built for AI — vector-level ACLs✓○○
Confidential-compute AI inference✓○○
FIPS 140-3 + post-quantum crypto✓◐○
Sovereign · self-hosted · air-gap capable✓◐◐
Erasure coding + disk-to-client audit✓◐○

✓ built-in  ·  ◐ partial or bolt-on  ·  ○ not addressed

The Front Doors

The data speaks every language
your stack already uses.

Amazon S3objects · apps · backups · pipelines Apache Iceberganalytics tables · Trino / Spark Qdrant & Milvusvector search for AI / RAG OpenAI-compatiblegoverned LLM chat / inference Governed SQLFlightSQL over the data lake REST + File APInative app + administration GOVERNANCE + AUDIT identical RBAC · ABAC · ACL · labels for every surface One governed, encrypted copy erasure-coded · FIPS 140-3 · WORM
The Platform · Single Pane Of Glass

Enterprise-grade by construction —
from the disk to the client.

AUDIT & POLICY STREAM · SINGLE PANE OF GLASS Clients & AI agentspeople · applications · autonomous agents Open API surfacesS3 · Iceberg · Qdrant/Milvus · OpenAI · SQL · REST GovernanceRBAC · ABAC · ACL · sensitivity labels · auto-redaction EncryptionFIPS 140-3 · post-quantum (ML-KEM) · HSM-wrapped keys Data reductionentropy-aware compression + deduplication Storage engineerasure coding (Reed-Solomon shards) · WORM / Object Lock Disks & racksmulti-rack · rack-aware placement · automatic failover (HA/DR)
Governed AI · End To End

Everything AI touches stays governed.

Caller + clearance Vector search ACL filter at the vector level Governed context only permitted docs Confidential-compute LLM · hardware attestation verified Answer Governed SQL FlightSQL query Row + column redaction beneath every aggregate Governed result the same clearance is enforced at retrieval, at the model, and at query
HAOS · By The Numbers

The whole story, at a glance.

1
governed copy
one source of truth for every interface
6
open interfaces
S3 · Iceberg · vector · LLM · SQL · REST
4
checks per request
RBAC · ABAC · ACL · sensitivity label
100%
encrypted at rest
FIPS 140-3 · post-quantum ready
6 yr
tamper-proof audit
immutable, HIPAA-grade retention
10GB+
single-file streaming
resumable large-object uploads
0
data leaves your control
sovereign · self-hosted · air-gap
40%
of apps embed AI by 2026
Gartner — up from under 5%
The Market

HAOS sits where three big
markets collide.

Enterprise storage AI & agents Data governance HAOS
HAOS is the governed, AI-ready slice of storage — the MinIO for buyers who cannot compromise on control.
Target buyers · Defence · Government · Healthcare · Financial services · Critical infrastructure · Sovereign cloud
Who It's For

Built for buyers who can't compromise.

Defence & Intelligence

Clearance-aware AI

Analysts and AI agents query classified data at their clearance — never a row above it.

Government · Sovereign cloud

Data stays home

Citizen data lives on your own hardware, encrypted and audited end to end.

Healthcare

AI without HIPAA risk

PHI is usable by models with restricted fields redacted; six-year audit is built in.

Financial services

Models, minus the leakage

Customer records feed AI with SSNs and account numbers auto-redacted per user.

Critical infrastructure

Air-gapped & tamper-proof

Write-once storage for operational and incident data, fully isolated.

AI platform teams

Governed data for every pipeline

Give RAG and agents governed data — no ungoverned copies, no leaks.

The Opportunity

Large today. Growing fast.
Converging on HAOS.

2026 2030–34 $8B $34B Object storage ~17% CAGR $11B $50B AI agents ~45% CAGR $5B $15B Data governance ~20% CAGR
Gartner: 40% of enterprise applications will embed AI agents by the end of 2026 — up from under 5% a year earlier.
Blended industry estimates (MarketsandMarkets · Grand View · Fortune Business Insights · BCC · Gartner), rounded for briefing use.
Why Now

The AI wave is forcing the governance question.
HAOS answers it at the storage layer.

The organisations that can safely feed sensitive data to AI will move faster than everyone else. The ones that can't will stall — or breach. HAOS is how they do it safely: one governed copy, every interface, full audit, sovereign control.

The pitch in a lineSecure storage AI can be trusted with.
Why it winsRules in the data, not the app — copy-proof, disk-to-client audit.
Where it playsDefence, government, healthcare, finance — buyers who can't compromise.
Presenter only — the moat Do not put this on screen

Our secret sauce.

Everyone else secures an app, or a single interface. We put the security underneath everything — in the storage itself — and make the same rules work no matter how the data is reached: as files, as analytics tables, as an AI search index, or through an AI model.

One governed copy, enforced at the data, surfaced through every standard interface, at classified grade. That combination is the part competitors haven't put together.
It's architecture, not a featureCan't be bolted on afterwards — which is why incumbents can't just "add" it.
One set of rules, every doorwayRivals govern one surface; we govern the data, so every interface inherits it.
AI-native from day oneVector-level permissions, governed SQL, and models that only run on proven-secure hardware.
Classified-grade foundationsFIPS crypto, erasure coding, sovereign / air-gap — the hard engineering startups can't fake.
If asked "why can't AWS or MinIO just do this?" — "MinIO stores data; it doesn't govern it. Governance tools sit in the app, so the moment data moves they're gone. AWS sells you the parts, not one governed copy across all of them on your own sovereign hardware. HAOS is the only one that put the whole thing in one place, beneath the data."
Presenter — not for the room Memorise this

The 60-second version.

"Every company wants to put AI agents to work — but the data that would make those agents genuinely useful is also the data they can't afford to expose: customer records, financials, classified material. The problem is that today, access rules live in the applications, not the data — so the moment data moves, or an agent gets a key, control is lost.

HAOS fixes that by building the rules into the storage itself. It enforces who-can-see-what at the data — right down to individual rows and columns — and surfaces that one governed copy through every interface a modern stack uses: S3, analytics, vector search, even a governed AI chat gateway that only runs on proven-secure hardware. So an agent gets exactly the data it's cleared for and nothing else, with a full audit trail from the disk to the client. It's FIPS-grade encrypted and runs on your own hardware.

In short — HAOS is the secure, governed storage layer that lets organisations trust AI agents with their most sensitive data."

Maturity, if pressed: core storage, governance, S3, analytics and vector interfaces are built; hardening toward general availability. Say "built and being hardened," never "finished." FIPS module validation is in process — don't claim a finished certificate.

Presenter — sound technical Term → what to say

Parrot these with confidence.

RBAC / ABACAccess by role, plus by attributes. "Access follows your role — then attribute rules add conditions like clearance level, where you're connecting from, and the time of day."
ACLPer-item permissions. "Permissions right down to individual files and folders — like Windows file permissions, but enforced inside the storage."
Block-level controlEnforced at the data, not the app. "The access rules live in the storage layer itself — so they can't be bypassed by copying the data or swapping the application."
Erasure coding
(Reed-Solomon)		Failure-proof with less overhead. "We shard the data with erasure coding — it survives a whole rack failing, using far less space than making three full copies."
Redaction /
row-column governance		Hides what you're not cleared for. "If you're not cleared for a column, it comes back redacted — blacked out — automatically, at the moment of access."
Single pane of glassOne unified view. "One view of security and audit across every layer — from the physical disk to the client."
FIPS 140-3The US government crypto standard. "The encryption is FIPS 140-3 — the standard governments require. Every byte is encrypted at rest." (If pushed: validation is in process.)
Post-quantum
(ML-KEM)		Safe against quantum computers. "It's post-quantum ready — it stays secure even against future quantum attacks."
Apache IcebergOpen analytics tables. "The same data is queryable as analytics tables via Apache Iceberg — Trino, Spark, DuckDB."
Vector DB / RAGHow AI retrieves relevant data. "It speaks the vector-database protocols AI uses to retrieve information — Qdrant and Milvus — so RAG pipelines get governed data."
Vector-level
ACLs		Permissions baked into the AI search index. "The access rules go all the way into the vector index — so an AI search only ever returns results the user is cleared to see."
Confidential
computing		The AI runs on proven-secure hardware. "Sensitive prompts only run on confidential-compute GPUs — HAOS cryptographically checks the hardware is genuine and sealed before any classified data reaches the model."
Governed SQLQuery the data lake, safely. "Analysts run normal SQL, but each person only sees their permitted rows and columns — restricted fields are blanked out automatically, even inside totals and averages."
WORM /
Object Lock		Write once, can't be changed or deleted. "Records can be locked write-once for retention and legal hold — they can't be tampered with or deleted, which auditors require."
HAOS
01 / 13