Visual infrastructure as code: design cloud resources on a diagram, review every change, and apply it in your own AWS account.

Hey Product Hunt 👋 I'm Kerem.

For years I was the person my team pinged before anything touched AWS. Not because nobody else could write the code, but because the picture of how everything fit together lived in a few heads. Every change waited on one of us. And when it didn't wait, we found out weeks later, on the bill.

I didn't want to build another tool that makes infrastructure "easier". I wanted the expertise a team already has to travel with every change: you see what you're about to build, you know what it will cost, and someone else looks at it before it ships. That's where "your expertise, at Paxper speed" comes from.

Today is the first time we're showing Paxper outside our own circle, and honestly, I'm a little nervous. If you work on cloud infrastructure, I'd love to hear what slows your team down, what's missing here, and what you'd want next. I'll be here all day reading every comment.

Kerem
paxper.com

finding out on the bill weeks later is way too familiar, seeing what a change will cost before it ships is the part i'd show a team first

how close is the estimate to what AWS actually charges, does it count data transfer or only the resources on the diagram??? and can the reviewer be someone with no AWS acess at all???