ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Está viendo la edición Perú. Está viendo la edición Colombia. You're viewing the Pakistan edition. Cambiar a la edición global →Cambiar a la edición global →Switch to the global edition →

Mermaid diagrams render to PNG server-side, exposed over a gRPC endpoint

Mermaid diagram rendering now produces PNG output alongside SVG, exposed through a new TransformMermaidToPNG gRPC call, so diagrams embed reliably in generated PDF reports.

Mermaid diagrams can now be rendered to PNG on the server, not only to SVG. The addition targets a concrete limitation: PDF report generation embeds raster images more reliably than inline SVG, so diagrams authored in Mermaid now survive the path into a pixel-perfect document.

Rendering pipeline

  • PNG alongside SVG. The Mermaid execution path returns either output form through a single result type, so a caller requests PNG or SVG without a separate code path.
  • Report embedding. The PDF pre-processor now embeds Base64-encoded PNGs for Mermaid graphs in place of generated SVG, keeping rendering consistent across the document toolchain.

Exposed as a service

  • gRPC transform call. A new TransformMermaidToPNG remote call, defined in the microservices protocol, renders a diagram to PNG out of process and returns the encoded image.
  • Aligned protocol contract. The protocol adds a dedicated PNG response message, so the encoded bytes travel over the same gRPC contract as the existing diagram transforms.

SVG output is unchanged for callers that prefer it; PNG is an additional option chosen at the point of rendering.

See the feature →

← All posts