AI AdminPanel Documentation

AI Services Templates

This inventory describes the v2.12.8 source manifests in the ai category. Available means the manifest is not marked Coming Soon; it is not proof of a successful deployment, a current browser card, or a security review. The browser's unfiltered catalog is paginated; use category/search controls to find an entry. See Template System.

Template List

Template IDSource availabilityMinimum CPU coresMinimum memory MB
anything-llmAvailable12048
bolt-diyAvailable22048
comfyuiComing Soon24096
contextforgeAvailable11024
crewaiComing Soon11024
deerflowAvailable24096
difyAvailable26144
flowiseAvailable11024
hermes-agentAvailable22048
ironclawAvailable22048
janComing Soon22048
langflowAvailable12048
librechatAvailable12048
localaiAvailable24096
nanoclawComing Soon1512
nemoclawComing Soon48192
ollamaAvailable24096
open-webuiAvailable11024
openai-compatible-proxyAvailable1512
openclawAvailable22048
paperclipAvailable11024
perplexicaAvailable22048
rag-apiAvailable12048
searxngAvailable1512
stable-diffusion-webuiComing Soon24096
text-generation-webuiAvailable24096
vllmAvailable48192
whisperAvailable24096

Before deploying

Select an available card and review its current variables, image/source version, resource limits and application instructions. Coming Soon entries cannot be deployed. Minimum memory is a declared requirement, not a capacity guarantee. Required password inputs and generated system secrets are different: a blank password field does not automatically generate a value.

Use Template Deploy for the deployment steps and Template Authoring for the manifest schema. Container health checks report readiness; they do not by themselves restart a hung application or provide automatic image/security updates.

AI configuration

Choose the source supported by the template's aiInjection mapping, or configure the application itself when no mapping is declared. BYOK, shared Provider AI, Local AI and Metered AI have different storage and billing behavior; see How AI works.

OpenClaw: the shipped template disables Control UI device authentication. Password authentication remains configured. Read the prominent hardening warning before deployment; the catalog's availability marker is not approval of that security default.