[#CLI for Antidoc > Custom Kroki Server in CLI](https://wovalab-open-source-projects.zulipchat.com/#narrow/channel/330653-CLI-for-Antidoc/topic/Custom.20Kroki.20Server.20in.20CLI/with/598717466) ## Summary Add support for specifying a custom Kroki server URL through an optional CLI parameter. ## Use cases Currently, Antidoc uses a hardcoded Kroki server URL. This can be limiting in environments where users need to: - Use a self-hosted Kroki instance - Keep documentation generation traffic within their own infrastructure - Comply with security or data governance requirements - Use an alternative Kroki deployment for performance or availability reasons ## What is the expected new behavior? Users should be able to specify a custom Kroki server URL when running the CLI. ## Possible implementation Add an optional --kroki-server CLI parameter. When the parameter is provided, Antidoc should use the specified URL for all Kroki requests. Otherwise, it should fall back to the current hardcoded Wovalab Kroki server URL.