HoundShieldHoundShield
Products by industry

One firewall · Every compliance framework · One deployment

🔒
Technology
SOC 2 · AI Governance

Engineers pasting API keys and source into Copilot and ChatGPT.

❤
Healthcare
HIPAA · 45 CFR 164

Clinicians pasting patient records into AI for documentation.

⛨
Defense
CMMC L2 · NIST 800-171

DoD contractors leaking CUI into AI proposal tools.

💼
Legal & Finance
SOC 2 · PCI DSS

Lawyers and analysts sharing privileged data with AI.

🌐
Five Eyes / Global
DISP · ASD Essential 8

International suppliers navigating AUKUS and allied frameworks.

🏛
Government
FedRAMP · FISMA

Agencies adopting AI without a compliant data framework.

SOC 2 · HIPAA · CMMC L2 · 16 engines · <10msStart free — all frameworks →
How it worksPricingDocsBlog
14,363 interceptedSign inStart free

Five Eyes / Global · DISP · ASD Essential Eight

Allied data should never leave allied soil. Keep it local.

International defence and government suppliers navigating AUKUS, DISP and allied frameworks can't route classified-adjacent data through a US cloud. HoundShield runs entirely on your own infrastructure, in your own country, so caveated and export-controlled data is detected and contained on-prem.

Start freeSee pricing

What it is

A sovereign, local-only AI firewall you host yourself — no data crosses a border or hits a vendor cloud.

Who it's for

Defence primes and suppliers across AU, UK, CA and NZ working to DISP and Essential Eight.

How you use it

Deploy on-prem or air-gapped; caveated markings and export-control terms are caught before AI use.

What it detects for you

AUSTEO / REL caveatsProtective markingsITAR / export-controlNational security dataPersonnel PIIProgramme codewordsTechnical dataSupplier IP

How it works

  1. 01

    Deploy on your own infrastructure

    Run HoundShield on-prem or air-gapped, inside your own country's boundary.

  2. 02

    Caveated data is contained locally

    Protective markings and export-control terms are detected before any prompt reaches a model.

  3. 03

    Evidence for accreditation

    Signed audit logs support your authority to operate — and HoundShield never phones home.

How HoundShield supports allied frameworks

Control / requirementHow HoundShield maps to itStatus
DISP — Data securityData stays on your sovereign infrastructureEnforced
ASD Essential EightEgress control on every AI interactionEnforced
Export control (ITAR / EAR)Controlled terms & caveats detected pre-modelEnforced
Accreditation auditSigned logs for your authority to operateLogged

Common questions

Where does our data physically go?+

Nowhere outside your environment. Deploy on-prem or air-gapped; HoundShield never phones home — to us or anyone.

Does it work offline / air-gapped?+

Yes. Detection is fully local; only the AI provider you choose needs outbound connectivity.

Can it detect our national caveats and codewords?+

Yes. Detection patterns extend to AUSTEO/REL caveats, protective markings and programme codewords on top of the standard 16 engines.

Who hosts it?+

You do. There is no HoundShield cloud in the data path — sovereignty is a property of the architecture, not a contractual promise.

Sovereign by architecture

The only AI compliance firewall that never phones home — to anyone.

Book a sovereign deployment
HoundShieldHoundShield

Local-only AI compliance firewall for CMMC Level 2, HIPAA, and SOC 2. Prompt content never leaves your network.

CMMC LVL 2HIPAASOC 2NIST 800-171

Product

  • Features
  • How it works
  • Pricing
  • Changelog
  • Roadmap

Compliance

  • CMMC Level 2
  • HIPAA
  • SOC 2
  • NIST 800-171
  • DFARS 7012

Resources

  • Documentation
  • Blog
  • Partners
  • Contact
  • About

© 2026 HoundShield. All rights reserved.

PrivacyTerms