Ankra vs Northflank

Two platforms, different scope

Northflank runs services, jobs, databases and preview environments on Northflank’s cloud or in your own cloud account. It is polished for developers, and strong on running untrusted code, with microVM sandboxes for AI-generated code.

Ankra covers that ground and the platform underneath it. It builds the Kubernetes cluster on the provider you pick or takes the one you already run, ships your code to it, and keeps operating everything on it with vulnerability ranking, cost, backups and AI that waits for your approval.

The biggest differences are where the cluster can come from, how much of the work after the first deploy is built in, and what the platform holds.

Where the cluster comes from

Northflank creates clusters in your account on EKS, GKE, AKS, Oracle OKE, Civo, CoreWeave, Nebius and AWS European Sovereign Cloud, and on Enterprise it lists fully managed clusters on bare metal. Anything else is imported, and its import requirements are strict. The cluster must use Cilium as its CNI, Northflank strongly recommends importing a new, dedicated cluster, and it says not to import clusters that run production workloads. It does not provision infrastructure for imported clusters, so their node pools are not autoscaled.

Ankra builds kubeadm or k3s clusters on Hetzner, OVHcloud, UpCloud, DigitalOcean, AWS EC2 and Proxmox VE, with a private network, a bastion and the storage driver. It creates EKS, GKE, AKS, DOKS, OVHcloud MKS and UpCloud UKS. And it imports any conformant cluster with one Helm command, production clusters included. The agent only connects outbound, so the cluster can stay behind a firewall or NAT.

If your plan is Hetzner, OVHcloud, UpCloud, Proxmox VE or the production cluster you already run, Northflank leaves that cluster to you outside Enterprise. Ankra builds it, or takes it as it is.

After the first deploy

Most of a cluster’s life comes after it is created. On clusters it builds, Ankra runs in-place Kubernetes upgrades with etcd snapshots, node groups, node autoscaling and power schedules that stop a cluster outside working hours. Cluster Mesh connects services across clusters with Cilium ClusterMesh over Ankra’s WireGuard overlay.

Shipping your code

Both products take a repository to a running service with pull-request previews. Northflank builds from a Dockerfile or Buildpacks, runs Workflows built in a visual editor with approval nodes, and provisions full-stack preview environments for pull requests.

Ankra’s Applications read your repository and open a setup pull request with the Dockerfile, chart and pipeline. Ankra Pipelines run in your own cluster, with tests, rootless builds and Semgrep, Checkov and Trivy scans, then a gate that decides which image may be published.

• Build once. A merge that carries exactly what a pull request run already built, scanned and tested publishes that tested image instead of rebuilding it.
• A merge train. The merge train tests each GitHub pull request as the exact commit its merge will produce, so two green pull requests cannot break the main branch together.
• Signed provenance. With verified provenance, an application refuses any image that your organisation’s pipeline gate did not publish, such as one built on a laptop or pushed by hand.
• Previews. Pull-request previews give each change its own environment.

Pipelines trigger on GitHub, GitLab and Bitbucket Cloud. Applications and previews start from GitHub repositories.

Platform add-ons and fleets

Northflank’s templates are edited as JSON with two-way Git sync, and cover its own services and add-ons.

Ankra’s stacks install any Helm chart or manifest in dependency order, so the database comes up before the service that needs it, and deploy waves order whole stacks. The catalogue covers ingress, cert-manager and monitoring, and security building blocks such as External Secrets, Sealed Secrets, Vault and Kyverno. Stack profiles version a setup and roll each new version across a fleet of clusters, and two-way GitOps keeps every change as a commit in your repository.

Data and backups

Northflank’s managed databases are a strength, with PostgreSQL, MySQL, MongoDB, Redis, MinIO and RabbitMQ and automatic backups.

Ankra protects stacks on a schedule into a bucket you own. The cluster writes its volumes and databases straight to the bucket, and the platform never holds the data. Restore points restore a stack in place, a stack can be cloned to another cluster with its data, and ankra migrate moves a Docker Compose deployment onto Kubernetes with its PostgreSQL, MySQL or MariaDB data. Ankra’s own managed services, PostgreSQL, Valkey, NATS, OpenSearch and S3-compatible storage among them, run on your cluster and are in closed beta.

Security of what runs

Northflank isolates workloads in Kata Containers microVMs by default. Its container scanning finds vulnerabilities and secrets in images you build on Northflank, once you enable it on a build or service, and for new builds only. Enterprise adds automatic scanning with policy enforcement.

Ankra’s Security Center reads the vulnerabilities in what is actually running across your clusters, including images Ankra never built, once the security baseline is on. It ranks them by CISA’s Known Exploited Vulnerabilities catalogue and FIRST’s EPSS scores, so the ones attackers use come first, and it scores how far each cluster’s network policies over-allow traffic. Compliance Management scores the fleet against CIS, NSA/CISA and the Pod Security Standards, tracks exceptions with owners and review dates, and produces an evidence report. Ankra’s security and compliance material is on its trust page.

Secrets, and the October 2026 incident

On 30 October 2026 Northflank disclosed a security incident after a threat alert from Wiz. Its status page told customers to “Assume all environment variables have been decrypted. Disable/rotate all keys.” It later wrote that “Users have reported unauthorised use of AI API keys supplied to the Northflank platform”, and on 31 October it enabled audit logs for all customers, including free users. On 2 November it moved the incident to monitoring. It said it believes the attack vector was contained within an hour, that the attack was focused on secrets held in its control plane and did not reach running workloads, that customers on forward-deployed or dedicated control planes were unaffected, and that it had patched CVE-2026-98432 across its fleet. It intends to share a root cause analysis once its findings are confirmed. Wiz counts it among at least nine incidents at AI developer platforms in October 2026, with attackers hunting stored environment variables that grant AI access.

If you used Northflank, rotate first. Revoke each key with the provider that issued it, not only in Northflank, and check your AI providers’ usage and billing for activity you did not start.

Then ask every platform, Ankra included, what it holds. Ankra answers on one page, What Ankra can see and do.

• Ankra’s inventory holds digests, not values. The agent replaces every Secret value with a SHA-256 digest before cluster data leaves the cluster, and the AI never sees the values. Reading one takes its own permission, and each reveal is written to the audit log, which is kept for 365 days.
• You choose what the platform holds. Your workloads run in your own cluster, so their secrets can be created there or synced from your own secret manager with External Secrets or Vault. Ankra’s inventory then holds only their digests.
• Ankra’s AI starts without your AI key. By default it runs on Ankra’s own model key within your plan’s monthly allowance. Past that, you connect your own provider key or your own endpoint.
• Pipeline secrets are files, not environment variables. A pipeline secret arrives as a file at run time, reaches only the stages that list it, is never written into the pipeline itself, and pull requests from forks get none.
• What you give Ankra is sealed. Cloud, Git and registry credentials, and your organisation’s SOPS key for Git, are stored encrypted in an OpenBao or HashiCorp Vault secret store in the EU and decrypted only when an action needs them. Values you store with ankra secrets go in and never come out.

Cost

Ankra’s Cloud Cost shows spend per cluster, namespace and stack, points out waste and savings, sets budgets, and reprices a whole cluster on other providers before you move it. Northflank bills usage to the second, with no seat fees.

AI that runs code, or AI that runs the platform

Northflank’s AI work gives agents a safe place to run. Sandboxes execute AI-generated code in microVMs, Cloud Harnesses run coding agents such as Claude or Codex, and an MCP server lets your coding agent deploy and inspect resources.

Ankra’s AI operates the platform. The assistant answers from your clusters, AI Insights analyses every firing alert, the AI board runs work through role agents with a person approving, and the AI Gateway reviews pull requests and opens fix pull requests. Every write waits for a person by default, and the MCP server gives your own agents more than 450 tools across the same operations.

Price

For clusters in your own cloud, Northflank’s pay-as-you-go plan charges $0.02083 per node vCPU an hour. On Northflank’s own cloud it charges $0.01667 per vCPU and $0.00833 per GB of memory an hour, compute included.

Ankra charges €0.01 per worker vCPU an hour on the Startup plan. The first 30 worker vCPUs are free on every plan, and controller nodes are never billed. Your provider bills the servers.

When to choose Ankra, and when to choose Northflank

Choose Ankra when you want Kubernetes on Hetzner, OVHcloud, UpCloud, DigitalOcean or your own servers built and operated for you, need to bring production clusters you already run, want the vulnerabilities attackers exploit found across every cluster, or want security, cost, backups and AI operations in the same product as delivery.

Choose Northflank when

• you want to run on Northflank’s own cloud, with no cluster of your own
• managed databases are the centre of your stack
• you want approval steps inside visual release workflows today
• you run untrusted or AI-generated code that needs microVM isolation

Compare the work that remains

1. Create the foundation. On your target provider, record who builds the cluster and who scales its nodes.
2. Bring what you run. Try to import a production cluster and note what each platform asks you to change first.
3. Ship a release. Include tests, scans, a preview and a rollback.
4. Add a platform component. Install an operator or monitoring stack and note how it is versioned across clusters.
5. Investigate a vulnerability. Find every affected workload, across every cluster.
6. Rotate a secret. Note every place the platform kept a copy of it.
7. Compare total cost. Include the infrastructure, the platform fee per vCPU and the work each route leaves to you. See Northflank’s pricing and Ankra’s pricing.

Reviewed 2 November 2026 against Northflank’s documentation, pricing, security page and status page. Product scope and plans can change.