WEB-STANDARDS-FIRST PYTHON
One application.
Every serious runtime.
Build typed HTTP, MCP, authentication, and checked data access once. Run it on ASGI, Cloudflare Workers, or AWS Lambda.
THE MODEL
Fetch at the center. Adapters at the edge.
Hayate keeps WHATWG-style Request, Response,
URL, and URLPattern semantics in the application
core. Deployment adapters stay explicit, so Cloudflare does not require
ASGI and conventional Python does not inherit Workers constraints.
THREE RUNTIME CONTRACTS
Choose the boundary. Keep the application.
ASGI
Uvicorn and the existing Python server ecosystem for conventional deployments.
Deploy on ASGI →Workers
Native Python Workers, D1 bindings, RPC-capable class entrypoints, and no ASGI layer.
Deploy on Workers →Lambda
API Gateway v2 and Function URLs, including a native response-streaming runtime.
Deploy on Lambda →COMPOSE ONLY WHAT YOU NEED
A small core. A deliberate family.
Auth, MCP, OpenAPI, checked SQL, outbound fetch, admin, and hypermedia are maintained as explicit packages—not hidden framework weight.
EVIDENCE, NOT A UNIVERSAL WINNER
Current claims are dated, reproducible, and bounded.
The published baseline records startup, dependencies, payload, throughput, and a shared HTTP contract. Compatibility is backed by real ASGI, Workerd/D1, and downstream package runs.
Read the evidenceSTART FROM A TESTED COMPOSITION
From empty directory to passing production checks.
uvx --from create-hayate==0.11.1 create-hayate my-app --template workers --preset production