AIVory Architect

Hi Product Hunt!

I'm Jenni from the AIVory team. We've spent 20+ years building software, and infrastructure has always been the part that takes way longer than anticipated and no one really wants to tackle.

Not because it's unimportant — but because it's a massive time sink that pulls you away from actually building your product. And let's be honest, best practices also keep shifting so every time you get started on a completely new project there is something new to learn and documentation can be an absolute pain to find or understand.

Strange syntax, the jungle that is AWS or Azure documentation, indent errors in your YAML... but even when you have a working version (yay!) have fun remembering what the commands were you needed to restart or deploy. To not even speak of getting information from a specific pod... You're jumping between terminal, cloud console, and Lens just to see what's happening.

We built Architect out of these pain points for our own use because we wanted to skip all of it:

* Design infrastructure visually (drag-and-drop, a wizard, no syntax)
* Deploy with auto-generated Terraform/K8s configs
* Operate with SSH, logs, and monitoring right in the IDE (a simple button)

That last part matters most to us. Design is a one-time thing. Debugging and monitoring happen every single day — and we were tired of context-switching between 5 different tools to do it.
We decided to build it as a plugin for your IDE so it is where you are already working anyway. It is available for Jetbrains, VSCode and anything that uses the VSX Marketplace like Cursor or Antigravity.

We're offering 50% off for 6 months for the PH community.

Question for you: what's the most frustrating part of your current infrastructure workflow? We'd love to hear what we should tackle next.

interesting concept