BareProxy 0.2.0 Runs WebAssembly Plugins Through the Proxy-Wasm Interface

Thu, 08 Oct 2026 00:00:00 +0000

BareProxy 0.2.0 is out, and it can run plugins. A plugin is a WebAssembly module, written to Proxy-Wasm, the plugin interface Envoy and Istio use, and run on wazero, a WebAssembly runtime in pure Go. So BareProxy is still one static binary on Linux, macOS and Windows. No plugin ships in this release. This one is the socket they plug into.

In a config it looks like this:

plugin crawlers /etc/bareproxy/plugins/crawlers.wasm
  config /etc/bareproxy/plugins/crawlers.json
  on-error open

site example.com
  use crawlers
  route /* -> files /var/www/example/public

What a Plugin Can Do

A site’s plugins see each request after the site is found and before routing. A plugin can change the headers, the method or the path, and then the core routes what it gets. It can answer the request itself. On the way back it sees the response headers and, if it asks, the whole body. Once the response is sent, it gets a last look for its own logging.

BareProxy Plugins Go WebAssembly, Starting With RenderCache and AI Crawler Control

Thu, 08 Oct 2026 00:00:00 +0000

BareProxy’s core stays bare. Everything else comes as plugins, and a plugin is now a WebAssembly module that BareProxy loads at run time. That replaces the earlier plan of modules compiled into the binary.

Three things change for anyone running it. A plugin is a .wasm file named in the config, so adding or upgrading one is a config change: plan shows it, apply makes it live, rollback takes it back. No rebuild, no restart. A plugin runs in a sandbox, with no files, sockets or processes unless the config grants them, so a broken one can’t take the server down. And a plugin can be written in anything that compiles to WebAssembly. Rust, Go, C++, Zig, AssemblyScript.

Plugins on BareProxy.com

BareProxy 0.2.0 Runs WebAssembly Plugins Through the Proxy-Wasm Interface

What a Plugin Can Do

BareProxy Plugins Go WebAssembly, Starting With RenderCache and AI Crawler Control