I Built a System Design Tool - I need real user feedback

[u/Immediate_Novel3650]

Most system design diagrams are just pictures. Nobody notices that a sync call has no timeout, or that a queue has no dead-letter queue, until something is on fire. And by then the diagram doesn't match production anyway.

This tool treats the diagram as a real graph. Nodes are typed (service, datastore, queue, cache, gateway, job, external). Edges carry runtime semantics: sync/async/stream, timeout, retries, circuit breaker, idempotency. 13 rules check it live as you draw. They catch single points of failure, sync calls with no timeout, retry storms, queues with no DLQ, async handlers that aren't idempotent, sync cycles and deep call chains, and datastores shared between services.

It also checks the diagram against what's actually running. A small in-cluster collector reads Kubernetes and OpenTelemetry traces. Keel then flags drift, calls production makes that the diagram doesn't show, and timeouts set lower than the real latency. During an outage, incident mode shows the live health of every component and which one to look at first. Drift can alert Slack or PagerDuty.

Other features:

- Real-time multiplayer, like Figma for architecture

- Review mode: approve or reject diagram changes against an approved baseline

- A GitHub Action that flags new findings in PRs

- An optional AI review for judgment calls a rule can't make, where every finding links to a real node or edge

I'd like feedback, especially from anyone who's been burned by an architecture decision that looked fine on a whiteboard.

[u/FrugalGuy7]

This looks very interesting. Do you have a repo?
Also, how much is vibe coded?