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.
seeing the aws cost before it ships is the real win here 🙌 congrats on the launch
I like that a reviewer can see the plan, cost, and diagram diff in one place without needing AWS access — that's the part that usually breaks when I try to get a second pair of eyes on infra. The per-resource cost estimate is what I'd check first, since a diagram that hides the price is how a small change quietly becomes an expensive one.
Knowing the expected AWS costs before a change goes live could save teams from some nasty billing surprises
Congrats on the launch! great to see your vision coming alive guys, lets go! 🚀
Keeping intended infrastructure separate from a hotfix in the console is a useful distinction. The expected-versus-actual view gives the reviewer a concrete decision to make before the next plan overwrites a change worth keeping.
Reviewing a diagram change before it hits my own AWS account is the bit that would get past our security people, since visual tools usually hide the apply button behind a magic commit.
can it pull in an existing aws account or do i have to draw it all from scratch? most of our stuff already lives in terraform so thats kinda the deciding thing for me
It's wonderful tool. Instead of using AWS console with different tabs on browsers, I'd like to use such a tool. Congrats team!
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???
congrats!! does the diagram stay true if someone hotfixes stuff straight in the console at 2am? that drift is usually where these break
About Paxper on Product Hunt
“Create cloud infrastructure visually and review every change”
Paxper launched on Product Hunt on November 13th, 2026 and earned 109 upvotes and 24 comments, placing #9 on the daily leaderboard. Visual infrastructure as code: design cloud resources on a diagram, review every change, and apply it in your own AWS account.
Paxper was featured in Design Tools (264k followers), SaaS (45.4k followers) and Artificial Intelligence (483.7k followers) on Product Hunt. Together, these topics include over 248.3k products, making this a competitive space to launch in.
Who hunted Paxper?
Paxper was hunted by Kerem D. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Paxper stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Kerem D
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