Qovery
Qovery automates cloud infrastructure deployment for regulated companies.
On the record
Checkpoint: 12-month window for Qovery to prove its governance layer is sticky before hyperscalers or rivals match it
The call
Qovery has customers and a fresh raise, but its bet on becoming the required checkpoint for AI-agent infrastructure changes is still just a bet, with Northflank, Render, Railway, and Porter all making the same pitch.
Qovery sells software that lets AI agents safely build and manage computer systems, especially for banks and hospitals that need strict controls. Right now it is hard to copy because Qovery has real customers and working code, but companies like Northflask, Render, Railway, and Porter are selling nearly identical products to nearly identical customers, and AI tools like Claude Code and Cursor can now write the same infrastructure code without needing Qovery at all. The deciding factor: whether Qovery's new governance and safety layer becomes so critical and locked in for highly regulated companies that customers cannot afford to leave, or whether rivals copy it quickly and reduce Qovery to just another choice in a crowded market.
Why
01
AI pressure: Claude Code, Cursor, Codex. These tools already write the Kubernetes and Terraform configs Qovery was built to automate, cutting out the need for its platform entirely. Could AI do the core job? Only partly.
02
Bigger players: AWS, Google Cloud, Azure. If any hyperscaler ships native audit controls for AI-agent infrastructure changes, Qovery's main pitch to regulated buyers disappears. Could a giant copy it? Yes, easily.
03
What protects it. Paying regulated customers who need an audit trail for AI-driven deployments, but this is unproven at scale and matched by rivals' identical pitches.
What would change this call
Northflank, Render, or Railway announces a marquee regulated-industry enterprise customer. Would show rivals matching Qovery's compliance pitch and pulling customers away.
AWS, Google Cloud, or Azure ships native audit/governance controls for AI-agent infrastructure changes. Would remove the need for a third-party governance layer like Qovery.
Qovery announces a Series B round or discloses net-retention figures within 12 months. Would indicate whether investors and customers see the governance-layer thesis holding up.
AWS, Google Cloud, or Azure ships native audit/governance controls for AI-agent infrastructure changes. Would remove the need for a third-party governance layer like Qovery.
Qovery announces a Series B round or discloses net-retention figures within 12 months. Would indicate whether investors and customers see the governance-layer thesis holding up.
Key numbers
- $13M Series A raised, led by IRIS
- 200+ organizations run on Qovery
- 40+ employees across Europe and North America
Named risks
- AI coding agents (Claude Code, Cursor, Codex) can natively generate Kubernetes/Terraform configs, Qovery's original core job.
- Equally-funded peers (Northflank, Render, Railway, Porter) pitch identical governance positioning, risking commoditization.
- Governance/audit moat is new, vendor-claimed and unproven at scale with regulated enterprises.
- Hyperscalers could ship native agent-governance controls, removing need for a third-party layer.
- Small team (40+ employees) and limited disclosed revenue relative to competitive intensity.
Rivals, as read in July 2026
| Rival | Direction | Evidence |
|---|---|---|
| Heroku (Salesforce) | gaining on | Heroku moved to sustaining engineering Feb 2026, no new features or enterprise deals |
| Northflank | contesting | Both push identical BYOC governance pitch for AI-agent infrastructure as of 2026 |
| Render | contesting | Named as direct Kubernetes-abstraction/PaaS competitor as of Sept 2025 |
| Railway | contesting | Named as direct Kubernetes-abstraction/PaaS competitor as of Sept 2025 |
| Porter | contesting | Named as direct Kubernetes-abstraction/PaaS competitor as of Sept 2025 |
| AWS/Google Cloud/Azure | losing to | Hyperscaler native tools (App Runner, Cloud Run) are live substitutes for abstraction-layer PaaS |
Questions people ask
- Is Qovery profitable in 2026?
- Qovery is a private, VC-backed startup with no published profitability data. It closed a $13M ($11.3M) Series A in September 2025 led by IRIS, and reported 115% YoY growth at that time (company-stated), but no audited revenue or profit figures have been disclosed as of 2026.
- Could AI replace Qovery's product?
- Qovery's core job, turning deployment intent into Kubernetes/Terraform config, is exactly what AI coding agents like Claude Code, Cursor, and Codex can now generate directly. Qovery responded by launching a DevOps AI Copilot in November 2025 and an MCP server/Qovery Skill in 2025-2026, positioning itself as a governance layer for agent-driven infrastructure rather than resisting automation.
- Who is Qovery's biggest competitor?
- Qovery competes with Northflank, Render, Railway, and Porter, all pitching similar bring-your-own-cloud governance positioning as of 2026. The incumbent, Heroku (Salesforce), was put into sustaining engineering mode in February 2026 with no new features or enterprise deals, opening market share that Qovery and rivals are actively contesting.
- Who owns Qovery?
- Qovery is privately held and VC-backed, founded in 2020 by CEO Romaric Philogène and Morgan Perry. Its September 2025 Series A was led by IRIS, with participation from Speedinvest, Crane Venture Partners, Techstars, and angels including Datadog co-founders Olivier Pomel and Alexis Le-Quoc and Docker co-founder Sebastian Pahl.
- How much funding has Qovery raised?
- Qovery has raised roughly $18M to $19.9M total across pre-seed, seed, and Series A rounds as of September 2025, including a $13M ($11.3M) Series A closed September 30, 2025, led by IRIS, earmarked for US expansion and AI product development.
- What does Qovery's platform actually do?
- Qovery is a DevOps automation platform that provisions, deploys, observes, secures, and optimizes cloud infrastructure (Kubernetes-based) directly on a customer's own AWS, GCP, or Azure account. By 2026 it rebranded as an 'agentic infrastructure platform,' adding governance controls for AI agents deploying infrastructure.
Timeline
- 2026-07-06Qovery rebrands again as an 'agentic infrastructure platform' with MCP server and Qovery Skill
- 2026-02-09Salesforce puts Heroku into sustaining engineering, no new features or enterprise deals
- 2025-11Qovery launches DevOps AI Copilot for natural-language infrastructure actions
- 2025-09-30Qovery closes $13M Series A led by IRIS, rebrands as 'DevOps automation platform'
- 2025-09-22RxVantage case study published citing 75% faster deployments (vendor-claimed)
- 2024-09-29Alan case study published citing 85% faster deployments (vendor-claimed)
- 2024-08Qovery adds Terraform deployment templates, expanding beyond Kubernetes
- 2020Qovery publicly launches, founded by Romaric Philogène and Morgan Perry
Revision history
22 July 2026
First assessed. Losing its protection. The text above is fixed as of this date and is not edited afterwards.
In the same band
Sources
- Paris-based Qovery lands €11.3 million (2025-09-30)
- Valuation, Funding Rounds & Stock Price (2025-11-13)
- Qovery raises $13M to simplify cloud app deployment (2025-09-30)
- About Qovery
- Qovery - Headcount, Funding & Open Jobs (2026-06-13)
- Our rebrand: setting a new standard for DevOps automation (2025-09-30)
- How the market pulled us into becoming an agentic platform (2026-07-06)
- From a simple CLI PaaS to a unified DevOps Platform (2025-12-28)
- Alan case study (2024-09-29)
- RxVantage case study (2025-09-22)
- Salesforce puts Heroku out to PaaSture (2026-02-09)
- hashicorp/agent-skills: A collection of Agent skills and Claude Code plugins for HashiCorp products · GitHub