Structly - Architecture as code — diagrams that update when code does

👋 Hey Product Hunt, Every architecture diagram I've ever drawn died the same way: beautiful in Lucid/Miro/Excalidraw on day one, quietly wrong by week three, and openly lying about the system within a month. Nobody updates the picture, so eventually nobody trusts it. I built Structly so the diagram can't drift from the code, because it lives with the code. It's an architecture diagram described as a plain .structly.json file you commit to your repo. That one decision unlocks a few things: It's generated, not hand-drawn. Describe your system in a sentence ("a web app, an API, a Postgres DB, and a worker draining a queue") or point it at a GitHub repo, and you get a first diagram in seconds. Edit from there. It's actually readable. Click any box to read what it does. Press play to follow a single request through the whole system, hop by hop. It diffs. It's JSON in version control, so the diagram shows up in code review next to the change that caused it. No more "update the wiki" tickets nobody does. It meets you where you work. There's a VS Code extension with schema validation, autocomplete, snippets, and a live preview right beside your file. Generation runs on Sonnet 4.6 and Haiku 4.5 today, with Opus 4.8 coming soon. Honestly, this started as me scratching my own itch. I was buried in a big codebase where the only "map" of the system was a diagram that hadn't been true in over a year, and I kept re-deriving the architecture in my head every time I touched something. I wanted a picture that stayed honest without anyone having to babysit it. It's free to try — no signup to generate your first diagram. Just describe your system and go. I'd love your honest feedback, especially: does the generated diagram match how you'd actually draw your system? And what would make this a permanent part of your repo? I'm in the comments all day. — Harshith