Yes — on-prem inside your existing boundary. FedRAMP authorization is on the roadmap and not yet complete, so we're upfront about that.

Does anything leave our ATO boundary?

No. HoundShield runs inside your boundary and never sends data out.

Is HoundShield FedRAMP authorized?

Not yet. FedRAMP authorization and full FISMA control mapping are on the roadmap. The on-prem CUI/FOUO controls are available today.

Government · FedRAMP · FISMAComing soon

Agencies are adopting AI faster than they can govern it.

Public-sector teams want AI productivity without a compliant data-handling framework. HoundShield gives agencies an on-prem AI firewall that keeps CUI and citizen PII inside the boundary — FedRAMP and FISMA alignment is on the roadmap.

Join the waitlist See pricing

What it is

An on-prem AI gateway that enforces data-handling policy on every prompt inside an agency boundary.

Who it's for

Agency CIOs/CISOs and program offices piloting generative AI under FISMA.

How you use it

Deploy inside your ATO boundary; CUI and PII are detected and contained before any model call.

What it detects for you

CUI / FOUO

Citizen PII

SSN / records

Law-enforcement data

Procurement-sensitive

Geospatial / infra

Health (CMS)

Tax data

Deploy inside your ATO boundary

HoundShield runs on-prem, inside your existing authorization boundary.

CUI & citizen PII contained

Sensitive data is detected and held before any model call — nothing leaves the boundary.

Signed evidence for review

Tamper-evident logs of every prompt support audit and oversight.

Where the public-sector edition stands today

CUI / FOUO handling
Detected before the model — on-prem, available todayLive

Audit & accountability
Signed logs of every promptLive

FISMA control alignment
Mapping in progressRoadmap

FedRAMP authorization
Planned — not yet authorizedRoadmap

FAQ

Common questions

Be first in line for the public-sector edition

Join the waitlist and we'll bring you in as FISMA mapping and FedRAMP authorization land.

Join the waitlist