Modal
by Modal Labs
Serverless GPU compute for Python teams, billed by the second
Modal is a serverless GPU cloud for Python teams: decorate a function and it runs in the cloud with sub-second cold starts, per-second billing and autoscaling from zero to thousands of GPUs. It removes the Docker, Kubernetes and capacity-planning work that normally stands between an ML engineer and production inference, training or sandboxed agent execution.
Modal is a Python-native serverless compute platform: developers add decorators to ordinary Python functions and Modal runs them in the cloud on GPUs, replacing the Dockerfile, Kubernetes manifest and cluster-management layer that normally sits between an ML engineer and hardware. It was founded in January 2021 by Erik Bernhardsson, previously ML lead at Spotify and CTO of Better.com, with co-founder Akshat Bubna, and is headquartered in New York with offices in San Francisco and Stockholm. The company wrote its own container runtime in Rust and virtualises every job with gVisor, Google's user-space kernel sandbox, which is what underpins its claim of sub-second cold starts on pay-per-second billing with no reserved capacity. A single SDK covers four workload shapes: online inference with sub-10ms platform overhead plus token streaming, WebRTC and WebSocket transports; batch and asynchronous inference for embeddings, evaluations and dataset generation; training that spans LoRA and full fine-tunes, reinforcement learning and multi-node runs of up to 128 B200s over 3200 Gbps InfiniBand; and Sandboxes, isolated environments for executing untrusted or agent-generated code with GPUs attachable on demand. Autoscaling runs from zero to more than a thousand GPUs, routed across multiple clouds and regions, with integrated logging across every function, sandbox and container. Named production users include Suno, Lovable, Quora, Substack, Decagon, Reducto, Runway, Chai Discovery and Physical Intelligence. Modal completed a SOC 2 Type 2 audit and offers HIPAA BAAs on Enterprise plans. Independent analysis put its annualised revenue near $300 million by April 2026, and its own site reports over $466 million raised; it competes directly with Baseten, Replicate, RunPod, Beam and the hyperscalers' own scale-to-zero services.
The ML or platform engineering lead at an AI product company whose GPU traffic is spiky — they get scale-to-zero that actually works, without hiring a Kubernetes team to build it.
Ship GPU workloads straight from a decorated Python function and pay by the second, with sub-second cold starts instead of idle reserved capacity.
At a Glance
- Category
- Infrastructure & Cloud
- Pricing
- Usage-based, Subscription, Freemium, Contact for pricing
- Target Market
- CTOs, VP Engineering, ML Engineers, Platform Engineers, Enterprise Developers
- Deployment
- Cloud-only, Multi-cloud, API-based
- Founded
- 2021
- Headquarters
- New York, United States
- Team Size
- 51-200
Key Features
- ✓Python decorator SDK
Turns an ordinary Python function into a cloud workload with one decorator, so there is no Dockerfile, YAML or cluster to maintain.
- ✓Sub-second cold starts on a Rust runtime
A custom Rust container stack starts containers in under a second, which is what makes scale-to-zero viable for user-facing traffic rather than batch only.
- ✓gVisor-sandboxed execution
Every job is containerised and virtualised with gVisor, giving isolation strong enough to run untrusted or model-generated code safely.
- ✓Multi-node distributed training
Gang-schedules up to 128 B200 GPUs over 3200 Gbps InfiniBand from a single line of code, covering fine-tuning, RL and hyperparameter sweeps.
- ✓Sandboxes for agents
Programmatically spawned isolated environments for coding agents, background agents and RL rollouts, with GPUs attachable on demand.
- ✓Per-second billing with autoscaling
Meters compute by the second and scales from zero to over a thousand GPUs, so idle reserved capacity is never paid for.
- ✓Integrated observability
Logging and full visibility into every function, sandbox and container, so failures are debuggable without bolting on a separate stack.
Capabilities
Use Cases
- •Autoscaling LLM inference
Serve open-weight or fine-tuned models behind an autoscaling endpoint with sub-10ms platform overhead and token streaming.
- •Agent code sandboxing
Run untrusted, model-generated code from coding agents inside gVisor-isolated sandboxes rather than on shared application infrastructure.
- •Fine-tuning and reinforcement learning
Launch LoRA runs, full fine-tunes or multi-node RL jobs without provisioning a persistent GPU cluster or scheduler.
- •Batch embeddings and evaluations
Fan out embedding generation, model evaluations and synthetic dataset creation across hundreds of containers, paying only for seconds actually used.
- •Generative media products
Back image, video and audio generation features where traffic is spiky and idle GPU capacity would otherwise dominate unit cost.
Ideal For
Best For
- ✓Autoscaling LLM and multimodal inference endpoints with spiky or bursty traffic
- ✓Sandboxed execution of untrusted, agent-generated code from coding agents and RL rollouts
- ✓Fine-tuning and multi-node distributed training without standing up a GPU cluster
- ✓Large batch jobs: embedding generation, model evaluations and synthetic dataset creation
- ✓Python-first teams that want to avoid Docker, Kubernetes and capacity planning entirely
Not Ideal For
- ✗Steady, high-utilisation GPU workloads — one independent comparison puts Modal's H100 near $4.76/hour against RunPod's $4.47/hour, and per-second billing stops paying for itself once utilisation is consistently high
- ✗Teams that need self-hosting or an air-gapped deployment: Modal is cloud-only, with no on-premise option, unlike open-source alternatives such as Beam
- ✗Non-Python stacks — the programming model is Python decorators, so a Go or JVM service has to call Modal over HTTP rather than use a native SDK
- ✗Organisations that require ISO 27001 or an explicit GDPR certification, neither of which appears in Modal's published security documentation
Integrations
Deployment
Market Analysis
Pros
- ✓Cold starts are genuinely fast — the Rust runtime and gVisor stack make scale-to-zero practical for user-facing endpoints, not just batch jobs
- ✓Developer experience is the strongest in the category: one Python file replaces a Dockerfile, a Kubernetes manifest and a scheduler
- ✓One platform covers online inference, batch, training and agent sandboxes, so teams stop stitching three vendors together
- ✓Compliance is unusually mature for a company this young — SOC 2 Type 2 completed, HIPAA BAAs on Enterprise, gVisor isolation, and zero data retention on inference endpoints
- ✓Commercial traction is verifiable: roughly $300M annualised revenue by April 2026 and named production users including Suno, Quora, Substack and Runway
Cons
- ✗Expensive under sustained load — an independent comparison priced Modal's H100 near $4.76/hour against RunPod's $4.47/hour, and Modal bundles CPU and memory charges that competitors bill separately
- ✗Python-only: there is no first-class SDK for any other language, so a Go or JVM service has to call Modal over HTTP
- ✗No self-hosting. The same comparison flags that Modal has no on-premise or open-source path, unlike Beam, so exit means rewriting against another platform's primitives
- ✗Workloads are written against Modal's proprietary decorators rather than plain containers, which is why lock-in is the recurring theme in alternatives round-ups
- ✗Hyperscaler pressure is structural — AWS SageMaker and equivalents are adding scale-to-zero, and independent analysis flags GPU supply constraints and commoditisation as the company's main risks
- ✗Published compliance stops short of ISO 27001 and an explicit GDPR statement, and the HIPAA BAA explicitly excludes Volumes v1, Images and Memory Snapshots
Pricing
Starter
$0
- ✓$30/month free compute credits
- ✓10 GPU concurrency
- ✓100 containers
- ✓5 deployed cron jobs
Team
From $250/mo
- ✓$100/month free credits
- ✓50 GPU concurrency
- ✓5,000 containers
- ✓Unlimited cron jobs
Enterprise
Contact for pricing
- ✓Volume discounts
- ✓Higher GPU concurrency limits
- ✓Embedded ML engineering support
- ✓HIPAA Business Associate Agreement
List pricing is fully published, which is unusual in this category. Compute is metered per second on top of a plan fee — Starter $0, Team $250/month, Enterprise custom — with GPUs ranging from $0.000164/sec for a T4 to $0.001097/sec for an H100 SXM5 and $0.001972/sec for a B300, CPU at $0.0000131 per core-second (0.125 core minimum) and memory at $0.00000222 per GiB-second. Storage is $0.09/GiB/month after a 1 TiB free allocation. Starter includes $30/month of free credits and Team $100/month; startup credits and academic grants up to $10,000 are applied for separately. Per-second granularity favours spiky traffic, but an independent 2025 comparison priced Modal's H100 at roughly $4.76/hour against RunPod's $4.47/hour and noted Modal bundles CPU and memory charges alongside GPU time where competitors separate them — so sustained high-utilisation workloads pay a premium. HIPAA BAAs and embedded ML engineering are Enterprise-only.
Security & Compliance
Connect
Sources
This page was written from 6 sources, 3 on domains other than modal.com.
Stay Ahead of the Curve
Weekly enterprise AI insights for technology leaders. No spam, no vendor pitches—unsubscribe anytime.
SubscribeRelated Products
LiteLLM
Open-source AI gateway: 100+ LLM APIs behind one OpenAI-compatible endpoint, with cost tracking and guardrails
CIQ Fuzzball
Sovereign AI and HPC orchestration: train, fine-tune and serve models on infrastructure you control
Crusoe Cloud
Vertically integrated AI cloud — own the power, own the datacentre, rent the GPUs by the minute
Nexthop AI
Ethernet switches and network software co-designed for AI clusters, built for hyperscalers and NeoClouds