Security & compliance
The posture below is generated from our compliance configuration
(deploy/config/compliance.yaml),
so it reflects what is actually in production rather than what reads
well. Launched 2026-06-01.
Baseline controls
In force from launch. Each control is a property of how the platform is built, not a commitment in a contract.
| Control | Status | Statement |
|---|---|---|
| gdpr | compliant | GDPR compliant by design. DSAR endpoints, sub-processor list, DPA, EU representative engaged within 30 days of first EU customer. Region: eu-central-1 model plane |
| popia | compliant | POPIA compliant by design. Tenant data resident in af-south-1. Information Officer registered with the SA Information Regulator. Region: af-south-1 tenant plane |
| encryption at rest | enabled | AWS KMS-managed keys for tenant Postgres, Qdrant volumes, and S3 buckets. Per-tenant KMS key for any collection with special_pi=true. |
| encryption in transit | enabled | TLS 1.3 on every public endpoint. Linkerd mTLS on every pod-to-pod hop, including cross-region inference path. |
| breach notification | ready | 72-hour breach notification pipeline. Audit categories isolation_violation_detected, unauthorised_access, data_exfiltration_attempt auto-trigger runbook. SLA: 72 hours |
Audits & certifications
Where each programme actually stands today, with its dates. We do not list an attestation we do not hold.
| Programme | Status | Detail |
|---|---|---|
| soc2 type2 | observation in progress | SOC 2 Type II observation period began at launch. Full report available month 12.
|
| iso27001 | stage 1 evaluation | ISO 27001 Stage 1 evaluation in progress for EU customers. Full certification a year-2 milestone if EU pipeline justifies. |
| pen test | scheduled | External pen test #1 is scheduled with an independent firm ahead of GA. The report summary will be available under NDA once complete.
|
| bug bounty | scheduled | Private bug bounty programme launches month 6. Public bounty consideration at month 12.
|
Tenant isolation primitives
Isolation is enforced by construction — at the namespace, database and vector-store layer — not by a WHERE clause an engineer could forget to write.
| Pod-namespace tenant ID | Tenant ID is derived from the pod's namespace at boot, never from a request parameter. |
|---|---|
| Stateless model plane | No prompt content is persisted. Audit logs store hashes + token counts only. |
| Cross-tenant cache off | vLLM cross-tenant prefix caching is disabled by default; re-evaluation gated on SOC 2 Type II. |
| Belt-and-braces retrieval | Qdrant collections are physically separate per (tenant, collection) and every query filters by tenant_id payload. |
| Internal email + password authentication | Argon2id-hashed, NIST 800-63B policy, account-enumeration-safe responses, 5-strike soft lockout. On-prem installs own their credential store outright — it never touches a hosted third-party IdP. Enterprise SSO (SAML / OIDC) federation to your own identity provider is on the roadmap; when it ships, feder8d does not become a sub-processor of your IdP. |
Full architecture & control inventory
Full security architecture, current control inventory, and audit evidence available under NDA upon request.
Request access by emailing security@feder8d.com.
Report a vulnerability
Email security@feder8d.com. We acknowledge reports within 3 business days and accept private disclosures via our (invitation-only) bug bounty programme.
Deferred items
Published so an evaluator does not have to ask. These are not in scope today.
| HIPAA / BAA | Phase 2 — when first US healthcare customer signs. |
|---|---|
| FedRAMP | Not on the roadmap. |
| CCPA explicit notice | Added at first paying CA customer. |
Bring your reviewers.
feder8d is AGPL-3.0 open core — the corresponding source is available to customers, users and their auditors on request. Your security team can read the code that handles your data.