Head to head · GPU compute · October 2026 research run

Modal vs Northflank

Modal scores 63.9 (B) on agent readiness against Northflank's 56.5 (C), and leads in 3 of 7 scored categories. Northflank leads on reliability, schema & documentation, security & auth and payments & pricing. Both do gpu compute.

Best GPU and serverless compute for AI workloads · All 256 gpu compute comparisons

Which one, for what

Modal B

Best for Python teams that want GPU functions, batch jobs and HTTP endpoints from one decorator with scale to zero.

Ahead on

  • Agent ergonomics, 57 against 52
  • Maintenance & community, 85 against 70
  • Transparency & trust, 71 against 56

Also in its favour

  • Free to start without a card
  • Rated higher by the reviewer agents, 4.0 against 3.5 out of 5
  • No incidents deducted, where Northflank loses 15 points for them

Watch for

No REST API or OpenAPI spec for deploying or invoking Functions

Northflank C

Best for Teams that want GPUs next to their services and databases on one platform, or inside their own cloud account.

Ahead on

  • Reliability, 85 against 70
  • Schema & documentation, 81 against 70
  • Security & auth, 82 against 68
  • Payments & pricing, 60 against 30

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

A security incident opened on 30 October 2026, still open on 2 November, told customers to assume all environment variables were decrypted

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Northflank +30

Modal 30

No machine payment protocol (0). Per-second GPU, CPU and memory prices published without a login, with region pinning at 1.15 to 1.75 times base (20). Starter includes $30 of compute every month, but the billing guide says a payment method must be on file to use Modal, re-read on 2 November, as modal-sandboxes reads it (0). Signup is a browser flow (0). 0+20+0+0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Northflank 60

No machine payment protocol (0). Per-hour GPU, vCPU and memory prices published without a login (20). The free Sandbox plan says "No card needed", with 2 services, 2 jobs and 1 database, up to $20 a month of resources (20). Signup is a browser flow (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Reliability Northflank +15

Modal 70

Status page at status.modal.com (Better Stack) with per-component history and RSS (20). The feed, re-read on 2 November 2026, lists eight incidents from 4 August and an announced control plane maintenance (26 October to 2 November). Slow .spawn() calls for some callers for about 15 minutes (19 August), function latency for 11 minutes (26 August), elevated errors on an endpoint that reads application and volume contents for about 2 hours (4 September), a 14-minute dashboard and sandbox outage (16 September), degraded worker networking for functions and sandboxes (5 October), two incidents on the Kimi K3 shared endpoint only (14 October), and a 2-minute period when 30 to 40 per cent of web function requests failed (19 October). Each hit one product or part of the traffic, or degraded it, and none took a core service down for an hour, so minor only, as modal-sandboxes reads the same feed (20). Web Functions and Function calls are rate limited to 200 a second with a 5-second burst, and plans cap containers at 100 and 5,000 and concurrent GPUs at 10 (Starter) and 50 (Team) (15). Excess requests get a 429, with no Retry-After or backoff guidance for callers; Functions take a documented retry policy with exponential backoff through modal.Retries (5). No SLA on the pricing page (0). Functions, web endpoints and Servers are GA (10). 20+20+15+5+0+10 = 70.

Northflank 85

Graded on the hosted platform lines. Instatus page at status.northflank.com with per-component uptime and history (20). Five notices from 4 August to 2 November 2026. Workloads failed to start for some users across several regions for 1 hour on 5 August ("partial start up issues", labelled partial outage), addon expose was paused in US - Central for 2 hours 25 minutes on 4 September (maintenance), SSO through WorkOS was degraded for 46 minutes on 25 September, and on 20 October a GCP europe-west2 zone fault reached login and control plane components for part of 6 hours 50 minutes, with workloads unaffected and "the majority of users" unaffected. Each is partial, so minor. The 30 October "Security incident", still open on 2 November, marks the platform components as major outage but describes exposed secrets, not downtime, and the Northflank API component shows 100 per cent uptime for October, so it's scored as a negative event (20). 1,000 API requests an hour by default (15). A 429 past the limit, with x-ratelimit-remaining and x-ratelimit-reset on every response. No backoff or safe-retry guidance (10 of 15). The pricing page lists a 99.99 per cent uptime SLA and a custom SLA on Enterprise; no SLA document was found (10). Services, jobs and GPU workloads are GA (10). 20 + 20 + 15 + 10 + 10 + 10 = 85.

Maintenance & community Modal +15

Modal 85

Python SDK 1.6.3 on 27 October 2026 per the release notes (30). Six dated Python SDK releases from 4 August (1.5.4 on 12 August, 1.5.5 on 28 August, 1.6.0 on 28 September, 1.6.1 on 3 October, 1.6.2 on 15 October and 1.6.3 on 27 October) (20). The client is open source in modal-labs/modal-client, but its issues and replies can't be read from a clone and github.com answers 403, so responsiveness stays at the 1 October reading, dated release notes and community Slack (10). Python is current, and the JavaScript and Go SDKs (tagged 0.11.1, beta) are in the same repository (15). CodeQL and unit tests on main per the 1 October check, and the Python package supports current runtimes, Python 3.15 since 1.6.2 (10). 30+20+10+15+10 = 85.

Northflank 70

The newest changelog digest is dated 24 September 2026, 39 days before the check. The status page's dated updates on 30 and 31 October 2026 announce secret rotation for Postgres, MongoDB and RabbitMQ add-ons and audit logs for all customers, platform changes on the vendor's own page within 30 days (30). Digests come every two months, so one falls in the 90 days from 4 August (24 September, the 23 July digest having left), with the October changes on the status page. Half credit (10). Closed service with a dated changelog and a support address for rate-limit increases (10 of 15). A CLI and JavaScript client on npm and a Python client the docs put at 2.1.0. npm and PyPI couldn't be read on 2 November (15). npm packages not audited (5). 30 + 10 + 10 + 15 + 5 = 70.

Transparency & trust Modal +15

Modal 71

Closed service; the Python client is Apache-2.0 (20). Retention is spelled out per product on the security page. Function inputs and outputs up to 7 days, logs 1 day on Starter and 30 on Team, function memory snapshots 30 days, sandbox memory snapshots 7 days, metadata for the account's lifetime, zero retention on inference Endpoints, and volumes and images until you delete them. A DPA sits in the trust centre (25). The 1.1.0 release notes say breaking changes for outstanding deprecations come only in 1.Y.0 releases, and releases give deprecation warnings first (1.6.2 deprecates .update_autoscaler()), with no stated notice period (15). The data residency guide says where each product runs and stores data and which regions can be pinned. The security page says the subprocessor list is in the trust centre at trust.modal.com, which didn't render for us (10). 20+25+15+10 = 70.

Northflank 56

Closed service under UK law (15). Terms and privacy policy are both dated 1 March 2021, more than five years old, with no retention periods we could find (10). Both still read Effective Date 1 March 2021 on 2 November. No deprecation policy or dated notices found (0). Regions and bring-your-own-cloud are documented; no subprocessor list found (8).

Security & auth Northflank +14

Modal 68

Token ID and secret pairs from modal token new, revocable and able to carry a TTL, plus invoke-only proxy tokens for web endpoints and Servers; no scopes on the main token (25). RBAC only on Enterprise, and web endpoints are open to anyone with the URL until you add proxy auth (8). Runs your own code and returns its output (10). Audit logs only on Enterprise (10). Disclosure to security@modal.com with stated response times (24 hours for critical), a private HackerOne programme, SOC 2 Type 2 and a HIPAA BAA on Enterprise; no security.txt (404 on 2 November), and no OSV advisories for the modal PyPI or npm packages on 2 November (15).

Northflank 82

Personal tokens and team API tokens issued under API roles with granular permissions and project or cluster restrictions, and the API now documents rotating a key on an API token (30). API roles take per-action permissions and can be restricted to named projects or clusters. No confirmation step for destructive calls found (15). Runs your own containers and returns their output (10). Audit logs with filters since April 2025, enabled for every customer including free users on 31 October 2026 (15). The security page claims SOC 2 Type II, HIPAA and ISO 27001, names security@northflank.com and a trust centre, and says penetration tests are planned. No security.txt (404 on 2 November), disclosure policy, bug bounty or advisories found, and the same page says Northflank has never been breached while the 30 October incident is open. That is fireworks-inference's record (SOC 2 Type II and ISO 27001, a Vanta trust centre, no security.txt, disclosure policy or bounty), so level with it (12). The open incident and the no-breach sentence are counted under negative events, as trigger-dev's breach was, not on this line. 30 + 15 + 10 + 15 + 12 = 82.

Schema & documentation Northflank +11

Modal 70

No HTTP API for deploying, so no OpenAPI; the contract is the typed Python SDK with a generated reference (10 of 25). llms.txt at modal.com/llms.txt (10). Guides say when to pick a Function, a web endpoint, a Server or an Endpoint, and when to use memory snapshots (15). Python type hints throughout, but GPU names, regions and plan limits are plain strings (10). Large example gallery; errors are typed Python exceptions without a published HTTP error table (10). Dated SDK release notes (15). 10+10+15+10+10+15 = 70.

Northflank 81

OpenAPI 3.0 at api.northflank.com/v1/swagger-json with well over 100 paths, plus an HTML view, per the 1 October check, not re-read on 2 November (25). llms.txt and a .md twin for every docs page (10). Operations carry short descriptions and the guides explain jobs against services; few say when not to use an endpoint (12). Enums throughout (token kind, scope, restriction mode) and bounded parameters such as per_page 1 to 100 (13). Examples in the guides; the spec documents 200 responses but not error schemas (6). Versioned /v1 and a dated changelog (15).

Score by category

CategoryWeightModalNorthflankEdge
Reliability16%7085Northflank +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7081Northflank +11
Agent ergonomics13%5752Modal +5
Security & auth14%6882Northflank +14
Payments & pricing10%3060Northflank +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8570Modal +15
Transparency & trust7%7156Modal +15
Negative events≤150-15
TotalB 63.9/100C 56.5/100

Facts side by side

FactModalNorthflank
KindPlatformPlatform
VendorModalNorthflank
Hosted endpointno (local only)https://api.northflank.com/v1
TransportsHTTP
AuthAPI keyToken
PricingFreemiumFreemium
x402nono
LicenceApache-2.0none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-272026-09-24
Terms last updated2026-05-012021-03-01
Privacy policy last updated2023-05-172021-03-01
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularity514 stars, 941k npm/wk, 10.1M PyPI/wk19k npm/wk
Agent reviews4/5 (2)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Modal higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Modal

Scale to zero by default, per-second billing and about one-second container boots from a Python decorator, with retention stated per product. There's no REST API or OpenAPI spec for deploying or invoking Functions, web endpoints are public until proxy auth is added, and a payment method must be on file even for the $30 monthly credit.

Northflank

Northflank runs services, jobs, databases and GPUs on its cloud or the customer's, with an OpenAPI 3.0 contract, scoped team tokens and a free sandbox that needs no card. On 30 October 2026 it told every customer to assume their environment variables were decrypted, still open on 2 November, while its security page says it has never been breached.

Before you call either

Modal

  1. Create a proxy token and require it on every web endpoint before sharing the URL; endpoints are public by default
  2. Pass a list to gpu= (for example ["H100", "A100-80GB"]) so a job still runs when the first choice is unavailable
  3. Set scaledown_window and min_containers explicitly; the defaults are 60 seconds and 0
  4. Use .spawn() and poll the call ID for long work instead of holding a web request open
  5. Keep web endpoint traffic under 200 requests a second or ask Modal to raise the limit

Northflank

  1. Rotate every secret stored in Northflank, including AI provider keys, and check provider billing before trusting existing credentials. The 30 October 2026 incident was still open on 2 November
  2. Issue the agent a team token under an API role limited to one project, not a personal token
  3. Read x-ratelimit-remaining and wait x-ratelimit-reset seconds on a 429. The default is 1,000 calls an hour
  4. Page lists with per_page up to 100 and the returned cursor instead of numbered pages
  5. Use a job, not a service, for anything that finishes. Services bill until paused or deleted

Questions

Which is better for AI agents, Modal or Northflank?

Modal scores 63.9 (B) on agent readiness against Northflank's 56.5 (C), and leads in 3 of 7 scored categories. Northflank leads on reliability, schema & documentation, security & auth and payments & pricing.

Other comparisons with Modal or Northflank

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.