Modal

Modal — serverless cloud compute for Python and ML workloads.

AnalyticsModerate

Stack Components

PlatformModal

Why

Run Python in cloud with one decorator, auto-scaling, GPU support, pay per second. PostHog and Plausible offer privacy-first analytics without GDPR consent banners, growing 200% in 2024.

BigQuery and ClickHouse process petabyte-scale data at $5/TB scanned.

When

Use for ML inference and batch jobs. Avoid for long-running servers.

How

1. pip install modal 2. @stub.function decorator 3. modal deploy 4. Call from client 5. Add environment configuration — cp .env.example .env && edit values 6. Run tests — npm test or pnpm test to verify setup 7. Deploy — git push to trigger CI/CD or manual deploy

Example

import modal stub = modal.Stub() @stub.function def f(x): return x ** 2 with stub.run(): print(f.remote(42))

Common Problems

⚠Cold start latency — use keep_warm
⚠Image build slow — cache with modal.Image
⚠Configuration drift between environments — use infrastructure-as-code (Terraform/Pulumi) to keep dev/staging/prod identical

Best Practices

✓Use .map() for parallel batch processing
✓Mount volumes for shared data
✓Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit

FAQ

What is Modal and what projects is it for?

Modal — serverless cloud compute for Python and ML workloads. It pairs layered technologies for end-to-end type safety and out-of-the-box deploys, fitting everything from MVPs to production SaaS.

How do I spin up a working demo with Modal in 10 minutes?

Two steps: (1) pip install modal; (2) @stub.function decorator. Get the local dev server running, then wire one real data source to verify the end-to-end loop.

What is the most common pitfall with Modal and how do I avoid it?

The most common pitfall is: Cold start latency — use keep_warm. Avoid it by adding the matching checklist to your PR template and running type-check + lint + unit tests in CI — three gates before merge.

What are the best practices for Modal?

Best practices for Modal include: Use .map() for parallel batch processing; Mount volumes for shared data; Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit. The first one — "Use .map() for parallel batch processing" — should be set up at project init to avoid costly rework later.

When should I NOT choose Modal?

Pick something else in three cases: (1) the team has zero experience with the core framework and the deadline is tight (learning-curve risk); (2) it's a pure content/marketing site (Astro is lighter); (3) you need very high throughput (>10k RPS) or strict-consistency microservices (Go/Rust). Modal shines for mid-to-high complexity full-stack and API work — don't over-engineer simple static pages with it.