Feith enforces federal records compliance on the record itself, from capture through disposition. Zero Trust aligned, FedRAMP authorized, and DISA-JITC tested from 2002 to 2023 under the now-retired DoD 5015.02 program.
Other systems enforce compliance at the folder or the perimeter. Feith enforces it on each record: six controls that travel with the record and resolve at query time, not at the directory.
CUI, PII, and classification markings applied automatically on capture.
Native classification markings (U//FOUO, CUI, SECRET, and the rest) plus custom agency taxonomies, rule- and ML-driven.
Schedule-driven retention, with disposition locked to the schedule.
Records can’t be deleted outside the schedule. Holds suspend disposition without altering the schedule itself.
Pattern-based and ML-assisted PII identification across every record type.
Configurable taxonomies for agency-specific PII, CUI categories, and sensitive program data. Keyword alerts flag sensitive communications.
Classification, nationality, and supplemental markings enforced at the record level.
Clearance and caveats travel with the record. ABAC evaluates user attributes against record markings at query time, and a user’s clearance filters results without revealing that inaccessible records exist.
Directory-integrated roles with attribute filters on every query.
Access lives at the record level, resolved on every query. RBAC and ABAC combine; CAC, PIV, PKI, MFA, and biometrics are all supported.
Automated redaction with reviewer accept/reject and FOIA exemption coding.
Every redaction decision, including AI suggestions the reviewer rejected, lands in the audit log.
Admins assign users to roles in the directory; roles are cumulative, so a higher clearance inherits every lower tier. ABAC filters each query at run time, so access resolves at the record level.
| Role / group | Unclassified | CUI | Secret |
|---|---|---|---|
| Resource Mgt Unclassified only | ✓ | – | – |
| Resource Mgt · CUI CUI + Unclassified | ✓ | ✓ | – |
| Resource Mgt · Secret Secret + CUI + Unclassified | ✓ | ✓ | ✓ |
From the Federal Records Act to FRCP eDiscovery, the same platform satisfies the capabilities each regime demands. A capability is listed only where Feith demonstrably satisfies it.
| Framework | Capture | Classify | Retention | Access | Audit | Search | Redaction |
|---|---|---|---|---|---|---|---|
| Federal Records Act 44 U.S.C. Ch. 31 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | – |
| NARA UERM OMB M-23-07 · M-19-21 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | – |
| DoDM 8180.01 · DoD 5015.02-STD DoD records | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FOIA 5 U.S.C. § 552 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Privacy Act 5 U.S.C. § 552a | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Section 508 Accessibility | – | – | – | ✓ | – | ✓ | ✓ |
| CUI handling 32 CFR 2002 · NIST 800-171 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FRCP (eDiscovery) Federal Rules | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Feith demonstrably satisfies the capability the regime requires. not applicable to that regime.
Every action against every record becomes an append-only event — attributed to an actor, cryptographically ordered, and tamper-evident.
append-only · hash digests with regular fixity checks · forwarded to the agency SIEM
No anonymous events. Destruction and accession additionally carry the approving official and the authority the action was taken under.
Every stage of a record’s life writes to the same append-only log. The trail is the proof.
Every record carries a secure hash digest generated at ingestion. Any alteration changes the digest, so a change is mathematically detectable, not silent.
Every capture, classification, access, modification, hold, and disposition is logged with the actor that triggered it. Service accounts, system actions, and human users each carry a distinct identity through the chain. No anonymous events.
The audit log is append-only: events are added, never edited or deleted in place. A correction is a new event that references what it supersedes, so the original record of what happened is never overwritten.
Holds attach to records, queries, custodians, or schedules. Suspended dispositions stay suspended until the hold is released, and releases are documented. FRCP obligations are met without forensic recovery.
When a record reaches the end of its schedule, the disposition (transfer to NARA, deletion, or accession) is documented with the same rigor as any other event. The custody record travels with the transfer.
One identity layer authorizes every path in. One encrypted, single-tenant vault holds the records. One append-only audit layer records everything, with operations watching the floor.
M365 · ServiceNow · FOIA.gov · Pay.gov · files · databases · paper
Encrypted records store
Watches every path to the vault: continuous monitoring, anomalous-access alerts, and integration with your 24/7 SOC.
Data sovereignty isn’t a setting. It’s the architecture. AI runs inside your boundary, against records that never leave it.
The model comes to the records. Nothing crosses the perimeter.
AI orchestration runs inside the deployment. Cloud, on-prem, or air-gapped, the model talks to records that already sit behind your accreditation, not across an external API.
Vendor-agnostic across cloud and on-premises foundation models. Azure OpenAI and open-weight models are supported, and your records never enter a vendor training corpus.
Every AI-assisted action is logged with the model reference, input, output, and the reviewer’s accept-or-reject decision. Audit-grade AI: explainable, reversible, accountable.
The credentials a federal records officer screenshots before sending the meeting invite. Each plate names the specific posture the authorization actually grants: authorized, certified, validated, aligned, or ready.
Cloud, on-premises, and classified air-gapped deployments all share one Records API, one compliance posture, and one audit log. Bit-for-bit identical, no degraded mode.
Civilian agencies that want managed services and rapid deployment.
Agencies with data-sovereignty requirements or legacy integration constraints.
Defense and intelligence missions that require air-gap operation.
Non-classified IP Router Network. DoD unclassified operations.
Secret IP Router Network. DoD Secret-level operations.
Joint Worldwide Intelligence Communications System. TS/SCI operations.
Government cloud environments at higher classification levels.
The platform runs identically inside the air gap (see deployment models above). What a classified mission adds is the surrounding apparatus: a cleared facility, cleared people, cross-domain review, and secure reading rooms.
The boundary model is the same one drawn under AI compliance — the vault, suggest-mode orchestration, and a foundation model, all inside your accreditation. A classified deployment changes just two things:
Everything else — encryption, audit log, retention, customer-managed keys — is bit-for-bit the deployment shown above. Outside the boundary: no external connectivity, no exfil path.
Feith holds a Facility Security Clearance. Sensitive workloads can be hosted in Feith-cleared environments where a customer’s accreditation requires it.
63% of Feith staff hold a Secret or higher clearance; 49% hold SCI. Every administrator of a sensitive federal system is a US resident with an active TS/SCI clearance. Program leadership includes retired senior Intelligence and Special Operations personnel.
The integrated Declassification Review module supports cross-domain workflows (Automatic (ADR), Mandatory (MDR), and Systematic (SDR) review) in compliance with Executive Order 13526.
Interagency consultation happens inside the classified boundary. Multiple cleared agencies coordinate over the same records without removing them from controlled environments.
US-only, FOCI-clean, and FAR-compliant today, hardened in partnership with the US Intelligence Community and DoD.
Support, development, services, and engineering performed exclusively within the United States.
No non-US proprietary code or tools in development or continuous monitoring of the platform.
Free of foreign ownership, control, or influence. Facility Security Clearance maintained.
No engagement with Forced Technology Transfer countries. No Covered Equipment in the platform stack.
Fully compliant with Federal Acquisition Regulation 52.204-24 and 52.204-26.
Across three tiers: named civilian agencies, the Department of Defense, and the Intelligence Community.
Named civilian customers, including:
Plus cabinet-level departments, independent agencies, and additional civilian customers.
DoD components and Joint / Combatant Commands, deployed across:
US Intelligence Community customers, deployed across:
Schedule an architecture review with a Feith security engineer. Bring your framework; we’ll map it.
We'll reach out shortly to schedule your architecture review.
