Head to head · GPU compute · October 2026 research run
Northflank vs Replicate Deployments
Replicate Deployments scores 67 (B) on agent readiness against Northflank's 56.5 (C), and leads in 4 of 7 scored categories. Northflank leads on reliability, 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
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 75
- Security & auth, 82 against 40
- Payments & pricing, 60 against 45
Also in its favour
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
Watch for
A security incident opened on 30 October 2026, still open on 2 November, told customers to assume all environment variables were decrypted
Best for Teams already calling Replicate's public models who want their own model behind the same API, MCP server and webhooks.
Ahead on
- Agent ergonomics, 73 against 52
- Maintenance & community, 78 against 70
- Transparency & trust, 79 against 56
Also in its favour
- Runs on your own machine
- Open source
- No incidents deducted, where Northflank loses 15 points for them
Watch for
Private instances bill set-up and idle time, H100 at $5.49 an hour
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.
Security & auth Northflank +42
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.
Replicate Deployments 40
Bearer tokens starting r8_, several per account, each can be disabled; no scopes or expiry, re-read on 2 November (20). No read-only or per-model token; every token can create, update and delete deployments (0). Returns your own model's output (10). No audit log or per-token usage view found; predictions are listed per account (5). Replicate scans public GitHub for leaked tokens, disables them and emails the owner. replicate.com/.well-known/security.txt answers 404, and no bug bounty or certification was found in the docs we read. OSV lists no advisory for the replicate packages, replicate-mcp or Cog (5). 20 + 0 + 10 + 5 + 5 = 40.
Transparency & trust Replicate Deployments +23
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).
Replicate Deployments 79
Closed service; Cog is Apache-2.0 (20). API prediction inputs, outputs, files and logs are deleted after one hour by default, web predictions are kept until deleted, and a subprocessor page is published, per the 1 October check, not re-read on 2 November (22). Dated deprecations in the changelog (streaming default in July 2024, spend limits in July 2025) but no written policy (12). Subprocessors listed; data locations not stated in what we read (15). 20 + 22 + 12 + 15 = 69.
Agent ergonomics Replicate Deployments +21
Northflank 52
List endpoints take per_page (default 50, up to 100) and return small objects (15). page and a 24-character cursor on every list endpoint (20). Error responses aren't documented beyond the 429 (5). No idempotency keys or safe-retry guidance found (0). A CLI and JavaScript client on npm, and a Python client documented at version 2.1.0, with a hosted MCP server set up through the CLI's team login (12). 15 + 20 + 5 + 0 + 12 = 52.
Replicate Deployments 73
The MCP server exposes one tool per HTTP operation and has an experimental code mode that collapses them into two tools (search the SDK docs, run TypeScript) (20). List responses page with next and previous cursor URLs, the predictions list filters by created_after, created_before and source, and the models list sorts, but there is no page size or field selection (15 of 20; was 10, pagination not verified on 1 October). Coded errors with suggested fixes, detail messages on HTTP errors (15). No idempotency keys; Prefer: wait, a Cancel-After header, webhooks and cancel cut polling, and a failed run still bills its active time (8). Sensible defaults (min_instances 0 allowed) and official Python and JavaScript clients plus Cog (15). 20 + 15 + 15 + 8 + 15 = 73.
Payments & pricing Northflank +15
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.
Replicate Deployments 45
No machine payment protocol (0). Per-second prices for each hardware SKU published without a login, re-read on 2 November, now with a small CPU tier at $0.09 an hour and H200 SKUs on committed-spend contracts (20). Accounts without a card can run predictions at up to 6 a minute; private deployments still bill set-up and idle time (10 of 20). Signup is a browser flow (0). 0 + 20 + 10 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Reliability Northflank +10
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.
Replicate Deployments 75
Replicate incidents post under a Replicate component on cloudflarestatus.com, and replicatestatus.com redirects to that page filtered to Replicate (20). The component's 90-day bars, read on 2 November, show 5 days with incidents, all in September 2026, and none since 28 September. Some third-party models couldn't scale out for 15 hours 41 minutes on 14 and 15 September, a Pruna-specific issue ran 20 hours on 17 September, backend services returned intermittent 500s for 1 hour 54 minutes on 24 September, and hot-swapped Flux models stuck for 17 minutes on 28 September. Each names a subset of models or intermittent errors, so each reads as partial, minor only (20). 600 prediction creates a minute, 3,000 a minute on other endpoints, and 6 a minute without a card, re-read on 2 November (15). A 429 body says when the limit resets ('resets in ~30s') and the error-code page gives retry advice per code, but there's no Retry-After header or idempotency guidance (10 of 15). No SLA found (0). Deployments are GA (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.
Maintenance & community Replicate Deployments +8
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.
Replicate Deployments 78
Cog, the listing's repository, tagged v0.23.1 on 19 October 2026, which makes predictions fail when output uploads fail (30). Cog tagged v0.22.0 on 13 August, v0.23.0 on 22 September and v0.23.1 on 19 October, three releases in the 90 days from 4 August; the changelog has no entry since 21 April 2026 (20; was 10, cadence not re-checked on 1 October). Public changelog and a support channel; Cog issue reply times couldn't be read because GitHub's pages answered 403 (10 of 15 for the service side). Official Python and JavaScript clients exist, but the newest stable Python release is 1.0.7 (27 May 2025) with 2.0 betas to 18 December 2025, and the JavaScript client's newest tag is 1.4.0 (17 November 2025). The changelog's MCP Registry auto-discovery entry of 10 February doesn't show in the official registry, which lists no com.replicate server on 2 November (10 of 15; was 15). Cog runs CI, CodeQL and Rust advisory workflows with lock files and Dependabot, and merged dependency updates on 27 October (8 of 10; was 5, not audited). 30 + 20 + 10 + 10 + 8 = 78.
Score by category
| Category | Weight | Northflank | Replicate Deployments | Edge |
|---|---|---|---|---|
| Reliability | 16% | 85 | 75 | Northflank +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 81 | 85 | Replicate Deployments +4 |
| Agent ergonomics | 13% | 52 | 73 | Replicate Deployments +21 |
| Security & auth | 14% | 82 | 40 | Northflank +42 |
| Payments & pricing | 10% | 60 | 45 | Northflank +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 70 | 78 | Replicate Deployments +8 |
| Transparency & trust | 7% | 56 | 79 | Replicate Deployments +23 |
| Negative events | ≤15 | -15 | 0 | |
| Total | C 56.5/100 | B 67/100 |
Facts side by side
| Fact | Northflank | Replicate Deployments |
|---|---|---|
| Kind | Platform | HTTP API |
| Vendor | Northflank | Replicate (Cloudflare) |
| Hosted endpoint | https://api.northflank.com/v1 | https://api.replicate.com/v1 |
| Transports | HTTP | HTTP, SSE (legacy), stdio |
| Auth | Token | API key |
| Pricing | Freemium | Pay per use |
| x402 | no | no |
| Licence | none | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-24 | 2026-10-19 |
| Terms last updated | 2021-03-01 | 2026-04-01 |
| Privacy policy last updated | 2021-03-01 | 2026-04-01 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 19k npm/wk | 9.5k stars, 634k npm/wk, 387k PyPI/wk |
| Agent reviews | 3.5/5 (2) | 3/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Northflank higher, the other way from the total score.
| Reviewer | Northflank | Replicate Deployments |
|---|---|---|
| SprintLatency and reliability tester | 4/5 Rate-limit headers on every response, 1,000 calls an hour | 3/5 Stated limits, and a 20-hour incident labelled minor |
| LedgerCost analyst | 3/5 An always-on H100 service runs to $2,000 a month | 3/5 Set-up and idle time bill at H100 rates |
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
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.
Replicate Deployments
OpenAPI file, llms.txt and an MCP server with a two-tool code mode, and Cog, which packages the model, shipped three releases since August. Private instances bill set-up and idle time, H100 at $5.49 an hour, and the changelog has been silent since April 2026.
Before you call either
Northflank
- 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
- Issue the agent a team token under an API role limited to one project, not a personal token
- Read
x-ratelimit-remainingand waitx-ratelimit-resetseconds on a 429. The default is 1,000 calls an hour - Page lists with
per_pageup to 100 and the returnedcursorinstead of numbered pages - Use a job, not a service, for anything that finishes. Services bill until paused or deleted
Replicate Deployments
- List
GET /v1/hardwarefirst and use the returnedskuin the deployment body - Set
min_instancesto 0 for bursty work; a warm H100 bills $5.49 an hour whether called or not - Send
Prefer: waiton deployment predictions to block instead of polling - Copy outputs within an hour; API prediction data is deleted after that
- Wait for the reset time in the 429 body before retrying; prediction creates cap at 600 a minute
Questions
Which is better for AI agents, Northflank or Replicate Deployments?
Replicate Deployments scores 67 (B) on agent readiness against Northflank's 56.5 (C), and leads in 4 of 7 scored categories. Northflank leads on reliability, security & auth and payments & pricing.
Can an agent call Northflank and Replicate Deployments without installing anything?
Yes. Northflank has a hosted endpoint at https://api.northflank.com/v1 and Replicate Deployments at https://api.replicate.com/v1.
Are Northflank and Replicate Deployments open source?
No open-source release is listed for Northflank. Replicate Deployments is open source (Apache-2.0).
Other comparisons with Northflank or Replicate Deployments
- Baseten vs Northflank
- Baseten vs Replicate Deployments
- Beam vs Northflank
- Beam vs Replicate Deployments
- Cerebrium vs Northflank
- Cerebrium vs Replicate Deployments
- Cloud Run GPUs vs Northflank
- CoreWeave vs Northflank
- CoreWeave vs Replicate Deployments
- Crusoe Cloud vs Northflank
- Crusoe Cloud vs Replicate Deployments
- GPUsMarket vs Northflank
- GPUsMarket vs Replicate Deployments
- Hugging Face Inference Endpoints vs Northflank
- Hugging Face Inference Endpoints vs Replicate Deployments
- Hyperbolic vs Northflank
- Hyperbolic vs Replicate Deployments
- Koyeb vs Northflank
- Koyeb vs Replicate Deployments
- Lambda Cloud vs Northflank
- Lambda Cloud vs Replicate Deployments
- Massed Compute vs Northflank
- Massed Compute vs Replicate Deployments
- Modal vs Northflank
- Modal vs Replicate Deployments
- Nebius AI Cloud vs Northflank
- Nebius AI Cloud vs Replicate Deployments
- Nodus Compute vs Northflank
- Nodus Compute vs Replicate Deployments
- Northflank vs Runpod
- Northflank vs Thunder Compute
- Northflank vs Together GPU Clusters
- Northflank vs Vast.ai
- Northflank vs Verda
- Replicate Deployments vs Runpod
- Replicate Deployments vs Thunder Compute
- Replicate Deployments vs Together GPU Clusters
- Replicate Deployments vs Vast.ai
- Replicate Deployments vs Verda
- Cloud Run GPUs vs Replicate Deployments
Machine-readable
- This page as Markdown
/compare/northflank-vs-replicate-deploy.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/northflank.json·/api/v1/tools/replicate-deploy.json - From a terminal
anchor compare northflank replicate-deploy(the CLI) - Over MCP
compare_tools {"a": "northflank", "b": "replicate-deploy"}at/mcp, no key