FossFLOW: Privacy-First Infrastructure Diagrams

Stan Smith works a full-time job. In whatever hours remain, he maintains FossFLOW—a browser-based infrastructure diagramming tool that solves the limitation of commercial cloud diagramming tools requiring account registration, diagram limits, and subscription fees. Your infrastructure topology never touches someone else's server.

The Problem: Your Infrastructure Docs on Someone Else's Server

Drawing your network architecture in Lucidchart or Cloudcraft means uploading proprietary infrastructure documentation to third-party cloud platforms. For DevOps teams handling compliance requirements or sensitive topology information, that exchange—access to your diagrams for SaaS convenience—creates friction. Add recurring subscription costs, and the value proposition gets murkier for teams willing to self-host.

What Stan Built: Browser-Local Diagrams with Zero Cloud Dependency

FossFLOW runs as a Progressive Web App using React, TypeScript, and the Isoflow diagram engine. Diagrams live exclusively in browser localStorage. No authentication flow, no API keys, no data leaving your machine unless you explicitly export it. Open the URL, start dragging isometric infrastructure components, save locally. The architecture trades cloud sync and collaboration features for complete privacy control.

How It Works: From PWA to Self-Hosted Docker

The browser version works offline immediately—localStorage handles persistence without server round-trips. For teams wanting centralized access, FossFLOW deploys via Docker with persistent server-side storage, supporting both linux/amd64 and linux/arm64 architectures. Integration with Umbrel and Zeabur gives self-hosting communities familiar deployment paths.

Version 1.0.0 shipped in October 2024 with testing, CI/CD integration, and Docker multi-architecture builds. By December, version 1.0.5 added multi-language support for Spanish, Portuguese, French, Hindi, Bengali, and Russian, plus image export and custom icon imports.

The 1.0 Journey: One Developer vs. Well-Funded Teams

Stan maintains this alongside full-time employment, which shapes what FossFLOW can accomplish. The repository forked from the Isoflow library and carries MIT/Unlicense terms—pragmatic choices for a solo maintainer managing scope. Reaching 1.0.0 with multi-language support and deployment flexibility represents real progress given those resource constraints.

The gap between one developer's evenings and a venture-funded team's sprint capacity shows up in feature velocity and integration breadth. FossFLOW won't match the AWS-specific automation or collaboration tooling that commercial platforms staff teams to build. What it offers instead: zero recurring costs, complete source access, and infrastructure diagrams that stay exactly where you put them.

Where FossFLOW Fits: Excalidraw, Mermaid, and Cloudcraft

HackerNews discussion identified Excalidraw, Mermaid, Ilograph, and Cloudcraft as tools solving adjacent problems with different tradeoffs. Excalidraw prioritizes freehand drawing flexibility over infrastructure-specific components. Mermaid uses code syntax for version-controlled diagrams but requires learning domain-specific language. Cloudcraft delivers deep AWS integration and real-time resource sync that FossFLOW doesn't attempt.

FossFLOW targets the gap: infrastructure architects wanting isometric diagram aesthetics without uploading topology documentation to SaaS platforms. Each tool serves different use cases depending on team priorities around collaboration, cloud integration, or privacy control.

Who This Serves: DevOps Teams That Value Control

Technical communities including DevOps engineers, system architects, and infrastructure documentation specialists use FossFLOW based on developer blogs and tutorial videos. The profile fits teams with compliance constraints around data residency, self-hosting advocates running homelab infrastructure, or organizations evaluating subscription fatigue against tooling requirements.

The trade-off: accept slower feature development and smaller community in exchange for complete privacy control and zero vendor lock-in. For some infrastructure teams, that math works.