So, I've build Archflow
Every time I saved a diagram in draw.io, I knew it was a lie. The second I hit “save,” reality had already moved on. Structurizr’s DSL felt like writing code to describe code. And the “just use Confluence” crowd hadn’t earned the right to speak.
So I did what any architect with too much free time does: I built my own. Three times. C# first. Then Java. Then TypeScript. Now it’s ready for strangers.
Your architecture docs are more like archaeology docs
You know the drill. You spend hours on the perfect C4 diagram. You align it with arc42. You even add colors. Then life happens, a service gets renamed, a new dependency sneaks in, a microservice multiplies, and your crisp documentation becomes a relic. A lie that gets you in trouble.
From Kubernetes crawler to living workspace
At first I thought automation was the answer. Crawl Kubernetes, auto-generate Structurizr DSL. It worked. Sort of. Until the files got so big I was drowning in my own glue code.
Then I tried Java with the SDK instead. Still archaeology, just typed.
That’s when it clicked: I wasn’t solving the real problem. The problem isn’t docs that fall behind. The problem is docs that only ever reflect the past. What I wanted were docs that help shape what comes next.
So I started over. ArchFlow is a living workspace where the architecture evolves with the system. You update it from your coding agent via MCP, not three sprints after the fact. One source of truth that moves at the speed of the code.
What you can actually do with it
Model systems with C4, DDD context mapping, and workflows
Tag systems with ArchDeck cards
Calculate blast radius and complexity, the kind of numbers that end “it’s fine” arguments
Publish docs teams actually trust: arc42, custom pages, embeddable diagrams
Onboard existing projects via MCP and coding agents (Claude, Codex, etc.)
Talk to Archie, your BYO-AI architecture sidekick. No token scalping.
It’s opinionated. So am I. Built for the architect tired of tools designed by committee, or by someone who’s never shipped code.
The invite
ArchFlow is in closed beta. If you want in:
Invite code: build-simple-1
First-come, first-served.
Over the next few weeks I’ll share how I actually use it, design decisions, war stories, more invite codes. And with luck, fewer rants about draw.io.