The operator console. Every decision, every tenant, every model — printed afresh as data arrives.
Semantic DLP for the LLM era. Reversible anonymisation and runtime policy for every prompt, response, embedding, and agent action.
Traditional DLP looks for strings. AI leaks happen semantically — a developer pastes a stack trace that names a customer; a copilot summarises a deal memo into a retrieval index; an agent quietly emails a vendor list. Section sits in front of every LLM call, every retrieval, and every tool invocation, and answers three questions before any of them touch a model:
- What is in this payload? — entities, secrets, source code, regulated data, intent.
- Is this user allowed to send this to this model in this jurisdiction?
- Can we keep the request useful by anonymising sensitive parts and putting them back on the way out?
Yes → forward, log, lineage. No → block or transform, with a signed audit record.
git clone https://github.com/cwellbournewood/section.git
cd section
cp .env.example .env
docker compose up --buildPoint any OpenAI client at the gateway and send a prompt:
export OPENAI_BASE_URL=http://localhost:8080/v1
export OPENAI_API_KEY=section-demo-key
curl http://localhost:8080/v1/chat/completions \
-H "Authorization: Bearer $OPENAI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "gpt-4o-mini",
"messages": [{"role":"user","content":"Email john.smith@acme.com about invoice 4471"}]
}'Open the admin UI at http://localhost:3000, or run the smoke demo:
bash scripts/demo.shFull walkthrough: docs/getting-started.md.
- Gateway — OpenAI- and Anthropic-compatible HTTP proxy with adapters for Azure OpenAI, AWS Bedrock, Ollama, and any OpenAI-compatible endpoint.
- Semantic DLP — regex, secrets, source-code, prompt-injection, and Microsoft Presidio NER detectors composed into one pipeline with a category-keyed label taxonomy.
- Reversible anonymisation — vault-backed tokenisation (AES-256-GCM, per-tenant HKDF), FF3-1 format-preserving encryption, and redaction — policy-selectable per entity. Streaming responses are chunk-boundary safe.
- Policy as code — YAML + CEL, cosign-signed bundles, race-safe
hot-reload,
section-policy lint. - Audit & lineage — Postgres-backed hash-chained event log with a
section-audit verifytamper CLI, SIEM webhook, and Splunk HEC sink. - Edge coverage — Manifest V3 browser extension (6 consumer AI sites), VS Code + JetBrains extensions, and a local CA proxy that brings Cursor, Claude Code, Continue, aider, Cline, Copilot CLI, and Zed into compliance.
- Vector connectors — pgvector and Qdrant with scan-on-write and retrieval ACL enforcement.
- Admin UI — events, policies, lineage DAG, simulator, detokenise workflow, command palette. Light-first, AAA-accessible.
- Production deploy — Helm chart with HA, NetworkPolicies, and External
Secrets; Terraform reference modules for AWS, Azure, and GCP; Kubernetes
ValidatingAdmissionPolicyand Gatekeeper templates. - Supply chain — every release is cosign-signed, ships a CycloneDX SBOM per image, and carries SLSA-3 build provenance.
+----------------------------+
server-side apps, | Section Gateway |
agents, CI ------------------> | | --> OpenAI / Anthropic
| | --> Azure OpenAI / Bedrock
edge browser extension | +--------+ +--------+ | --> Gemini / Cohere / Mistral
(ChatGPT, Claude.ai, --/v1/scan----> | | Policy | | DLP | | --> Ollama / vLLM
Gemini, Copilot, /v1/restore| | engine |<-+ engine | | --> sovereign / local
Perplexity, Mistral) | +---+----+ +---+----+ |
| | | |
local CA proxy | v v |
(Cursor, Claude Code, --HTTPS_PROXY->| +-------------------+ |
Continue, aider, Cline, | | Anonymiser + | |
Copilot CLI, Zed) | | Token Vault | |
| +---------+---------+ |
VS Code, JetBrains --/v1/scan---> +-------------+--------------+
(scan-selection, |
diagnostics, tokenise) |
v
+-----------------------+-----------------------+
| | |
v v v
+-----------+ +-----------+ +-----------+
| Postgres | | Redis | | Admin UI |
| audit + | | vault | | (Next.js) |
| lineage | | (token -> | | |
| | | secret) | | |
+-----------+ +-----------+ +-----------+
Deeper dives in docs/architecture/.
- Getting started — install, first request, first policy
- Architecture overview
- Threat model
- Operations — observability, OIDC, signed bundles, backup/restore, disaster recovery, edge install
- Compliance mappings — EU AI Act, GDPR, HIPAA, SOC 2, ISO 27001, NIST AI RMF, CRA
- Architecture decision records
- Edge coverage matrix
Vulnerability disclosures go through GitHub Private Vulnerability
Reporting.
See SECURITY.md for the disclosure SLA and scope.
Every release is cosign-signed with verifiable GitHub OIDC identity. Each
image ships a CycloneDX SBOM and a SLSA-3 build provenance attestation;
verification recipes are in
docs/security/supply-chain.md.
Apache 2.0 — see LICENSE. Built to be forked, audited, and self-hosted.