Component

core/security/kong-ai-pii-service

Kong's AI PII service: a service that finds personal and other sensitive data in a text and rewrites it in the same call. A caller posts a text, the categories to look for — person names and places, phone numbers, email addresses, card and bank numbers, national identifiers, credentials and the like — any regular expressions of its own, and how to rewrite what it finds, and the service answers with the rewritten text and what it found. The image is supplied by the operator: Kong distributes the service's images under its own terms, so the Release names in infra.image one it is entitled to pull, and the catalog names none. Nothing renders until the Release sets `infra.image`. Each image carries the language model for the language its tag names, or all of them; a model the service is configured for that its image does not carry is fetched from the spaCy models repository when the service starts, by the running service and never by the build. core/gateway/kong-enterprise takes it on its pii_sanitizer socket, for Kong's AI PII Sanitizer. Recognition is automated, so it misses some sensitive data and marks some text that is not sensitive. Kong's sanitizer presents no credential to it and every text reaches it unmasked, so it is published on an in-cluster address for the component that calls it and is not meant to be exposed beyond the cluster. Realized on Kubernetes by its Helm Recipe, running the image the Release names as a single stateless service over plain HTTP. Exports its host, port and protocol to consumers.

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:db2746c4ef7d535f77627a74250b3bbb891bf537712660809cb9416ccc23db4e
Published
2026-11-10T10:13:40Z
Signing identity
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Signature

  • Officialapplication/vnd.dev.sigstore.bundle.v0.3+json

    https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

    sha256:84444e03c603c399b53b3833a4a52c148a214dea539f47cc5874dd6a85d7899d

Reference at this version

oci://hub.aggrega.ai/component/core/security/kong-ai-pii-service:1.0.0

Developer parameters

Values the developer sets in the Aggregate.

No developer parameters declared.

Operator sizing

Infrastructure sizing the operator tunes per environment.

NameTypeDefaultRequiredDescription
imagestring—yesFull reference of Kong's AI PII service image, tag included, as in kong/ai-pii-service:v0.2.2-en — the image the operator is entitled to pull. The tag names the language whose model the image carries, or all of them. There is no default, because access to the images is governed by Kong's terms rather than by the catalog, and the catalog therefore names none; a build that omits it halts.
image_pull_secretstring—noName of a pre-created image-pull Secret granting access to the registry the image is pulled from. Set this when that registry needs credentials; omit it when the cluster can pull the image without them.
computeobject—no—

Output contract

Values this component publishes to consumers over the uses topology.

NameTypeDefaultRequiredDescription
hoststring—yesIn-cluster DNS name of the Service fronting the PII service. Every caller reaching this name can submit text, so it is an address for the component that calls the service rather than one to publish.
portinteger—yesTCP port that Service accepts callers on, the port the service listens on over plain HTTP. A consumer reads it rather than assuming a default.
protocolstring—noURL scheme to reach `host` and `port` over, which a consumer hands to the client it calls the service with.

Uses sockets

The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.

No uses sockets declared.

Attachment slots

Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.

No attachment slots declared.

Self-inject allowlist

No self-inject pipes declared.

Relationships

Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.

Uses

This entity uses nothing in the catalog.

Used by

Component concept reference →

The Aggrega catalog — an open index of components, features, recipes, and the plugins that render them.

Built with the shared Aggrega design system.

Privacy