Designed for on-premises and sovereign deployment. Smart-card. STIG-hardened. IPv6-native.
Federal agencies, DoD components, and defense industrial base contractors operate inside the strictest compliance perimeter on Earth. The Federal plan we are building is designed around STIG-hardened images, enforced FIPS 140-3 validated cryptography, smart-card (CAC/PIV) sign-in, and IPv6-native control + data planes for OMB M-21-07.
Not available yet. This page describes the Security Platform we are building; ACOG is the product you can use today.
Regulatory posture
The frameworks federal customers are audited against.
The federal stack is FedRAMP (Low / Moderate / High), DoD IL2-IL6 for cloud workloads, CMMC 2.0 (L1-L3) for the defense industrial base, ITAR for export-controlled material, CJIS for criminal-justice data, IRS Pub 1075 for federal tax information. The Security Platform is designed for the High / IL5 / L3 envelope; Tessarac holds none of these authorizations today, and pursuing them is on the roadmap, not in progress.
- FedRAMP High — roadmap; no sponsoring agency or assessor is engaged yet
- DoD IL5 — roadmap; it would follow a FedRAMP High authorization
- CMMC 2.0 L2 / L3 — roadmap
- ITAR — designed so export-controlled material never leaves the customer's compliance boundary
- CJIS + IRS Pub 1075 — designed for on-premises deployment inside the customer's boundary
- OMB M-21-07 — IPv6-native control plane and data plane; AAAA records published; cordon rules emit dual-stack
The federal-shaped deployment
Designed around STIG-hardened images, enforced FIPS-validated cryptography, smart-card sign-in for every operator account, and a deployment shape that runs fully on-premises.
-
Smart-card (CAC/PIV) sign-in
Embedded DoD/FCPCA trust bundle, OCSP + CRL revocation checking, PIN-protected reader integration. Planned to be required by default on the Federal plan and available on every paid plan. Operator-only (workforce) plus end-user options.
-
STIG-hardened images, FIPS-validated crypto
The Federal plan is designed to ship STIG-hardened base images audited against the latest DISA STIG, with FIPS 140-3 validated cryptography enforced across every component — no opt-out, no operator misconfiguration window.
-
Sovereign US-only environment or fully on-premises
Designed to run fully on-premises in your air-gapped environment with no outbound connectivity required, or in a US-only hosted environment once one exists. Neither is available today.
-
Tamper-evident audit + log shipping
Hash-chained audit log; export to your existing SIEM, your own object-storage bucket inside the sovereign boundary, syslog, or a Linux host. Customer opt-out of Tessarac retention entirely — sovereign deployments are designed to keep nothing outside the boundary.
Why a sovereign-deployable platform matters
The vendor risk model is different inside the boundary.
In commercial SaaS, you trust your vendor. In federal SaaS, you assume your vendor will be subpoenaed, attacked, and audited — sometimes all in the same week. Tessarac is built so the customer holds the keys, the customer can opt out of vendor retention, and the customer will be able to run the same product fully offline if the operational risk math says so.
- Per-tenant ECDSA P-384 trust anchor with HSM / cloud-KMS / BYOK options — operator key path is independent of Tessarac
- Customer opt-out of Tessarac retention entirely — sovereign deployments are designed to keep nothing outside the boundary
- Air-gapped install — planned for the Federal plan as an offline bundle, with no outbound connectivity required during install or operation
- Out-of-band cordon — even if the agent is compromised, isolation works via the cloud control plane
- Designed to collect compliance evidence continuously, so audit day is not a fire drill
Talk to a Tessarac federal architect
The Federal plan is not available yet. Talk to us to help shape it.