Skip to content

Introduction

OpenFlowKit is a local-first diagramming workspace for developers and builders. It combines a visual canvas, code-friendly representations, deterministic imports, AI-assisted generation, and share/export workflows in one browser-based tool.

OpenFlowKit works best when a diagram needs to evolve instead of staying static:

  • start from a blank canvas, template, AI prompt, code representation, or imported source artifact
  • move quickly from Mermaid, SQL, OpenAPI, infrastructure files, or a builder-oriented starter template
  • refine the result visually instead of treating generation as a one-shot output
  • keep a text representation close to the editor model when needed
  • export or share the same diagram across docs, design, and collaboration workflows

The current product centers on four major surfaces:

  • A visual canvas for direct editing
  • A command-driven launcher for search, templates, assets, layout, and design systems
  • A Studio rail for AI, code, imports, infrastructure sync, and linting
  • Export, embed, and share flows for moving work outside the editor

The editor currently has first-class support for these diagram types:

  • flowchart
  • stateDiagram
  • classDiagram
  • erDiagram
  • gitGraph
  • mindmap
  • journey
  • architecture

You will also see reusable node families for general-purpose flows, architecture icon nodes, annotations, sections, images, and wireframe-style surfaces.

Diagram state lives in the browser by default. You choose when to export, share, or join collaboration-style room flows.

OpenFlowKit does not force a single source of truth. You can work visually, with AI, through OpenFlow DSL, through Mermaid, or from structured imports.

Generated and imported diagrams come back into the same editable canvas model rather than becoming dead screenshots.