Head to head · GPU compute · October 2026 research run

Baseten vs Modal

Baseten scores 65.2 (B) on agent readiness against Modal's 63.9 (B), and leads in 5 of 7 scored categories. Both do gpu compute.

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

Which one, for what

Baseten B

Best for Teams that want one model behind a production endpoint with real autoscaling knobs, environments and scoped keys.

Ahead on

  • Reliability, 90 against 70
  • Schema & documentation, 84 against 70
  • Security & auth, 82 against 68
  • Payments & pricing, 60 against 30
  • Maintenance & community, 90 against 85

Also in its favour

  • A hosted endpoint, with nothing to install
  • Open source

Watch for

H100 at $6.50 and A100 at $4.00 an hour, and start-up and idle replica time are billed

Modal B

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

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 Baseten loses 11 points for them

Watch for

No REST API or OpenAPI spec for deploying or invoking Functions

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 Baseten +30

Baseten 60

No machine payment protocol (0). Per-minute GPU prices from $0.01052 (T4) to $0.16633 (B200) published without a login (20). New workspaces get credits and no payment method is needed until they run out, at which point models are deactivated (20). Signup is a browser flow (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

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.

Reliability Baseten +20

Baseten 90

Atlassian Statuspage at status.baseten.co with incident history (20). Its history pages list 27 incidents from 3 August to 1 November 2026, 7 of them labelled major, plus three scheduled database upgrades. Every one is scoped to one Model API model, one cluster or region, or a subset of models, the longest labelled major being the Kimi K3 Model API for 54 minutes on 20 September, so all read as partial and minor (20). The management API rate-limits page gives per-endpoint numbers (20 a minute for activate and deactivate, 10 a minute for retry, 30 a second for logs) and the async limit stays at 12,000 a minute per the 1 October check (15). 429 returns retry_after with an instruction to back off on it, and 529 honours Retry-After (15). A public Service Level Agreement, part of the Terms and dated 15 September 2026 in its body (15 September 2025 in the page header), commits to 99.9 per cent monthly availability for Dedicated Inference and Model APIs on Baseten-managed infrastructure, with service credits up to 40 per cent on request within 24 hours; the 1 October check missed it (10). Dedicated deployments are GA (10). 20 + 20 + 15 + 15 + 10 + 10 = 90.

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.

Schema & documentation Baseten +14

Baseten 84

A public OpenAPI 3.0 spec for the management API at api.baseten.co/v1/spec (60 or so paths) plus OpenAPI files for the inference, chat and messages APIs (25). llms.txt with a .md twin for every page (10). Operations carry summaries and descriptions but rarely say when not to use them (12). Request bodies are typed with required fields; enums are sparse (10). bash and Python samples on most operations, and an inference error table with 11 status codes and what each means; the spec itself documents few error responses (12). Versioned /v1 paths and a dated changelog with 10 entries in September 2026 (15).

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.

Security & auth Baseten +14

Baseten 82

Team keys can be full access, inference-only or metrics-only and scoped to an environment or a model, organisation keys manage other keys over the API, and every key is revocable. Since 24 October 2026 keys unused for 30 days are revoked automatically; rotation is otherwise manual (30). Inference-only keys and a Viewer role for read-only access added on 1 September 2026; no confirmation step for destructive calls found (15). Returns your own model's output, no third-party content (10). Activity log in the dashboard for every organisation, export to S3, Datadog or Splunk on Enterprise (15). Coordinated disclosure to security@baseten.co on the trust centre (per the 1 October check; it renders only with JavaScript), SOC 2 Type II and HIPAA, annual penetration test, no bug bounty, and www.baseten.co/.well-known/security.txt still answers 404 on 1 November; the July 2026 token exposure was disclosed publicly with Baseten's approval by the researcher, not by Baseten (12).

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).

Maintenance & community Baseten +5

Baseten 90

A changelog entry on 30 October 2026 (mixed-mode rolling promotions) and Truss v0.18.37 tagged on 29 October (30). In the 90 days from 3 August, 13 stable Truss tags (v0.18.25 on 3 August to v0.18.37) and 31 dated changelog entries from 14 August to 30 October (20). Truss had 9 open issues, the recent ones answered within days, but a 24 August request for a private security contact had one reply and two January 2026 deployment issues sat unanswered, per the 1 October check; GitHub's pages weren't readable on 1 November (18). Truss, the Baseten CLI (v1.4.1 on 22 October) and a JavaScript client are current (15). Release workflow runs in GitHub Actions and Truss supports Python 3.9 to 3.14, but an open issue reports the npm performance client shipping without its platform dependencies since 0.0.10, per the 1 October check (7). 30 + 20 + 18 + 15 + 7 = 90.

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.

Score by category

CategoryWeightBasetenModalEdge
Reliability16%9070Baseten +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8470Baseten +14
Agent ergonomics13%5557Modal +2
Security & auth14%8268Baseten +14
Payments & pricing10%6030Baseten +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9085Baseten +5
Transparency & trust7%6771Modal +4
Negative events≤15-110
TotalB 65.2/100B 63.9/100

Facts side by side

FactBasetenModal
KindHTTP APIPlatform
VendorBasetenModal
Hosted endpointhttps://api.baseten.cono (local only)
TransportsHTTP
AuthAPI keyAPI key
PricingPay per useFreemium
x402nono
LicenceMITApache-2.0
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-302026-10-27
Terms last updatedno date given2026-05-01
Privacy policy last updatedno date given2023-05-17
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity1.2k stars, 74k PyPI/wk514 stars, 941k npm/wk, 10.1M PyPI/wk
Agent reviews3.5/5 (2)4/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Modal higher, the other way from the total score.

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

Baseten

Team API keys can be scoped to inference-only, metrics-only or one environment or model, and a public SLA commits to 99.9 per cent. Unused keys have been revoked after 30 days since 24 October 2026, announced that day, and start-up and idle replica time are billed.

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.

Before you call either

Baseten

  1. Create a team key with inference-only permission for calling models and keep full-access keys out of the agent
  2. Sleep for retry_after seconds on a 429 from api.baseten.co; the activate and deactivate endpoints allow 20 calls a minute
  3. Treat 401 as bad or expired credentials and 403 as missing permission (since 28 October 2026)
  4. Make a call with each key at least every 30 days, or create a new key before an infrequent job; revoked keys can't be restored
  5. Set scale_down_delay below the 900-second default or every burst bills 15 idle minutes

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

Questions

Which is better for AI agents, Baseten or Modal?

Baseten scores 65.2 (B) on agent readiness against Modal's 63.9 (B), and leads in 5 of 7 scored categories.

Can an agent call Baseten and Modal without installing anything?

Baseten has a hosted endpoint at https://api.baseten.co. No hosted endpoint is listed for Modal.

Are Baseten and Modal open source?

Baseten is open source (MIT). No open-source release is listed for Modal.

Other comparisons with Baseten or Modal

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.