Cloudflare Python Workers are generally available, and now run FastAPI, Django and Flask with Hyperdrive access to Postgres and MySQL

Cloudflare announced on 2026-09-21 that Python Workers has moved to general availability, two years after Cloudflare's own dating of its first introduction. The company says FastAPI, Django and Flask now run natively in the Workers runtime, and that Hyperdrive can connect Workers to PostgreSQL and MySQL from Python through a newly enabled TCP socket implementation.

What actually changed

The runtime uses Pyodide, a WebAssembly build of the Python interpreter, and ships type conversions between Python and JavaScript inside the runtime and the SDK. Cloudflare writes that this removes the manual glue code a developer used to write when calling a JavaScript-side binding from Python. The web frameworks connect through built-in ASGI and WSGI adapters, which Cloudflare describes as "a thin, optimized bridge" between an HTTP request and the framework's handler.

Cloudflare also says Python Workers has adopted the PyEmscripten platform in PEP 783, which is the standard packaging format for Python wheels built for WebAssembly. In practice this means a wider slice of pure-Python packages installs without a custom fork.

What ships with it

The platform bindings that were already available to a JavaScript Worker are now callable from Python: Workers AI for on-network model inference, R2 for object storage, D1 for SQLite, Hyperdrive for a pooled connection to an external Postgres or MySQL database, Durable Objects for stateful compute, Queues and Workflows. Cloudflare calls out the OpenAI, LangChain and Model Context Protocol packages by name, all of which work under Pyodide today.

Cloudflare frames the Hyperdrive step as the change that lets most existing Python code run without a rewrite: the runtime now supports raw TCP sockets, so a Postgres client that speaks the database wire protocol can open a connection through Hyperdrive rather than through an HTTP proxy.

Where the trade-off sits

Two limits are worth reading before a team commits. First, the runtime is Pyodide, a WebAssembly build of Python, so any package that ships a C extension without a WebAssembly build will still refuse to install. Second, Cloudflare's post does not restate the per-request CPU, memory or startup limits for the general availability version, so a team that plans to move an existing service should measure those on its own workload rather than assume the JavaScript numbers still apply.

For a Python team that has been running FastAPI on a container platform to serve an AI agent, this is the first Cloudflare release that lets the same code go to production on Workers without a rewrite. The named support for OpenAI, LangChain and Model Context Protocol packages is the specific fact worth acting on: an agent that calls a hosted model, keeps a vector store in R2 or D1, and pulls user data through Hyperdrive is now one Python file that deploys with wrangler, with no JavaScript layer to write, maintain or re-port every time the Python side changes.

Source

• Cloudflare: Python Workers are now generally available