Hi, I'm Antoine PedrettiCloud engineer building products in public
Cloud/DevOps engineer with scale-up DNA, now building AI products and content in public. Infrastructure, product, and indie hacking — all at once.
I'm a cloud engineer with 3+ years working in the startup ecosystem — shipping production infrastructure at fast-growing companies. One of the platforms I helped scale grew from 0 to 100+ cities in 18 months, processing millions of real-time data points and contributing to a €15M fundraising round.
Working that close to fast scale made me want to be closer to the product itself. So in parallel, I started building my own: AI products, experiments, a content studio, a freelance agency. The empire model — each one teaches me something the next one needs.
I'm also always learning. This year I'm deepening AI engineering, product management, and shipping cadence. I share what I learn as I go.
Active in:
Scale-up DNA, product mindset
Posture stats — the experience without naming employers. Credentials that travel with me, not with the companies I happened to work at.
How I work
Six principles that shape what I build and how I ship. The stack is a consequence of the problem, not the other way around.
Ship first, optimize later
MVPs over polish. Public revision beats private perfection. A shipped B+ ships a week, a perfect A ships never.
AI-native development
AI is infrastructure now, not a feature. Claude Code runs alongside me every day — it's part of the stack, not a gimmick.
Scale-up pragmatism
Production scaling taught me what actually breaks. Overengineering kills more startups than underengineering — I ship for the load I have, not the load I imagine.
Breadth over depth
I'd rather be strong across infra, AI, web, and product than deep in one. The problem picks the stack — currently Terraform, AWS, LangGraph, Next.js, Python.
Product-owner mindset
I don't just execute, I decide what to build. A DevOps background means I also know what the ops-cost of a decision will be — and scope accordingly.
Always learning, always shipping
Courses run while projects are live. Both at once, forever. Learning in public means every course I take shows up in the next thing I build.
Projects
Each card is a bet and a lesson. Thesis first, stack second, what I learned third. The story lives on the blog.
Project retrospectives drop here as they ship. First one soon.
From the blog
Build stories, scale-up lessons, and indie hacker notes. What I think as I ship.
Build stories drop here as I ship. First post soon.
Let's talk
Hiring: cloud/DevOps roles or CTO-flavored early-stage work — my resume is here.
Everything else: the blog covers most of what I think.
Email address
antoine@helmo-solutions.com