Trust Center

The record, before you ask for it

This page pre-answers what security reviews ask: how the platform is built, who touches your data, and what is, and is not yet, on the record.

01Architecture & data flow

How the platform is built

Each line cites the named controls that an in-cluster scanner re-checks continuously: the same checklist our own posture snapshots are graded against.

Tenant isolation: One platform, hard walls. PostgreSQL row-level security is forced on tenant-owned tables and service roles cannot bypass it; the evidence ledger and object storage are partitioned per tenant; the API rejects cross-tenant reads.
ISOL-001 · ISOL-002 · ISOL-003
Identity: Self-hosted Keycloak, OIDC. Protected endpoints reject missing and invalid tokens, and tokens minted for the wrong audience.
AUTH-001 · AUTH-002 · AUTH-003
Credentials & keys: HashiCorp Vault holds the secrets; workloads carry no static cloud credentials. Tenant data is encrypted with per-tenant envelope keys through Vault Transit, optionally wrapped by a cloud KMS. Evidence-signing keys come from managed secrets.
KEYS-001: KEYS-005
Service-to-service traffic: Mutual TLS across the Linkerd service mesh, with scoped server authorizations for critical internal services and a ≥95% mesh-coverage target where every exception is time-bounded. TLS 1.3 is enforced at the ingress.
MTLS-001: MTLS-005 · K8S-006
Policy evaluation: Fail-closed. A checkpoint that cannot be evaluated holds or blocks the action: nothing proceeds on a missing answer.
Audit & telemetry: Governed decisions are emitted as OpenTelemetry traces and sealed into a tamper-evident, per-tenant evidence ledger (immudb). Database activity is audited with pgAudit.
OTEL · PGAUDIT
Change management: GitOps is the source of truth: cluster state is declared in version control and synced by Argo CD, no manual drift. Security guard checks run in CI, and a runtime verifier re-checks the live cluster.
ARGO CD · CI
Supply chain: Container images are signed with Cosign and pinned by immutable digest.
K8S-005 · COSIGN
Workload hardening: No default service accounts, no cluster-admin bindings, hardened container security contexts, resource limits on every container, and no host networking.
K8S-001: K8S-004 · MTLS-004
Continuous posture: An in-cluster scanner replays a fixed, versioned checklist of these controls. Snapshots retain names, metadata, and hashes, never sensitive values.

02External service disclosure

Outbound paths in the reviewed deployment

These rows record outbound paths found in source and development GitOps. Counsel and founder approval are required before a signed production subprocessor schedule is issued. A production operator records the provider, region, and data-flow choices for its deployment.

Service	Purpose	Scope
Microsoft Azure	Development AKS hosting and Azure Key Vault integration. Current development node-label evidence records the westeurope region.	Development infrastructure
OpenAI	AgentKit defaults to an OpenAI-compatible provider, and the development execution and evaluation deployments accept an optional OpenAI credential. When enabled, the configured model endpoint receives agent or evaluation inputs and outputs.	Development agent execution and evaluation
Azure OpenAI	AgentKit and Policy Builder support Azure OpenAI when an endpoint and credentials are configured. The configured model endpoint receives agent prompts and model outputs.	Configuration-capable model provider
Anthropic	The Assistant and Policy Builder support Anthropic credentials and request paths. When enabled, the Anthropic endpoint receives assistant prompts and model outputs.	Configuration-capable model provider
Amazon Bedrock	Policy Builder supports Amazon Bedrock as a configured model provider. The selected Bedrock endpoint receives model inputs and outputs when a tenant enables it.	Configuration-capable model provider
Google Analytics 4	Traffic measurement. Runs in Google consent mode with all storage denied by default.	Public site and signed-in console
Microsoft Clarity	Session diagnostics. Synced to the cookie-consent signal; ad storage always denied.	Public site
Apollo.io	Business visitor identification for sales follow-up.	Public site after marketing consent
Calendly	Pilot and demo scheduling embed.	/book-demo
Resend	SMTP delivery for marketing lead messages.	Development lead capture
ntfy.sh	Push delivery for marketing lead and Argo CD deployment notifications.	Development notifications
PagerDuty	Alert routing for development Argo CD critical alerts and their alert metadata.	Development operations

Plausible Analytics is operated with the development deployment: its browser script and event endpoint point to plausible.dev.kla.digital, with service manifests maintained in this repository. It is deployment-operated infrastructure in this engineering disclosure.

03Vulnerability disclosure

How to report a vulnerability

A simple policy, stated plainly. We would rather hear about it from you.

Where to report: Email [email protected] with reproduction steps and your assessment of impact.
Acknowledgment: We acknowledge reports within five business days and keep you informed while we triage and fix.
Coordinated disclosure: We coordinate the timing of any public disclosure with the reporter, and credit good-faith reporters who want it.
Safe harbor: We will not pursue legal action over good-faith, non-destructive security research that respects tenant data and service availability.

04Certifications & audits

The honest line

A trust page from a company whose product is evidence cannot afford a single implied claim. So, plainly:

Certifications held today: None. We do not hold SOC 2 or ISO/IEC 27001 certification, and nothing on this page should be read as implying that we do.
What exists instead: A documented, versioned control model: scanned continuously in-cluster and mapped to internal-control and framework language. See the control mapping.
Independent assessment: Planned. We will put the engagement on this page when it is scheduled; no date is on the record yet.
Standards participation: KLA is a member of AFNOR's CN IA: France's AI-standardization commission, mirror committee to ISO/IEC SC 42 and CEN-CENELEC JTC 21. This is standards-setting participation.

05Documents on request

The paperwork, on request

What you can pull into a procurement file today.

Security whitepaper

Architecture, control implementation notes, and repository evidence for a technical security review. SOC 2 planning status is stated in the document.

Control mapping
Runtime controls, human approvals, and execution lineage mapped to internal-control and framework language.
View page →
Data Processing Agreement
A draft is under counsel and founder review. Request the approved version for your procurement file.
Request →
Execution lineage sample
A sample of the sealed execution-lineage record a governed pilot produces.
Request →

06Review pre-answers

What reviews usually ask

The questionnaire rows we can answer before the questionnaire arrives. Anything not listed here is not yet on the record: ask us, and we will say so.

Encryption in transit: TLS 1.3 at the ingress; mutual TLS between services across the Linkerd mesh.
Encryption at rest: Per-tenant envelope keys through Vault Transit, optionally wrapped by a cloud KMS. Evidence-signing keys are sourced from managed secrets.
Tenancy model: Multi-tenant with isolation enforced at three layers: forced PostgreSQL row-level security that service roles cannot bypass, per-tenant partitions in the evidence ledger and object storage, and API-level rejection of cross-tenant reads.
Identity & access: OIDC through self-hosted Keycloak; endpoints reject missing, invalid, and wrong-audience tokens. In-cluster: least-privilege service accounts, no cluster-admin bindings, hardened security contexts.
Secrets management: HashiCorp Vault. No static cloud credentials in workload environments; Kubernetes secrets sync from Vault via ExternalSecrets.
Logging & audit: OpenTelemetry traces for every governed decision; tamper-evident per-tenant evidence storage; pgAudit on the database. Posture snapshots keep names, metadata, and hashes, never sensitive values.
Change management: GitOps only. Cluster state is declared in version control and synced by Argo CD; security guards run in CI and a runtime verifier re-checks the live cluster.
Supply chain: Cosign-signed container images, pinned by immutable digest.
Backups: Development backup configuration for PostgreSQL, Redis, immudb, ClickHouse, Vault, and Plausible database jobs targets the in-cluster MinIO endpoint at minio.kla-infra.svc.cluster.local:9000 and the backups bucket. The observed MinIO Service is ClusterIP. A production operator selects the production backup target.
Data residency: Development evidence records AKS node labels in westeurope and backup targets inside the development cluster. This evidence describes development only. A production operator records its residency, backup location, and third-party transfer settings in the executed DPA.
Penetration testing: No third-party penetration test report is on the record yet. Automated posture scanning runs continuously against a versioned control checklist; an independent assessment is planned.
Certifications: None held today: see the honest line above. The control model and its framework mapping are documented and reviewable now.
External service disclosure: The rows above record outbound paths found in source and development GitOps. Counsel and founder approval are required before a signed production subprocessor schedule is issued.
Vulnerability reports: [email protected]: acknowledgment, coordinated disclosure, and safe-harbor terms are published above.

Read the record, then test it

The fastest security review is the one that runs on your own Process.

4 weeks · your Process · signed evidence you keep

Request a security review