Our Experience at AWS re:Invent 2024
What Made AWS re:Invent Special for Qovery and Me
The Scale and Importance of the Event
AWS re:Invent is more than just a tech conference—it’s where cloud innovation happens. For a company like Qovery, focused on automating tedious, time-consuming, and costly DevOps tasks, having a booth in the AWS Marketplace space was a no-brainer. This event brought together the right decision-makers—people who truly understand the challenges of managing infrastructure—and gave us the perfect stage to demonstrate how Qovery makes a difference.
Human Connections in a Digital World
As much as I love technology, nothing beats the power of face-to-face interactions. Meeting our customers, prospects, and partners in person at re:Invent was an absolute highlight. We had the chance to share ideas, gather feedback, and build stronger relationships.
These real-life conversations reminded me why human connection is irreplaceable in a world dominated by Zoom calls and Slack messages 😁 (I still love Slack).
The Magic of Live Demos
If you know me, you know how passionate I am about showing Qovery in action. At re:Invent, we delivered hundreds of live demos, and I have to say, the “wow” moments were unforgettable. Watching decision-makers react to how Qovery can simplify DevOps and drastically cut costs was so rewarding.
The fact that we ran these demos straight from an iPad — no mouse, no keyboard — made it even cooler and showcased how accessible our platform truly is.
Challenges We Faced (and Learned From)
Rethinking Goodies
Let’s talk about freebies. While they’re a great way to draw people to your booth, we quickly learned that they can also attract the wrong crowd. Some visitors were more interested in our swag than our story. So, we decided to give goodies only to those who genuinely wanted to learn about Qovery—customers, partners, and prospects. A quick 30-second chat was usually enough to tell who was truly interested.
Be Ready To Walk
AWS re:Invent is massive. Coordinating meetings across different venues meant long walks, and I had to cancel a few meetings because of the time it took to get from one place to another. While it’s not always possible to centralize everything, this experience taught me the importance of planning better and maybe prioritizing meetings closer to the booth. (sorry for all I had to cancel 🙏🏼)
No Third Challenge!
Honestly, there’s not much else to criticize. AWS re:Invent is hands down the best event we’ve attended as a team. From the volume of meaningful conversations to the excitement around our demos, it’s clear that this event is a must for us.
Meeting decision-makers from Fortune 500 companies was the cherry on top, and I’m already counting the days to next year’s event.
Wrapping Up
AWS re:Invent 2024 was an unforgettable experience. It reinforced my belief in what we’re building at Qovery and the value we bring to companies struggling with DevOps and infrastructure challenges. The connections we made and the lessons we learned will shape our next steps as a team.
To everyone I met—thank you for taking the time to connect and share your insights. And to those who haven’t experienced AWS re:Invent yet—mark your calendar for 2025. It’s a place where cloud innovation comes alive, and I’m thrilled that Qovery gets to be part of it.
I want to thank our Partner Manager at AWS, Aurore Poirier, who helped us get there. Thank you Aurore!
See you next year!
.svg)
.svg)
.svg)
Suggested articles
The shift from AI copilots to autonomous agents is redefining infrastructure requirements. Discover how to build secure, stateful, and compliant Agentic AI systems using Kubernetes, sandboxing, and observability while meeting EU AI Act standards
Effective Kubernetes management in 2026 demands a shift from manual cluster building to intent-based fleet orchestration. By implementing agentic automation on standard EKS, GKE, or AKS clusters, enterprises eliminate operational weight, prevent configuration drift, and proactively control cloud spend without vendor lock-in, enabling effective scaling across massive fleets.
A Kubernetes single pane of glass is a centralized management layer that unifies visibility, access control, cost allocation, and policy enforcement across § cluster in an enterprise fleet for all cloud providers. It replaces the fragmented practice of switching between AWS, GCP, and Azure consoles to govern infrastructure, giving platform teams a single source of truth for multi-cloud Kubernetes operations.
Deploying a Docker container on Kubernetes requires building an image, authenticating with a registry, writing YAML deployment manifests, configuring services, and executing kubectl commands. While necessary to understand, executing this manual workflow across thousands of clusters causes severe configuration drift. Enterprise platform teams use agentic platforms to automate the entire deployment lifecycle.
At enterprise scale, managing provider-specific Kubernetes YAML across multiple clouds creates crippling configuration drift and operational toil. By adopting an agentic Kubernetes management platform, infrastructure teams abstract cloud-specific configurations (like ingress controllers and storage classes) into a single, declarative intent that automatically reconciles across 1,000+ clusters.
To stop GPU costs from destroying SaaS margins, teams must transition from static to consumption-based infrastructure by utilizing Karpenter for dynamic provisioning, maximizing hardware density with NVIDIA MIG, and leveraging Qovery to tie scaling directly to business metrics.
AI is helping developers write more code, faster than ever. But writing code is only half the story. What happens after? Building, deploying, debugging, scaling. That's where teams still lose hours.We're building Qovery for this era. Not just to deploy your code, but to make everything that comes after writing it just as fast.
.webp)