Component

core/ai-agent/dify-plugin-daemon

The Dify plugin runtime — the service that installs and runs the plugins a Dify installation's model providers and tools are delivered as. Every model call and every tool invocation an application makes is dispatched through it, so an installation with no plugin runtime can edit a workflow but cannot run one. It keeps its own plugin catalogue and installation records in a dedicated database on the PostgreSQL backend wired through the `backend` uses-socket, coordinates through the Redis-compatible cache wired through `cache`, and calls back into the API server over the internal API on the `api` socket to resolve workspace and credential context. Installed plugin packages and their prepared runtime environments live on its own volume, and it verifies each package's signature before running it, so it renders as a single-replica stateful server with a persistent claim. Exports its host, port and protocol to consumers via the uses topology. It serves its own metrics in the Prometheus format at /metrics/ on that port, on by default and asking no key, and its Recipe publishes that address as `metrics_endpoint`.

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:235db0a06173e63ea780afee705f161b356137d9bb23b70ec6ded021a2a2ce76
Published
2026-11-10T10:07:46Z
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:6b10147c2e908f21a543eea128ac8d8c25ebff57f5816ccadcbed892b88011ba

Reference at this version

oci://hub.aggrega.ai/component/core/ai-agent/dify-plugin-daemon:1.0.0

Developer parameters

Values the developer sets in the Aggregate.

NameTypeDefaultRequiredDescription
plugin_databasestringdify_pluginnoName of the database the runtime keeps its plugin catalogue in. It sits on the same backend as the platform's own database and is separate from it, so an installation that reuses one server for both keeps the two schemas apart.
verify_signaturebooleantruenoWhether a plugin package must carry a valid signature before the runtime will install it. Left at the default, an unsigned package is refused, which is what stops arbitrary code entering the installation through the plugin path. Set it false only for an installation that develops its own unsigned plugins.
max_package_sizeinteger (min 1)52428800noLargest plugin package, in bytes, the runtime accepts for installation.
max_execution_timeoutinteger (min 1)600noHow long, in seconds, one plugin invocation may run before the runtime stops it.

Operator sizing

Infrastructure sizing the operator tunes per environment.

NameTypeDefaultRequiredDescription
portinteger (min 1024, max 65535)5002noHTTP listen port the plugin-dispatch API is served on.
engine_versionstring0.6.10-localnoDify plugin-runtime container image tag. The runtime is released on its own cadence, so this tag moves independently of the API server's.
computeobject—no—
storageobject—no—
overridesobject (open)—noProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

Output contract

Values this component publishes to consumers over the uses topology.

NameTypeDefaultRequiredDescription
hoststring—yesIn-cluster DNS name of the Service fronting the plugin runtime. The API server dials this name to dispatch a model call or a tool invocation.
portinteger—yesTCP port that Service accepts dispatch requests on. It follows the port an operator set in the Release, so a consumer reads it rather than assuming a default.
protocolstring—noURL scheme to reach `host` and `port` over, which a consumer composes its base URL on.
metrics_endpointstring—noThe full address Prometheus scrapes this component's metrics at — scheme, host, port and path, `http://<host>:<port>/metrics/` on the dispatch port. Empty where the component serves none reachable.

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.

backend

Selector
component.aggrega.ai/category=datastore
Inject
env

Slots each connection through this socket may fill

SlotSelectorRequiredInjectSensitiveDescription
credentialfeature.aggrega.ai/kind=secretnoenvyesOptional password the runtime presents to the backend this connection reaches, shared with that backend. When attached, supplies the backend password via the credential subsystem; unattached, the Recipe uses the development literal `apppass`, which this catalog publishes, so every Release that leaves the slot unattached shares that password.

cache

Selector
component.aggrega.ai/category=datastore
Inject
env

Slots each connection through this socket may fill

SlotSelectorRequiredInjectSensitiveDescription
server_cafeature.aggrega.ai/kind=secretnofileyesOptional authority the runtime checks the cache's certificate against while the cache publishes protocol valkey-tls or redis-tls, where the image does not already trust the authority that signs it. Its Secret holds ca.crt. The Recipe mounts the whole Secret read-only and points the runtime's cache client at the file. The build halts on a server_ca publishing no Secret name, and on one wired to a cache served without TLS. Fill it with core/referenced-secret.

api

Selector
component.aggrega.ai/category=ai-agent
Inject
env

Slots each connection through this socket may fill

SlotSelectorRequiredInjectSensitiveDescription
credentialfeature.aggrega.ai/kind=secretnoenvyesOptional credential the runtime presents on every call back into the internal API of the API server this connection reaches, which the server compares against its own. The API server and the task worker hold the same key in their inner_api_key slots, so the credential is attached to all three or to none: attaching it to some of them leaves the rest carrying a different value, which renders cleanly and is refused when the call is made. Unattached, the Recipe uses the pinned development literal `dify-plugin-inner-api-key`, suitable for evaluation only and published in this catalog, so every Release that leaves the slot unattached shares it.

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.

SlotSelectorRequiredInjectSensitiveDescription
plugin_daemon_keyfeature.aggrega.ai/kind=secretnoenvyesOptional credential the runtime requires of every caller, and which the API server and the task worker present on every call they make, each on its own connection to the runtime. The same credential is attached here and on both connections, or on none: attaching it to some of them leaves the rest carrying a different value, which renders cleanly and is refused when the call is made. Unattached, the Recipe uses the pinned development literal `dify-plugin-daemon-server-key`, suitable for evaluation only and published in this catalog, so every Release that leaves the slot unattached shares it.

Self-inject allowlist

env

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

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