// the find
zappa/Zappa
Serverless Python
Zappa wraps existing Python WSGI/ASGI web apps and deploys them to AWS Lambda + API Gateway with a single command. It handles packaging, IAM role creation, routing setup, and SSL cert management — you point it at your Flask/Django/FastAPI app and it does the AWS plumbing. Aimed at developers who want Lambda's cost model without rewriting their app for a serverless runtime.
The zero-code-change deployment story is real — your existing Flask or Django app runs unmodified, which is a meaningful advantage over frameworks that require Lambda-aware handlers. The CLI is genuinely thoughtful: `zappa tail`, `zappa rollback -n 3`, and `zappa manage production migrate` cover the operational loop most teams actually need. ASGI support for FastAPI and Starlette landed properly, not as a bolted-on afterthought. The test suite uses placebo for AWS interaction recording, so tests don't require live AWS credentials.
Cold starts are a first-class problem and the 'keep warm' workaround is a scheduled ping hack, not a solution — you're paying for fake traffic to avoid Lambda's inherent latency. The default IAM policy is overly permissive and the README admits it but leaves the fix to you, which means most people ship with it. ASGI support has notable gaps: no WebSocket via ASGI, no lifespan protocol, no streaming responses — if you're using FastAPI for its streaming or lifespan startup hooks, those won't work. The 30-second API Gateway hard timeout is a wall that catches people off guard; the ALB workaround is documented but requires separate setup that Zappa doesn't automate.