Application hosting / PaaS: read the guide
Scanned 7 Oct 2026 · Schema v5 · features v21
- From
- Free
Usage-based, billed per second (prorated) on Northflank Cloud: vCPU + memory + GPU + disk + egress. Predefined compute plans are priced per container. No seat pricing ('Teams included for free'). Tiers: Sandbox (free), Pay-as-you-go, Enterprise (custom, invoice, annual commit). BYOC adds no per-resource Northflank compute charge.
- Free tier
- Yes
Yes: 'Sandbox' tier ('for testing and building trust with Northflank'): always-on compute (no sleeping), 2 free services, 1 free database, 2 free cron jobs, 2 projects, limited compute; free projects support one Cloud Harness.
- Isolation
- Kata / gVisor
hardened or user-space kernel
- Regions
- 17
EMEA (africa-south) · Asia Pacific (asia-east) · Asia Pacific (asia-northeast) · Asia Pacific (asia-south-delhi) · Asia Pacific (asia-southeast) · Asia Pacific (australia-southeast) +11
- Capabilities
- 30 / 61
12 partial · 19 fail · 0 not assessed
- Agent readiness
- 9/11 · 8.5/11
read · drive, pre-login surface
Advertised for
Services (long running, combined/build/deployment) · Jobs (one off + cron) · Addons / managed databases + queues (Postgres, MySQL, MongoDB, Redis, RabbitMQ, Memcached) and object storage buckets · Sandboxes (microVM, untrusted / agent code, sub second boot) · Cloud Harness coding agent workspaces · GPU workloads (inference, training, notebooks) · Preview environments · Workflows / release flows · Volumes
Built for
Developers, then technical
- · API / CLI / JS + Python SDK / GitOps / Dockerfile-first onboarding
- · microVM, Kata, gVisor, BYOC, Kubernetes, VPC vocabulary
- · usage-metered per-second pricing with compute plans
01 Pricing Usage-based, billed per second (prorated) on Northflank Cloud: vCPU + memory + GPU + disk + egress. Predefined compute plans are priced per container. No seat pricing ('Teams included for free'). Tiers: Sandbox (free), Pay-as-you-go, Enterprise (custom, invoice, annual commit). BYOC adds no per-resource Northflank compute charge.
| Tier | EntrySandbox (free) | Pay-as-you-go | TopEnterprise |
|---|---|---|---|
| Price | $0/mo | from $0/mo + usage | custom |
| Includes | 2 services, 2 jobs, 1 addon, 2 projects, limited compute, always-on; 1 Cloud Harness | Unlimited projects/services/jobs/addons/users; usage per second: vCPU $0.01667/hr, memory $0.00833/GB/hr, disk $0.15/GB-mo, egress $0.06/GB; GPUs L4 $0.80/hr -> RTX PRO 6000 $3.00/hr; 6+ cloud regions, 600 BYOC regions | Run in your VPC, 24/7 support + SLA, FDE onboarding, SSO SAML/OIDC, audit logs, global backups + HA/DR, white-label, BYO registry/Vault/DNS, self-deployable control plane, HIPAA BAA, invoice billing, volume discounts, annual commitment |
| Transfer overage | — | $0.06/GB | — |
| Storage overage | — | $0.15/GB | — |
| vCPU hours overage | — | $0.01667/h | — |
| Memory gb hours overage | — | $0.00833/h | — |
Free tier: Yes: 'Sandbox' tier ('for testing and building trust with Northflank'): always-on compute (no sleeping), 2 free services, 1 free database, 2 free cron jobs, 2 projects, limited compute; free projects support one Cloud Harness.
per vCPU-hour + per GB-memory-hour + per GPU-hour + per GB-month disk + per GB egress·Card required: No·northflank.com
Overages: vCPU $0.01667/hr; memory $0.00833/GB/hr; disk (SSD/HDD) $0.15/GB-mo; egress $0.06/GB (ingress free; cross-zone $0.02/GB with zonal redundancy). GPUs: L4 $0.80, A100-40 $1.42, A100-80 $1.76, H100 $2.74, RTX PRO 6000 $3.00 per hour. The June read's 'builds & backups $0.08/GB-mo' and 'logs & metrics $0.20/GB (first 10 GB free)' lines are no longer on the page.
02 Runtime Each fact carries its source; dots show confidence. Open a row for the evidence.
Isolation & lifecycle
Isolation primitive
Kata / gVisorhardened or user-space kernel
Persistence
Persistent volumes ($0.15/GB-month SSD or HDD), incl. ReadWriteMany (RWX) multi-read-write volumes, now direct-mounted inside microVM guests; per-replica volumes for stateful sets; scheduled volume backups; managed addons (Postgres/MySQL/MongoDB/Redis/RabbitMQ) keep data. Sandbox ephemeral storage is lost on pause unless a volume is attached; Cloud Harness persists /home/harness by default.
Snapshots / forks
Container snapshots (Aug-Sep 2026): capture the FILESYSTEM of a running or terminating service pod and restore a service from it (dashboard/CLI/API; requires the Kata runtime). Plus database fork ('create a new database from the existing state of another'), volume backup/clone incl. cross-namespace clone. No memory/process snapshot.
Resources & limits
Storage
Persistent volumes incl. RWX at $0.15/GB-month; managed S3-compatible object storage buckets with automatic domain allocation (May-June 2026, the off-ramp from MinIO addons); managed Postgres/MySQL/MongoDB/Redis/RabbitMQ/Memcached addons; backups (snapshot/dump, global backups to your own S3 incl. Object Lock).
Limits & quotas
Compute plans from nf-compute-10 (0.1 shared vCPU / 256 MB, $2.70/mo) to 32 vCPU / 488 GB ($3312/mo); CPU scales 0.1-32 vCPU, memory 256 MB-256 GB; custom plans on request / any size on BYOC. Free 'Sandbox' tier: 2 services, 2 jobs, 1 addon, 2 projects, limited compute, one Cloud Harness. API: 1000 requests/hour default with x-ratelimit-limit/remaining/reset headers.
GPU
Yes: NVIDIA L4 24GB $0.80/hr, A100 40GB $1.42, A100 80GB $1.76, H100 80GB $2.74, RTX PRO 6000 96GB $3.00 (rendered prices). H200 141GB and B200 180GB appear in the pricing-calculator catalogue without a rendered price. GPU sandboxes run under gVisor and need a GPU-enabled region; time-slicing and MIG supported.
Access
Deploy interface
UI dashboard, REST API (OpenAPI 3.0.1), CLI (@northflank/cli 0.13.0), JS + Python SDKs, bi-directional GitOps, Git-connected builds (GitHub, GitLab incl. self-hosted, Bitbucket, Azure DevOps, Gitea, GitHub Enterprise, Cursor Origin), source-bundle builds, Dockerfile/buildpacks, external registry images, IaC templates, GitHub Action
SDK languages
JavaScript/TypeScriptPython
Network & secrets
Egress controls
Network policies with ingress AND egress allow/deny rules ('If you add any egress rule, it becomes an allow-list and only specified traffic is permitted'), managed from the dashboard (May-June 2026) and API; Cilium namespace isolation by default; static egress IPs (shared or dedicated) via Cilium egress gateway; Tailscale integration.
Secrets
Runtime-variable and build-argument secret injection (kept out of Kubernetes), secret files with Unix ownership/mode, secret groups restricted by tags/environments, global secrets with version history, external secret managers (Vault, beta), customer-managed envelope encryption with your own cloud KMS key (Aug-Sep 2026), addon credential rotation.
Bring your own cloud
Yes: AWS (EKS, incl. AWS EU Sovereign Control Plane), GCP (GKE), Azure (AKS), Oracle (OKE), CoreWeave, Civo, Nebius, or any Kubernetes / bare metal / OpenShift / RKE2. 'No added cost for running in your VPC.' Kata microVM / gVisor sandboxing self-service on BYOC (Aug-Sep 2026); Enterprise adds a self-deployable control plane and BYO registry/Vault/DNS/logs/metrics.
Placement & use
Jurisdiction
UK company (Northflank Ltd, London). Control plane on Google Cloud London or Amsterdam. Managed worker clusters: free tier on Azure, paid tier on GCP, in 17 user-selected regions (Americas, EMEA, Asia Pacific); region fixed per project. BYOC runs in the customer's own account/region.
Advertised workloads
Services (long running, combined/build/deployment)Jobs (one off + cron)Addons / managed databases + queues (Postgres, MySQL, MongoDB, Redis, RabbitMQ, Memcached) and object storage bucketsSandboxes (microVM, untrusted / agent code, sub second boot)Cloud Harness coding agent workspacesGPU workloads (inference, training, notebooks)Preview environmentsWorkflows / release flowsVolumes
03 Capabilities 30 pass · 12 partial · 19 fail · 61 of 61 assessed
- Supported — Documented on the public surface and verified.
- Partially supported — Exists with caveats: gated, thin, or enterprise-only.
- Not supported — Checked and not offered.
- Not assessed — Scanned before this capability was tracked. Not a lack.
Compute & storage 6/11
Persistent diskStorage that survives restart/stop (not ephemeral-only).
Supported
Object storageManaged S3-compatible / blob object store the platform PROVIDES to a user's workloads (buckets, presigned URLs). DISTINCT from persistent-disk (block/volume attached to an instance) and from a self-host dependency (source.self_host.deps[]=["object-storage"] is an infra dep to RUN an OSS tool — the opposite direction). SCOPE varies and matters: native first-class (Railway Buckets, Cloudflare R2) vs a sibling SKU / extension (Fly Tigris, Bunny Storage, DigitalOcean Spaces) — record which in the evidence quote / note. Admitted v15.
Supported
Snapshots / forkingSnapshot or copy-on-write fork of a running instance (filesystem-only counts). Whether the snapshot also restores memory + running processes is recorded separately by memory-snapshot (v19).
Supported
Live-state (memory) snapshotsA snapshot / checkpoint / pause captures a running instance's MEMORY and PROCESS state and restores it, so running processes continue where they left off instead of a freshly booted instance with the same files. Counts whether user-triggered (snapshot, checkpoint, pause-to-storage) or used to restore pre-initialised state (memory snapshots for fast cold starts). Distinct from snapshots-forks (any snapshot or fork, including filesystem-only; a product passing that key may still fail this one) and from scale-to-zero (an idle-cost property; suspension may or may not keep memory). Actor multiplexing (see scale-to-zero) records its live-state half here — only when the suspended actor's MEMORY/process state is what comes back, not a freshly booted worker with the actor's files.
Not supported
Scale to zeroIdle instances suspend at no / negligible cost. ACTOR MULTIPLEXING (many suspended stateful actors sharing a small pool of pre-warmed workers, woken on request — Agent Substrate, AX, kagent; Rivet's hibernating actors) has NO key of its own (proposal REJECTED v20) — score the idle-cost half HERE and the live-state half under memory-snapshot; the oversubscription ratio / density is a performance characteristic the registry does not key.
Partially supported
GPU computeGPU-backed instances available.
Supported
Multi-regionCompute placeable in more than one geographic region.
Supported
Sandbox templates / custom imagesBuild reusable sandbox/VM images from an OCI image or Dockerfile (a base you fork instances from).
Supported
Cloud-init / ignition configCustomise a VM / microVM / instance at boot via cloud-init (or ignition) user-data — the same boot-metadata interface as AWS/Azure/GCP. Inject packages, users, SSH keys, files, and run-commands declaratively at launch. Distinct from sandbox-templates (a PREBUILT image you fork instances from) — this is PER-LAUNCH declarative customisation, not a baked image.
Partially supported
Desktop / computer-use sandboxA virtual desktop (GUI) for LLM computer-use — browser + desktop automation, often via noVNC/VNC.
Not supported
Selectable isolation runtimeThe user chooses the isolation runtime per workload / environment / sandbox from more than one option (e.g. microVM vs gVisor vs plain container, native namespaces vs gVisor, gVisor vs VM). Records the CHOICE; the isolation_primitive facet still records the best-evidenced primary. A platform that switches runtime automatically without a user choice (e.g. gVisor forced for GPU) does not pass on that alone.
Partially supported
Networking & delivery 6/9
Automatic HTTPSTLS endpoints provisioned automatically per workload.
Supported
Built-in reverse proxyPlatform routes external traffic to workload services.
Supported
Custom domainsBring-your-own domain via CNAME/DNS.
Supported
Public preview URLsShareable per-deploy / per-branch URLs.
Supported
Direct public IPv6Per-instance stable public IPv6 for raw TCP/UDP (beyond a managed HTTPS proxy) — e.g. mosh / raw sockets.
Not supported
Egress controlsConfigurable OUTBOUND network policy — egress firewall / allowlist / egress proxy on traffic LEAVING a workload. Scoped to OUTBOUND only (v15): private-network REACHABILITY between a user's own services is private-networking, not this. Static-egress-IP belongs here (an outbound concept).
Supported
Private networkingA platform-internal private network between a user's OWN services — service-to-service connectivity, VPC, service mesh, and/or service discovery, not exposed to the public internet. DISTINCT from egress-controls (OUTBOUND firewall/allowlist), reverse-proxy (PUBLIC inbound ingress), and direct-ipv6 (per-instance PUBLIC addressing). Admitted v15.
Supported
Email send / receiveSend and/or receive email from the workload.
Not supported
Edge KV storeA globally-replicated key-value store read from WITHIN an edge runtime at the PoP (low-latency, eventually-consistent) — Cloudflare Workers KV, Deno KV, Fastly KV Store, Akamai EdgeKV, Vercel Edge Config. Distinct from first-party-db (a managed DATABASE service you provision and connect to) and from http-query-api (HTTP access to an external store) — edge-kv is colocated with the edge compute and read at the edge.
Not supported
Developer access 6/10
Public APIDocumented programmatic API.
Supported
OpenAPI specMachine-readable OpenAPI / Swagger spec published.
Supported
CLIOfficial command-line tool.
Supported
SDKOfficial client library/libraries.
Supported
SSH accessDirect SSH into workloads.
Supported
Filesystem APIRemote file operations over the API (list/read/write/watch/copy/upload) without SSH.
Partially supported
Git deployDeploy from a Git repo / push-to-deploy.
Supported
Private container registryHosted private image registry.
Partially supported
E2B-compatible APIDrop-in compatibility with the E2B sandbox API/SDKs — existing E2B client code runs against this product by changing the endpoint/domain + key, with no business-code changes. E2B itself passes as the reference implementation. Distinct from public-api / sdk (the product has its own API — this key says it also speaks another vendor's) and from self-host-oss (a self-hosted E2B-compatible server is scored on both).
Not supported
HTTP data APIQuery / read / write the stored DATA over plain HTTP/REST (or GraphQL) WITHOUT the native protocol driver (Postgres wire / Redis RESP) — agent- and edge-friendly data access via fetch(). The DATA plane; distinct from public-api (a control-plane / management API). Auto-generated-from-schema REST/GraphQL (PostgREST, pg_graphql) is a flavour of this.
Not supported
AI & agents 3/12
Built-in coding agentShips a first-party AI coding agent in the product.
Not supported
Agent skillsInstallable / declarable agent skills or tools.
Supported
AI app builderPrompt-to-app / vibe-coding generation surface.
Not supported
MCP serverExposes a Model Context Protocol server for agents.
Not supported
MCP clientActs as an MCP client / consumes MCP tools.
Not supported
MCP-server hostingRun/host MCP servers as a workload on the platform (distinct from exposing a first-party MCP control server — that is mcp-server).
Supported
LLM gatewayRoutes LLM API calls through the platform (multi-provider).
Not supported
BYOK for LLMsBring-your-own LLM provider keys.
Partially supported
Model inference API (first-party)A FIRST-PARTY hosted LLM/model inference API — the provider serves its OWN catalogue of (usually open-weight) models behind a (typically OpenAI-compatible) endpoint, billed per token. Distinct from llm-gateway (a multi-PROVIDER proxy/router for YOUR calls to external providers like OpenAI/Anthropic) and from byok-llm (bring your own provider keys) — here the platform IS the inference provider, serving its own models.
Not supported
Autonomous QA agentA first-party AUTONOMOUS AI agent that QA-TESTS a running app / implementation — exercising it like a real user (clicking through flows, checking behaviour) and reporting bugs/defects (often back to a coding agent, or before a human review). Distinct from built-in-agent (a code-AUTHORING agent — this one VERIFIES the result, it does not write the feature; a product can ship both), from ai-guided-code-review (organises a diff for a HUMAN to review — not an autonomous tester), and from observability (runtime metrics/logs, not active testing).
Not supported
Credential-injection proxyThe platform holds real secrets OUTSIDE the workload and injects them on the wire (an egress / broker proxy swaps a placeholder or phantom token for the real credential on matching outbound requests), so code running in the sandbox — e.g. an untrusted agent — never sees or can exfiltrate the real key. Distinct from secrets-management (storage + injection INTO the workload as env vars/files — the workload holds the secret) and from egress-controls (outbound allow/deny POLICY; a product can have an allowlist without injecting credentials, and vice versa).
Not supported
Preinstalled coding agentThe platform installs and launches a THIRD-PARTY coding agent (a harnesses.yml entry — Claude Code, Codex, OpenCode, Pi ...) inside a workspace/sandbox it provisions, with the agent's auth wired in (your own account or API key), so you start an agent session rather than an empty box. Distinct from built-in-agent (a FIRST-PARTY agent the vendor ships) and from harnesses[] (which records that a harness CAN target the product, not that the product runs it for you).
Supported
Data 1/4
First-party databasePlatform-provided managed database.
Supported
Database branchingCopy-on-write branch of a DATABASE (schema + data) as a dev-lifecycle primitive — branch your data like code, usually instant via a metadata operation. Distinct from snapshots-forks (forks a running compute INSTANCE / VM state) and from preview-environments (a full per-PR environment that may USE a DB branch). For a data product a CoW branch maps HERE, not to snapshots-forks.
Partially supported
Vector searchFirst-class storage, indexing, and similarity search of vector embeddings — a native vector type/index or a managed vector DB. The data-layer primitive for RAG / semantic retrieval.
Partially supported
Ephemeral instant DB (no-signup)Provision a working, usable instance via a single command / HTTP call with NO account, signup, or card — typically time-boxed (expires unless claimed). A zero-onboarding path an agent can hit directly.
Not supported
Platform & operations 3/6
Scheduled tasksCron / scheduled job primitive.
Supported
Durable workflowsDurable execution / long-running workflow primitive.
Partially supported
Preview environmentsA full EPHEMERAL environment spun up per PR / branch — compute + addons + (often) a DB branch — torn down on merge. More than preview-urls (which is just a shareable URL for one deploy).
Supported
Built-in observabilityFirst-party metrics / logs / tracing / APM / profiling included in the platform (no third-party stack required to see what a workload is doing).
Supported
Managed CI/CD runnersPlatform-hosted, drop-in CI/CD runner VMs (GitHub Actions / GitLab), typically faster and cheaper than the CI vendor's own hosted runners, billed per runner-minute; isolated + ephemeral per job. Distinct from git-deploy (push-to-deploy of an APP) and scheduled-tasks (cron) — this is managed CI COMPUTE you point your existing pipelines at.
Not supported
Project template marketplaceA marketplace / gallery of prebuilt PROJECT STARTER templates (apps or websites) a user clones or launches a new project from and then customises — the "start from a template" surface of a builder / PaaS. Distinct from sandbox-templates (a COMPUTE base IMAGE you fork runtime INSTANCES from — Dockerfile / OCI), from app-builder (the prompt-to-app GENERATION surface — a product can have both), and from one-click OSS-app catalogues / helm-addon-marketplace (deploy a FINISHED app as-is, not a starter you build on).
Partially supported
Organisation & security 5/9
Built-in authPlatform-provided authentication / IAM for workloads.
Not supported
SSO / SAMLEnterprise single sign-on.
Partially supported
Secrets managementFirst-class secrets storage / injection.
Supported
TeamsMulti-user team accounts.
Supported
SharingShare a running workload/resource via link (optionally gated).
Partially supported
BYOCRuns inside the customer's own cloud account.
Supported
Deploy into customers' VPCsA SaaS vendor uses the platform to deploy and operate ITS software inside ITS CUSTOMERS' cloud accounts / VPCs (nested or "customer BYOC"), managed from the vendor's control plane. Distinct from byoc (your own workloads in your own cloud account).
Supported
Workload identityThe platform gives each workload its own verifiable identity (OIDC token, SPIFFE SVID, cloud IAM federation) that it exchanges for short-lived credentials, so no long-lived static secret is stored or injected. Distinct from secrets-management (stores / injects static secrets) and credential-injection-proxy (swaps real secrets in on the wire).
Supported
Self-host / OSS coreOpen-source core that can be self-hosted.
Not supported
Proposed, not verified
Capabilities the scan saw but the registry does not track yet. A key is admitted only once two distinct products exhibit it. These are not scored.
- Customer-managed envelope encryption (BYO cloud KMS key)customer-managed-encryption-keys
“You can now use your own cloud KMS key to wrap encryption keys, or opt into Northflank-managed envelope encryption.” northflank.com
04 Agent readiness Pre-login surface · counts, not a grade
Can an agent read it?
parse-ability · docs, metadata, machine-readable surfaces
9/11
8 full · 2 partial · 82% of applicable checks
- llms.txtSupported
- llms-full.txtPartially supported
- robots.txt AI policyPartially supported
- JSON-LDNot supported
- SitemapSupported
- Meta tagsSupported
- Markdown negotiationSupported
- Content efficiencySupported
- Docs discoverableSupported
- Machine-readable pricingSupported
- No anti-bot wallSupported
Can an agent drive it?
act-ability · APIs, SDKs, MCP, credentials, webhooks
8.5/11
7 full · 3 partial · 77% of applicable checks
- Public APISupported
- OpenAPI specSupported
- MCP serverNot supported
- SDK packagesSupported
- Auth documentedSupported
- Self-serve credentialsPartially supported
- WebhooksSupported
- CLI toolSupported
- Error modelPartially supported
- Rate limits documentedSupported
- Agent config filesPartially supported
05 Coding harnesses Which agents and IDEs are documented to run here
Advertised integrations 6
- Claude Code AnthropicSupported
- Codex CLI OpenAISupported
- Cursor AnysphereSupported
- OpenCode opencodeSupported
Pi earendil-worksSupported- Windsurf CodeiumSupported
Plausible compatibility 11
Derived, not stored: the product passes SSH access, so any CLI coding agent is installable inside it. This is plausible compatibility, not a supported integration.
Aider
Amp
Antigravity
Devin
Droid- Gemini CLI
Goose
Hermes Agent
Kilo Code
Kiro CLI
Qwen Code
06 Compliance & regions Standards held, with ordinal rigor; never a score
Certifications held 2
- SOC 2 Type IIcertifiedhosted
- HIPAAenterprise-onlyhostedNEW since 2026-06-05, when the same page read 'HIPAA: No'. No certifying body for HIPAA; usable for PHI only with an Enterprise BAA.
Regions 17
- EMEA (africa-south)Africa South
- Asia Pacific (asia-east)Asia East
- Asia Pacific (asia-northeast)Asia Northeast
- Asia Pacific (asia-south-delhi)Asia South Delhi
- Asia Pacific (asia-southeast)Asia Southeast
- Asia Pacific (australia-southeast)Australia Southeast
- Americas (canada-central)Canada Central
- EMEA (europe-west)Europe West
- EMEA (europe-west-frankfurt)Europe West Frankfurt
- EMEA (europe-west-netherlands)Europe West Netherlands
- EMEA (europe-west-zurich)Europe West Zurich
- Americas (southamerica-east)Southamerica East
- Americas (us-central)US Central
- Americas (us-east-ohio)US East Ohio
- Americas (us-east1)US East1
- Americas (us-west)US West
- Americas (us-west-california)US West California
17 Northflank Cloud regions (API ids in parentheses), region fixed per project; free-tier worker clusters on Azure, paid on GCP; control plane GCP London/Amsterdam. GPU availability varies by region (e.g. L4 in Netherlands, H100 in Frankfurt, RTX PRO in US West). Plus BYOC into any AWS/GCP/Azure/Oracle/CoreWeave/Civo/Nebius region ('6+ cloud regions, 600 BYOC regions', '330+ availability zones').
07 Company & presence Facts only, not scored
Company
- Headquarters
- London, UK (20-22 Wenlock Road, N1 7GU)
- Founded
- 2019 (company formed 1 April 2019; 'running microVMs in production since 2021' per the 2026-05 intel)
- Team size
- Not disclosed. Platform metrics: 'Millions of containers', '130B+ requests processed', '100k+ developers in production' (was '80k+' in June), '330+ availability zones', 'Trusted by 2,000+ start-ups and enterprises'.
Activity
- Last release
- Changelog 'August & September 2026' published 24 Sep 2026 (Harnesses, BYOC microVMs, container snapshots, BYO-KMS encryption, Delhi region); PyPI northflank 2.0.0 on 2026-09-22; skills repo pushed 2026-09-16. northflank.com
- Last blog post
- Several posts dated 6 Oct 2026 (e.g. 'How to run AI coding agents in AWS', 'Best microVM sandboxes for AI coding agents in 2026'). northflank.com
Presence 12
- GitHub
- X / Twitter
- Blog
- Changelog
- Guides
- Stack templates
- Status
- Trust Center
- Docs
- skills.sh
- PyPI
- npm
Links found on the public surface scanned; not an exhaustive search.
08 Sources & method How this entry was produced
Public surface only
Everything here was read from northflank.com's unauthenticated pages, docs, pricing and repository on 7 Oct 2026. Nothing behind a login was used.
Statuses, not scores
Capabilities are pass, partial or fail against a written rubric (features v21). “Not assessed” means the scan predates the key.
Confidence is separate
Each fact carries its own confidence. Low-confidence facts are shown, never hidden, so you can weigh them.
- Schema
- scan v5
- Features registry
- v21
- Keys tracked today
- 61
- Assessed on this entry
- 61
Something wrong on this page?
