Diagrams should be version controlled, reviewable, and effortless — a lightweight, high-performance, and minimal dependencies rendering engine for all your documentation needs.

Managing multiple rendering engines—Mermaid, Graphviz, D2—often leads to “Docker bloat” or complex CI/CD setups. We built Kroki-rs to solve this.

By leveraging native CLI tools and the safety of Rust, we’ve created a drop-in replacement for the Kroki API that is:

• Instant: Low latency rendering for local development.

• Resource Efficient: Fraction of the memory footprint of Java-based alternatives.

• Native: Runs directly on your host or edge devices.

Structure of the Documentation¶

This guide is designed to get you from zero to production quickly:

• Discover: Why Kroki-rs is the right choice for your stack.

• Understand: Explore the supported engines and tool requirements.

• Apply: Practical patterns for CLI and Server usage.

• Developer Guide: Deep dive into the rust-native architecture.

Information is visual. Rendering should be effortless.