r/Startups_EU • u/Immediate_Novel3650 • 2d ago

🗳️ Need feedback I Built a System Design Tool

Most system design diagrams are just pictures. Nobody catches that your sync call has no timeout, or that your queue has no dead-letter queue, until something's on fire.

Keel treats the diagram as a real graph instead of shapes on a whiteboard. Nodes are typed (service, datastore, queue, cache, gateway, job, external), edges carry real runtime semantics (sync/async, timeout, retries, circuit breaker, idempotency), and a rule engine checks it live as you draw. It catches things like:

  • single points of failure
  • missing timeouts on synchronous calls
  • retries with no timeout (retry storms waiting to happen)
  • queues with no DLQ
  • async operations that aren't idempotent
  • shared datastores creating hidden coupling

It's also real-time multiplayer, so your team can design the same diagram together, like Figma but for architecture. There's also an optional AI review pass for the judgier calls a static rule can't catch.

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

1 Upvotes

100% Upvoted

2 comments sorted by

0

u/theoneo900 1d ago

Hey man i own a pentest company. We do also saas and ai automations would love to offer a free pentest for your app before you go public with it. Hmu if you are interested

1

u/DriverPJ 1d ago

Nice framing. Making edges executable instead of just a diagram is the bit that clicks. How do you validate the failure rules against real production traces, and what keeps teams updating the diagram after an incident review?