Python Workers Reach GA as Cloudflare Deletes the JS Conversion Tax

Python Stops Translating and Starts Running

Cloudflare has moved Python Workers into general availability, making Python a fully supported first-class language on the Cloudflare Developer Platform.

Python developers can now bring existing libraries, patterns, and code directly to Workers AI, R2, D1, Hyperdrive, Durable Objects, Queues, and Workflows without a JavaScript translation layer.

For performance teams, the most important change is the removal of the Python-to-JavaScript object conversion tax that previously sat between Python code and Cloudflare bindings.

GA Stack: Bindings, Frameworks, Sockets, and Wheels

As noted on the Cloudflare blog, Cloudflare has encapsulated type conversion inside the Workers runtime and Python SDK.

Previously, sending a Python dictionary to a Queue required explicit conversion through the Pyodide foreign function interface and a JavaScript object constructor.

That requirement forced Python developers to keep the JavaScript runtime in mind even when writing pure Python workers.

Now a direct dictionary send works as if the binding was native Python.

• Native bindings: no explicit JavaScript conversion across Cloudflare APIs.
• Web frameworks: FastAPI, Django, and Flask run through ASGI and WSGI connectors.
• Database access: Hyperdrive supports PostgreSQL and MySQL through socket-level bridges.
• Package ecosystem: PyEmscripten wheels are becoming a standardized WebAssembly target under PEP 783.
• AI libraries: OpenAI, LangChain, and MCP clients run natively against Workers AI and AI Gateway.

The framework support removes the need for an internal server such as Uvicorn or Gunicorn.

Cloudflare’s network handles load balancing and scaling, while the workers.asgi and workers.wsgi connectors translate incoming requests into the standard interfaces that Python frameworks already expect.

That keeps the connector thin and avoids routing every request through a heavier development server.

Hyperdrive access required solving a lower-level problem: WebAssembly sandboxes typically stub out POSIX networking system calls.

Database drivers such as aiomysql and asyncpg rely on the socket module, so any standard TCP connection would fail without a bridge.

Cloudflare implemented socket system calls using the Workers connect API, translating Python socket operations into the runtime’s JavaScript networking primitives.

Because that work happens at the system call layer, Python drivers do not need to know that the underlying runtime is WebAssembly.

Package support is also moving from manual builds to a cross-community standard.

Python packages with native C, C++, or Rust extensions must be compiled to WebAssembly, and the newly accepted PEP 783 PyEmscripten platform gives maintainers a published target.

Cloudflare also contributed PyEmscripten support to cibuildwheel, which reduces the friction for package maintainers.

AI workloads benefit from the same networking repair.

Contributions upstream allow HTTP clients such as requests and httpx to route through JavaScript fetch inside WebAssembly environments.

That makes openai, langchain, and mcp packages viable inside Python Workers, either for direct model access or through Workers AI and AI Gateway.

The Workers Revenue Signal in the Performance Market

Reporting from Zacks Equity Research, carried by Yahoo Finance, positions Workers as moving beyond an adoption metric into a meaningful revenue contributor for Cloudflare.

At the end of the second quarter of 2026, Cloudflare counted more than 7.4 million developers on Workers, adding nearly 2 million in that quarter alone.

That single-quarter gain exceeded the 1.5 million developers added during all of 2025.

Enterprise traction is following the developer expansion.

One APAC technology company signed a $4 million pool-of-funds contract for Workers after previously signing an $8.7 million Application Services contract.

Another technology company signed a $6 million Workers contract specifically to support AI agent capabilities.

Consensus estimates point to Cloudflare revenue growth of 32.3 percent in 2026 and 28.5 percent in 2027.

Cloudflare’s forward price-to-sales ratio sat at 28.87 versus an industry average of 3.91.

Cloudflare shares had gained 40.7 percent year-to-date when the data was compiled, while the broader Internet – Software industry declined 4.5 percent.

Performance constraints expanded on a similar timeline.

Cloudflare raised the Workers per-request CPU ceiling from 30 seconds to 50 seconds between June and August, creating more headroom for AI, database, and stream-processing workloads.

Python Workers also gained direct Python-to-JavaScript runtime calls with live object references, reducing serialization overhead across language boundaries.

Competitive pressure surrounds that growth.

Palo Alto Networks reported SASE annual recurring revenue up 40 percent year over year in its third fiscal quarter of 2026.

Zscaler ended its third fiscal quarter with more than 700 Zero Trust Everywhere enterprises, up from more than 550 in the prior quarter.

Those data points show the edge security and connectivity market is not ceding ground while Cloudflare pushes deeper into Python workloads.

Edge Python’s Production Runway

Python on Workers is no longer an experimental bridge; it is a production performance decision.

Data, AI, and database teams can now choose edge execution without accepting a JavaScript serialization penalty. For performance teams translating edge-native Python into faster production workloads, WordPress speed engineering at Andres SEO Expert applies the same bottleneck-first discipline — get in touch.