Rust, WebAssembly & Cloudflare edge
Rust is a systems language with no garbage collector, a type system and ownership model that guarantee memory safety and thread safety, and tooling that makes the result easy to build and test. That suits servers that must not crash, parsers of untrusted input, blockchain nodes and high-rate data capture. WebAssembly (Wasm) is a portable, sandboxed binary format that runs near native speed in browsers and on servers, and Rust compiles to it.
What we do
- Rust services, parsers and command-line tools
- Wasm modules for browser and edge
- Cloudflare Workers with KV, R2, D1 and Durable Objects
- WAF, rate-limit and bot rules at the edge
- Secrets and bindings kept out of source code
- Reproducible builds and release automation
Cloudflare Workers runs code on Cloudflare's network without servers to manage. JavaScript, TypeScript, Python and Rust are supported; Rust runs by compiling to WebAssembly through the workers-rs crate, wasm-bindgen and the worker-build tool. Around Workers sit KV for cached reads, R2 for object storage, D1 for SQL and Durable Objects for coordinated state, and the Cloudflare WAF with managed rules and rate limiting protects what is exposed.
We use this combination for sites, APIs and wallet or data tools: a small Rust core compiled once to Wasm, edge routing and caching, secrets in the platform store rather than in code, and tests that run the same binary locally and in production. Part of our tailored-software and cloud practice.
Leading platforms we work with
- Rust
- WebAssembly
- Cloudflare Workers
- Cloudflare WAF
- Cloudflare Pages
- Cloudflare Tunnel
- Fastly Compute
- Wasmtime
Platforms and practices
- Rust services and command-line tools
- Rust compiled to WebAssembly
- workers-rs and wasm-bindgen
- Cloudflare KV, R2, D1 and Durable Objects
- Cloudflare WAF managed rules
- Rate limiting
- Edge caching and routing
- Browser-side Wasm modules
References
Sources last checked .
Product names are trademarks of their owners and are listed to describe our experience; they do not imply endorsement or partnership.
How we use Rust, WebAssembly & Cloudflare edge for clients
Where this matters most
Frequently asked questions
Direct answers to the questions we hear most. Something else on your mind?
Send us a messageWhy Rust?
Rust has no garbage collector and its ownership model guarantees memory safety and thread safety, which suits servers that must not crash, parsers of untrusted input, blockchain nodes and high-rate data capture. Tooling makes the result easy to build and test.
What is WebAssembly?
A portable, sandboxed binary format that runs at near native speed in browsers and on servers. Rust compiles to it, so a small core can be written once and run in a browser, at the edge, or on a server.
How does Rust run on Cloudflare Workers?
Workers runs code on Cloudflare's network without servers to manage. JavaScript, TypeScript, Python and Rust are supported. Rust runs by compiling to WebAssembly through the workers-rs crate, wasm-bindgen and the worker-build tool.
What storage is available at the edge?
KV for cached reads, R2 for object storage, D1 for SQL and Durable Objects for coordinated state. Each has limits and consistency trade-offs, so we choose per workload and confirm against Cloudflare's current documentation before designing around one.
How are secrets and security handled?
Secrets live in the platform's secret store, not in code. The Cloudflare WAF with managed rules and rate limiting protects what is exposed. We run the same binary in local tests and in production, so what was tested is what ships.
Are you a Cloudflare partner?
No. This page describes our experience building sites, APIs and wallet or data tools on these technologies. Cloudflare, Rust and WebAssembly are trademarks of their owners, and we do not claim a partnership or certification.