Launched this week
Paxper
Create cloud infrastructure visually and review every change
112 followers
Create cloud infrastructure visually and review every change
112 followers
Visual infrastructure as code: design cloud resources on a diagram, review every change, and apply it in your own AWS account.







Free Options
Launch Team

AWS Activate CreditsCredits that fuel your startup’s next milestone
Promoted
Congrats on the launch! great to see your vision coming alive guys, lets go! 🚀
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???
@thamibenjelloun Glad that part resonates, that's exactly the problem we wanted to solve.
Prices come straight from AWS's own Price List API, per region and refreshed nightly, with no third-party pricing data in between. For the resources on the diagram, the estimate follows the same billing math AWS uses (instance hours, storage, NAT hours and so on), so it should land close to what you actually get billed.
And yes, the reviewer doesn't need any AWS access. The credentials live in Paxper, so you can name specific people or roles as approvers, and they review the plan and its cost in Paxper before anything gets applied.
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.
@karimbenkeroum Thanks, that's exactly why we built it this way. Editing the diagram never touches your AWS account on its own. Every change becomes a plan you can review first, and applying it is a separate, explicit step.
Happy to walk your security team through the flow if that helps.
congrats!! does the diagram stay true if someone hotfixes stuff straight in the console at 2am? that drift is usually where these break
@igorblink Thanks! And you're right, that's exactly where most of these tools fall apart.
Short answer: the diagram doesn't silently rewrite itself to match the console. It stays the source of
truth for what you intended, and Paxper tells you when reality stops matching it.
Drift detection compares your live AWS resources with the last successful apply. You can run it on demand
or schedule it (hourly up to daily). It shows which resources were added, removed or modified, and for
each changed attribute, the expected vs. the actual value. A drift alarm fires when something's off.
So for the 2am hotfix: the next morning you see exactly what was changed. If the fix should stay, you put
it in the diagram so the next plan doesn't undo it. If it shouldn't, the next apply brings things back in
line.
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.
@oleksii_sekundant Appreciate it! Console hotfixes happen, especially mid-incident, and the expected-vs-actual view makes sure they don't get silently overwritten. But we'd rather they didn't have to happen in the console at all.
In Paxper you can apply a hotfix right from the platform, so it's recorded as an intended change and
never shows up as drift. Drift detection is there as the safety net for the cases that still slip through.