Skitflow

AI Assistant

Use Skitflow's AI Assistant to generate Compose files, analyze deployments, harden configuration, answer product questions, and propose confirmed operations through AI Gateway.

The AI Assistant is Skitflow's product-facing AI layer. It is no longer a separate "AI DevOps Agent" feature. The assistant now covers Compose generation, Ask AI workflows, operational diagnostics, security reviews, and proposal-based actions.

The assistant uses AI Gateway for model routing when the gateway is enabled. It can also use the direct provider configuration path when the gateway is disabled.

What it can do

  • Generate Docker Compose — describe what you want and Skitflow creates services, environment variables, volumes, domains, and supporting config files.
  • Review Compose files — analyze Compose or Swarm stack files for insecure defaults, missing health checks, missing resource limits, privileged containers, risky mounts, and image pinning issues.
  • Harden Compose services — propose safer Compose changes with secrets redacted from the prompt.
  • Diagnose operations — inspect applications, compose services, databases, domains, backups, logs, metrics, route metrics, and deployment history when the user has permission.
  • Propose actions — prepare deploy, redeploy, restart, environment update, backup, domain, database, and volume-backup actions for explicit confirmation.

The Assistant can propose operational changes, but mutating actions are not applied just because the model suggested them. The user confirms the proposal, then Skitflow re-checks server-side authorization and dispatches the real mutation.

AI Gateway routing

When AI Gateway is enabled, the Assistant can use a dedicated model route instead of the organization default. The routing order is:

  1. Assistant-specific route.
  2. Organization default route.
  3. Newest enabled BYOK provider.
  4. Platform default chat model.
  5. No model configured.

This lets operators run the Assistant on a stronger or governed model while keeping other Ask AI flows on a cheaper or tenant-owned provider.

Supported provider modes

Skitflow supports both direct provider configuration and gateway-routed providers:

ModeHow it works
BYOK providerConfigure OpenAI-compatible providers in AI Gateway → Providers. The old Settings → AI page redirects there.
Platform modelOperators configure a platform default model in AI Gateway → Models. Tenants can use it without bringing their own key.
Direct fallbackIf AI Gateway is disabled, existing direct provider behavior continues to work.

OpenAI, Anthropic, Ollama, OpenRouter, Azure OpenAI, and other OpenAI-compatible endpoints can be used through provider configuration, depending on the provider adapter and endpoint shape.

Compose generation flow

  1. Navigate to Docker Compose → Create with AI.
  2. Describe what you want in natural language, for example "WordPress with MySQL and Redis cache".
  3. The Assistant generates a complete deployment including:
    • Docker Compose service definitions.
    • Environment variables with sensible defaults.
    • Volumes and network configuration.
    • Extra config files, each with path and content.
    • Domains mapped to the right service and port.
  4. Review and edit the output.
  5. Deploy from the editor, optionally targeting a specific server.

Operational tools

When used from the Assistant panel, Skitflow can expose scoped tools for:

  • Application and compose status, logs, deployments, metrics, and pre-deploy checks.
  • Database details, logs, metrics, and redeploy proposals.
  • Backup and volume-backup history, logs, and creation proposals.
  • Domain toggles and Traefik-related security checks.
  • Observability route metrics when Observability is available.

Tool access is scoped by organization, project, service, and RBAC permissions. The Assistant should not be treated as a root shell; it is a controlled interface over Skitflow APIs.

Privacy and safety

  • Secrets are redacted before logs or Compose files are sent to the model.
  • Environment diffs show key names only, not values.
  • Provider keys are stored server-side and are not returned to the browser.
  • Mutating proposals require explicit confirmation and server-side authorization.

Cost

Skitflow does not charge directly for BYOK provider usage. You pay your provider according to its pricing. Platform-provided models can be governed and tracked through AI Gateway usage and budget controls.

On this page