Modal vs Nebius AI Cloud

Modal

Scale to zero by default, per-second billing and about one-second container boots. No REST API or OpenAPI spec for deploying or invoking Functions.

Nebius AI Cloud

One API definition generates the REST and gRPC interfaces, the CLI, Terraform provider and three SDKs, with a 602-operation OpenAPI document, X-Idempotency-Key and role-scoped service accounts. The status page lists 14 major incidents between 14 July and 8 October 2026, no request rate limits were found, and signup needs a browser and a card.

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

Nebius AI Cloud

1. Use a service account with an authorised key, then exchange a five-minute RS256 JWT at https://auth.eu.nebius.com/oauth2/token/exchange for a 12-hour Bearer token
2. Send X-Idempotency-Key with a random UUID on every create, update and delete, since a 504 can follow a call that succeeded
3. Poll the returned operation (/ai/v1/endpoints/operations/{id}) until status is set; concurrent operations on one resource are not supported
4. Stop or delete endpoints when idle. A stopped endpoint bills nothing, a stopped Devlab or VM still bills for its disk
5. Check region support first. Serverless AI is absent from eu-south1 and us-north1, and each GPU platform exists in one to four regions
6. Run the beta nebius/mcp-server with safe mode on (the default); nebius_cli_execute can run any CLI command when SAFE_MODE=false