What's new in Qovery for August 2021?
By taking watching our Community Call August 2021 recording, you can expect to:
Get a quick introduction to Qovery.
Thanks to our community for being super supportive and active. Helping each other is a core value of Qovery and our community. Thank you so much for being here.
Announcing our brand new logo 😍
Thanks to Dmitry Lepisov for his great work. Take a look at his Dribbble. He is talented and works with great companies.
Manage your organization settings ✅
To go beyond app deployment, we plan to launch very soon organization settings that will let you:
- Configure Qovery to run on your AWS account.
- Invite your teammates to your organization.
- See how many credits remain in your account (Community).
- Manage your payment.
Community question: how do we manage our work like champions 😎
I show how we prioritize tasks with Atlassian Jira and gather feedback from the community via our public roadmap.
Live demo: Edit your code with Github Codespaces, deploy with Qovery 🍃
TLDR; Github Codespaces is a Web IDE - it is "VSCode" in your web browser.
12 years ago, when I started to work as a Developer, I would not have bet that I would write software and manage infrastructure right from my browser one day. At the time, web IDE did not exist. And managing infrastructure from the browser was super early. Today, it is all possible, and the future looks bright!
During this live demo, I show how to:
- Deploy an application with Qovery 👌
- Edit the code from my browser with Github Codespaces. 🙆🏻♀️
- Auto-deploy my changes with Qovery 🚀
Note: we also integrate Gitpod to edit your code in Gitlab.
DX improvements
We talk and show Developer Experience improvements we are currently working on.
--
I hope you enjoyed it. Join our growing dev community on Discord and our Forum.
.svg)
.svg)
.svg)
Suggested articles
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.
By adopting GitOps and utilizing management platforms like Qovery, fintech teams can automatically generate DORA-compliant audit trails, transforming regulatory compliance from a manual, time-consuming chore into an automated, native byproduct of their infrastructure.
Kubernetes success is determined by Day 2 execution, not Day 1 deployment. While migration is a bounded project, maintenance is an infinite loop that often consumes 40% of senior engineering capacity. To protect margins and velocity, enterprises must transition from manual toil to agentic automation that handles scaling, security, and cost.
Day-0 is planning, Day-1 is deployment, and Day-2 is the infinite lifecycle of maintenance. While Day-0/1 are foundational, Day-2 is where enterprise operational debt accumulates. At fleet scale (1,000+ clusters), managing these differences manually is impossible, requiring agentic automation to maintain stability and eliminate toil.
.webp)