Data residency — regions, backups, encryption

All FedGrade workspace data is stored and processed in the United States. Data is encrypted at rest and in transit. FIPS 140-3 validated cryptography, AWS GovCloud residency, customer-managed keys, and client-side envelope encryption are Government-/Enterprise-tier options on the delivery roadmap — they are scoped per agency during onboarding and are not live capabilities today. Where an item below is on the roadmap it is labeled as such; treat any capability not labeled "today" as not yet shipped.

Hosting & regions (today)

FedGrade runs on managed US cloud infrastructure:

All persistent workspace data lives within US regions of these providers. Multi-region and AWS GovCloud residency for Government-tier workspaces are on the roadmap, scoped per agency during onboarding.

Encryption at rest (today)

All persistent storage — the Postgres database, object storage, and the archive — is encrypted at rest with AES-256 by the underlying platform providers, using provider-managed keys. This is platform-level encryption at rest; it protects data on disk.

Roadmap (not live today): customer-managed keys (BYOK), a per-workspace client-side envelope on stored objects, and FIPS 140-3 validated key management for Government-tier GovCloud deployments. These are scoped and delivered jointly with the customer during onboarding.

Encryption in transit (today)

All client and service traffic is encrypted in transit with TLS (TLS 1.2+; TLS 1.3 where the client supports it). Roadmap: mutual TLS on Enterprise+ ingress and FIPS 140-3 cipher enforcement for Government-tier FIPS-mode deployments.

Backups

• Postgres: automated daily backups with 7-day retention, taken and held by the database platform (Supabase Pro plan). Point-in-time recovery is a separately paid add-on that FedGrade has not purchased, so the recovery granularity is one day, not one second.
• Object storage: durable, replicated storage provided by the storage platform.
• Search index / embeddings: derived from Postgres and rebuilt on restore; not separately backed up.

What that means in practice: the worst case for a database-level failure is the loss of up to 24 hours of writes, and the oldest restorable point is 7 days ago. Backups are held by the database platform in the same US region as the primary; there is no cross-region backup replication today.

Backup and restore procedures follow the managed platform's guarantees (Supabase — Database Backups, accessed 2026-08-04). A documented restore drill and restore report for Enterprise+ workspaces is on the roadmap.

Sub-processors

FedGrade uses the following sub-processors, each receiving only the minimum data needed for its function and only over encrypted connections:

The AI sub-processors (Anthropic, Voyage, Cohere) are processors, not stores, and are used under their respective enterprise/zero-retention terms where available. A canonical, versioned sub-processor list with DPA references is published for Enterprise+ workspaces on request.

Roadmap (not live today): for Government-tier GovCloud deployments, AI-provider routing that terminates inside the GovCloud boundary is scoped per agency during onboarding.

Customer key management (roadmap)

Customer-managed keys (BYOK) and the associated "kill switch" offboarding pattern — where revoking the key renders workspace data unreadable to FedGrade — are on the Enterprise+/Government roadmap, not a live capability today. They are scoped during onboarding.

---

This page describes FedGrade's current managed-cloud architecture and its roadmap items as of the "updated" date above. For a security review package (current posture, sub-processor list with DPAs, and roadmap commitments in writing), contact sales.