Northflank review

Northflank is a runtime platform for coding agents, AI-built apps and production workloads. It runs workloads in isolated microVMs and can run on Northflank Cloud, in your own VPC or on-premises. The platform handles builds from Git or container images, then deployment of APIs, frontends and workers. It also offers managed databases, including Postgres, MySQL, MongoDB and Redis, and supports GPU workloads for inference and training.

The pricing page lists a free Sandbox and usage-based paid plans. Sandbox includes 2 services, 2 jobs and 1 database, up to $20/month of Northflank Cloud resources, and one BYOC cluster capped at 12 vCPU and 48 GB. Paid usage starts at $0.01667 per vCPU hour; the listed nf-compute-50 plan costs $12/month. Northflank bills by the second, charges no seat fees and lists no annual billing option.

Northflank’s appeal is breadth: teams can use one platform for remote coding agents, application deployments, databases and GPU workloads, rather than assembling separate services for each job. MicroVM isolation is intended for coding agents and untrusted code, while persistent storage and real compute let agents run remotely. For apps, builds can start from Git or container images and deploy APIs, frontends and workers.

Its infrastructure choices also matter. Teams can use Northflank Cloud, bring their own cloud or run on their own hardware. The pricing page lists one BYOC cluster on the free Sandbox, while Enterprise supports a VPC, on-premises or air-gapped setups. That gives teams a route to start small and keep more control over where workloads run as requirements change.

The free tier is useful for evaluation or small workloads: it has unlimited users and no sleeping, alongside the service, job, database and resource caps. Paid plans also list unlimited users, deployments and workloads, plus GPUs, autoscaling, RBAC and the Platform SDK. That is a practical package for teams that want deployment tooling without per-seat pricing.

“Free” has clear limits: Sandbox stops at 2 services, 2 jobs and 1 database, $20/month of Northflank Cloud resources, and one BYOC cluster with up to 12 vCPU and 48 GB. Beyond that, costs are usage-based, not a predictable flat subscription. The pricing page lists Northflank Cloud CPU at $0.01667/vCPU hour, memory at $0.00833/GB hour, persistent disk at $0.11657/GiB/month and egress at $0.06/GB. GPUs are listed at $0.80–$5.87/hour. The $12/month nf-compute-50 plan is just 0.5 vCPU and 1 GB; other listed compute plans range from $24 to $192/month. Enterprise pricing is custom.

There is also a security concern to investigate. One r/cybersecurity Reddit thread alleged a breach and urged users to rotate environment variables and keys. The published discussion does not establish what happened or what remediation followed, so treat it as an allegation—not confirmation—and seek Northflank’s current security guidance before placing sensitive workloads there.

Northflank has a free Sandbox, but paid usage is not a flat monthly tier. The Sandbox includes 2 services, 2 jobs, 1 database, and up to $20/month of Northflank Cloud resources. It also lists one BYOC cluster, capped at 12 vCPU and 48 GB. Pay as you go starts at $0.01667 per vCPU hour, billed by the second, with no seat fees. That avoids seat-based charges, but does not give you a predictable monthly ceiling. Enterprise pricing is custom; the listed terms include a custom platform fee, usage, support, and SLA.

Compute plans are a separate cost: nf-compute-50 is $12/month for 0.5 vCPU and 1 GB, with four other plans listed from $24 to $192/month. Add-ons can move the bill: persistent disk is $0.11657/GiB/month, egress is $0.06/GB, and GPUs are $0.80–$5.87/hour. The pricing page lists no annual billing option.

Northflank supports deployments from Git or container images and can run on Northflank Cloud, in your VPC, or on your own hardware. That gives teams infrastructure choices, but the published material does not spell out a migration path, data-export process, or which configuration needs rewriting when you leave. Before moving production workloads, confirm how to export database data, preserve persistent storage, and recreate deployment and networking settings elsewhere.

A practical switch is to inventory services, jobs, databases, GPU use, and external dependencies, then estimate each workload separately. That is especially important if you use Northflank-managed databases or platform-specific deployment features. The published source flags security allegations on Reddit but gives no post details or substantiated account of why users leave, so we can’t responsibly summarize those claims. Review the underlying discussions and Northflank’s response before treating them as a reason to switch. If predictable flat-rate costs or published standard support terms are requirements, the published pricing information does not establish that Northflank meets them.