Gateway / Local-First Data Sovereignty
Egress: LOCAL - Always

Your data never
leaves your building.

Every AI inference runs on hardware inside your network. Prompts, responses, agent workflows; none of it reaches the internet. Not because of a policy setting. Because of where the model runs.

Sovereignty enforced by architecture. PHI, financial records, legal communications, and trade secrets stay on your side of the wall; and Gateway produces a complete audit trail proving it.

0
Bytes sent externally
100%
Inference runs on-premises
<300ms
Time to first token, local
The Problem

Cloud AI requires you to trust a third party with your data.

When you send a prompt to OpenAI, Anthropic, or Google that data physically leaves your network and enters their infrastructure. For general queries this is a trade-off. For PHI, financial records, legal communications, or internal trade secrets, it is a compliance failure.

Cloud AI - What you have today Data leaves network
Your Users
Your Agents
YOUR NETWORK BOUNDARY
prompt + your data
crosses boundary ⚠
Vendor Servers
OpenAI · Anthropic · Google
Your data is here
Data processed on vendor infrastructure
You trust their security and compliance
No guarantee data is not used for training
Audit trail, if any, controlled by vendor
Inferise Gateway - Safety filter Only safe data passes
Your Users
Your Agents
YOUR NETWORK BOUNDARY
Gateway - Safety Check
Policy · Classification · Log
✗ BLOCKED
unsafe data
✓ SAFE DATA
passes through
Vendor Servers
OpenAI · Anthropic · Google
Vendor Server Access: safe data only sent
Unsafe data is blocked before it reaches the model
Only safe, policy-approved data reaches local inference
All inference runs on your SAGA hardware - nothing external
Compliant by architecture, not configuration
Enforcement

Sovereignty enforced at every layer.

The local-first guarantee is not a policy checkbox. It is enforced by the routing architecture, the policy layer, and the physical hardware simultaneously.

Layer 1 - Architecture

Local inference by design

The Gateway routing engine has no path to an external model endpoint. Every inference request goes to the on-premises LLM inference engine component. There is no cloud route to misconfigure.

Routing table
request → ENGINE (local)
cloud_endpoints: none configured
Layer 2 - Policy

API-layer enforcement

Even if a future hybrid routing configuration is enabled, the policy engine evaluates every request before inference runs. Sensitive data tags (PHI, FINANCIAL, LEGAL, HR) are always forced to LOCAL regardless of routing preferences.

Policy override
IF data.sensitive THEN
route = LOCAL // always
Layer 3 - Hardware

Sealed system, no SSH

The SAGA appliance ships as a sealed system. No SSH access, no external management plane, chipset validation on every boot. There is no way to remotely reconfigure the system to exfiltrate data, because there is no remote access surface.

SAGA security posture
SSH: DISABLED
BOOT_VALIDATION: ACTIVE
EXTERNAL_MGMT: NONE
Routing Logic

Where every query goes.

Select a query type to see how Gateway routes it...

Query type
1
v1.0 - Shipping Now
LOCAL
query_type =
data_sensitivity =
cloud_endpoints = none
route = LOCAL // ENGINE on SAGA node
egress = LOCAL // bytes_external=0
SAGA Appliance

The physical embodiment of the sovereignty guarantee.

The strongest data sovereignty claim is hardware in your data center that you can physically point to. SAGA is a pre-configured, sealed appliance. It arrives ready to connect to your LAN. No setup, no cloud dependency, no external management plane.

SAGA Appliance - Specifications
IN PRODUCTION
form_factor 2U appliance, 1–4 ODIN nodes
node_platform M4 Mac Mini Pro · 64GB · 20 GPU cores
storage 8TB SSD - logs and data collection
network_access HTTPS only - no SSH, sealed
boot_validation chipset validation on every boot
external_deps none - fully air-gappable
ttft_per_node <300ms
concurrent_users 20 per node (usage-pattern dependent)
power 6W min / 140W max per node
Connect to LAN. Gateway is accessible immediately. No setup required.

Configuration can be changed.
Architecture cannot.

Cloud-based AI solutions may offer data residency agreements, privacy commitments, and enterprise terms. But those guarantees depend on the vendor honoring them and on your configuration remaining correct. A misconfigured setting, a vendor policy change, or a security breach can undermine them.

When the model runs on hardware in your data center, there is no vendor to trust, no agreement to enforce, and no configuration to misconfigure. The data cannot leave because there is nowhere for it to go.

Hardware in your data center
Sovereignty you can physically point to. SAGA appliances deploy to your LAN and never require an outbound management connection.
Complete audit trail, your possession
Every prompt, response, and agent step logged to your 8TB SSD. You retain the logs. You control the retention policy. No vendor holds your evidence.
Provably compliant from day one
Showing an auditor a sealed on-premises appliance with local logs is a different conversation than explaining a cloud vendor agreement.
Regulatory Coverage

What local-first means for each regulation.

Regulators have specific requirements around where data is processed, who can see it, and what evidence exists. Gateway satisfies each one architecturally.

HIPAA
SATISFIED

Protected Health Information

HIPAA requires PHI to remain under covered entity control and prohibits disclosure to unauthorized third parties. When inference runs locally, PHI never leaves the covered entity network... no BAA required with Inferise for local deployments.

PHI stays on covered entity hardware
Access logs satisfy audit control requirements
No third-party data processor in the loop
GDPR
SATISFIED

Data Residency & Processing

GDPR requires data controllers to implement appropriate technical measures and restrict transfers of personal data outside jurisdictions. Local inference eliminates cross-border transfer risk entirely since the data never moves.

No cross-border data transfer
Data subject rights enforceable locally
Customer controls retention policy
FISMA
SATISFIED

Federal Information Security

FISMA mandates that federal information systems implement comprehensive security controls and produce audit evidence. Gateway runs on-premises with full audit logging every access, every inference, every policy decision is logged locally.

System boundary entirely within agency control
Continuous monitoring via Prometheus export
Complete audit trail for ATO evidence package
SEC / SOX
SATISFIED

Financial & Securities Records

SEC and SOX require firms to maintain records of communications involving material non-public information and financial data. AI interactions involving financial data must be logged and controlled. Gateway logs every interaction and keeps financial data off external networks.

MNPI never routed to external AI service
Immutable audit log for all AI interactions
Access control per actor satisfies SOX IT controls
Now Accepting Enterprise Pilots

Your AI.
Your network.
Your rules.

The fastest path from zero to a fully auditable, locally-running AI infrastructure is a conversation.

Portal deployments start in minutes. SAGA hardware ships to your data center.