Dec 1, live webinar: Agents in production, live: who gives the agent production access?
Qoveryvs.Northflank

Qovery vs Northflank: two ways to run on your cloud.

Northflank runs workloads on Northflank Cloud or in your own cloud account. Qovery is an Agentic DevOps platform that never hosts your apps: they always run in your account.

The shift

One platform hosts or connects. The other only connects.

Northflank and Qovery overlap more than most comparisons in this space. Both can deploy into your AWS, GCP or Azure account and both connect coding agents through an MCP server. Northflank also operates its own managed cloud, Northflank Cloud, and prices compute per second. Qovery has no hosted option. Your apps run on Kubernetes in your own cloud account or on a cluster you already run, and Qovery is priced per plan, with compute billed by your cloud provider.

Who Northflank is best for

Teams that want hosted and BYOC in one product
Start on Northflank Cloud (17+ regions) with no cloud account, then move to BYOC on AWS, GCP, Azure, Oracle, Civo or CoreWeave without changing platform.
Running untrusted code
Northflank Sandboxes run code from users or agents in Cloud Hypervisor microVMs, with gVisor for GPU workloads, on Northflank Cloud or BYOC.
Per-second, per-resource billing
Pay as you go starts at $0.01667 per vCPU hour, billed by the second, with unlimited users. The smallest plan (0.5 vCPU, 1 GB) is $12 a month.
Where Qovery fits
Your apps never run on Qovery infrastructure
Qovery is not a PaaS. Apps, databases, Helm charts and Terraform modules are deployed as one environment on Kubernetes in your AWS, GCP, Azure or Scaleway account.
A cluster you already run, on every plan
The Qovery Operator connects an existing cluster (EKS, GKE, AKS, k3s or on-premise, Kubernetes 1.31+). The Free plan covers one such cluster with no credit card.
Plan pricing, not per-resource fees
Qovery plans are priced per month with included users, clusters and deployment minutes. Your cloud provider bills the compute directly, with no extra fee per vCPU.
Agents scoped like engineers
Agents work through Qovery Agent Skills, the MCP Server or the CLI, with their own scoped API tokens. They do not take a user seat, and every action is audited.
Detailed comparison

How they stack up.

A side-by-side look at what each platform delivers - including the AI capabilities that define modern infrastructure.

Qovery
Northflank
What it is
Agentic DevOps platform. Engineers and coding agents deploy and operate apps on Kubernetes in your own cloud account. Qovery is not a PaaS and does not host your apps.
"The runtime platform for autonomous software": services, jobs, databases, GPUs and microVM sandboxes.
Where your apps run
Your apps run in your own AWS, GCP, Azure or Scaleway account, or on a Kubernetes cluster you already run (EKS, GKE, AKS, k3s, on-premise) through the Qovery Operator.
Northflank Cloud (17+ regions), or your own cloud account with BYOC. On-premise and bare metal are also mentioned.
Your own cloud account
Always. There is no Qovery-hosted option. Clusters can be created by Qovery in your account or connected with the Qovery Operator.
BYOC on AWS, GCP, Azure, Oracle, Civo and CoreWeave, plus importing an existing cluster (BYOK). Workloads and data stay in your cloud, and the Northflank control plane manages deployments.
Pricing model
Free: $0, 3 users plus unlimited AI agents, 1 cluster of your own, 1,000 deployment minutes a month, no credit card. Starter $299, Growth $899, Scale $2,999 per month billed yearly. Enterprise priced to your team. Compute is billed by your cloud provider.
Pay as you go from $0.01667 per vCPU hour and $0.00833 per GB of memory per hour, billed by the second, unlimited users. BYOC fee of $0.02083 per node vCPU per hour. Enterprise on custom pricing.
Free option
Free plan: 3 users plus unlimited AI agents, 1 cluster of your own, 1,000 deployment minutes a month. No time limit, no credit card.
Sandbox tier: 2 services, 2 jobs and 1 database, up to $20 a month of resources on Northflank Cloud, 1 BYOC cluster up to 12 vCPU and 48 GB. No card needed.
Workloads
Applications, databases, Helm charts and Terraform modules deployed as one environment. Preview environments and environment cloning on every plan.
Services, jobs, preview environments, pipelines and release flows, GPUs (L4, A100, H100 billed by the hour). Templates as infrastructure as code with GitOps sync. Custom Helm addons in your own cloud only.
Databases
Databases deployed in the same environment as your apps, inside your cloud account.
Addons for PostgreSQL, MySQL, MongoDB, Redis, MinIO, RabbitMQ and Memcached.
Coding agents
Qovery Agent Skills, MCP Server and CLI for Claude Code, Cursor, Codex and others. Agents use their own scoped API tokens, do not take a user seat, and every action is audited.
MCP server for Claude Code, Codex, Cursor and OpenCode, plus API and CLI. MicroVM sandboxes for untrusted code.
Compliance
Workloads and data stay in your cloud account. SOC 2 Type II report and DPA on Scale, HIPAA add-on with a BAA on Scale, HIPAA, HDS, ISO 27001 and DORA package on Enterprise.
SOC 2 Type II, ISO 27001, and HIPAA with BAAs.

Pricing and features checked on 22 Nov 2026, sources: Northflank pricing, BYOC and BYOK requirements, Bring your own cloud, Databases, MCP server, Sandboxes, Security. Qovery prices from qovery.com/pricing.

Fair comparison

When Northflank is the better choice.

Northflank covers cases Qovery does not. If one of these is the main requirement, Northflank is a reasonable pick.

No cloud account yet

Qovery needs your cloud account or your cluster. Northflank Cloud runs workloads before you have either, and BYOC is there when you are ready.

Sandboxes as the product

If you run code from end users or agents and need microVM isolation, Northflank Sandboxes do that. Qovery is not an execution sandbox.

GPUs by the hour on a managed cloud

Northflank lists hourly L4, A100 and H100 prices on Northflank Cloud. With Qovery, GPUs come from your own cloud account.

Migration

Moving from Northflank Cloud to your own account

An agent reads your repository and deploys it into the AWS, GCP, Azure or Scaleway account you already own, after you approve the plan.

Move to your own cloud

Qovery vs Northflank

Does Northflank run in my own cloud account?
Yes, with BYOC. Northflank documents bring your own cloud on AWS, GCP, Azure, Oracle, Civo and CoreWeave, and importing an existing Kubernetes cluster. Workloads and data stay in your cloud while the Northflank control plane manages deployments. Northflank also runs its own managed cloud, Northflank Cloud. Qovery has no hosted option: your apps always run in your own cloud account or on a cluster you already run.
What is the main difference between Qovery and Northflank?
Northflank is a runtime platform that can host your workloads or run them in your cloud. Qovery is an Agentic DevOps platform and not a PaaS: it never hosts your apps. Engineers and coding agents deploy and operate apps on Kubernetes in your own AWS, GCP, Azure or Scaleway account, or on an existing cluster through the Qovery Operator. Pricing also differs: Northflank charges per resource and adds a BYOC fee per node vCPU hour, while Qovery charges per plan and your cloud provider bills the compute.
How much does Qovery cost?
As of 22 Nov 2026, Qovery has a Free plan at $0 with 3 users, unlimited AI agents, one Kubernetes cluster you already run and 1,000 deployment minutes a month, with no credit card and no time limit. Paid plans are Starter at $299 a month, Growth at $899 a month and Scale at $2,999 a month, billed yearly (monthly billing has no commitment), and Enterprise is priced to your team. Your compute, databases and network are billed by your own cloud provider, because they run in your account. Current prices are on qovery.com/pricing.
When is Northflank the better choice than Qovery?
When you do not have a cloud account yet and want a managed cloud to start on, when running untrusted code in microVM sandboxes is the product, or when you want hourly GPUs on a managed cloud. Qovery needs your own cloud account or cluster, and it is not an execution sandbox.
Can I try Qovery without a cloud account?
Yes. qovery demo up creates a local k3s Kubernetes cluster in Docker on your laptop (macOS, Linux, or Windows with WSL), installs the Qovery Operator and lets you deploy in minutes. It counts as the one cluster on the Free plan and is meant for trying Qovery, not for production.

Built for what's next

Both platforms let a coding agent deploy.
The difference is where it runs.

The difference is where the result lives. With Qovery it is always your cloud account, under your RBAC, with every agent action attributed in the audit log. Start on the Free plan with a cluster you already run, or try it on your laptop with qovery demo up.