Three ways to run your own logic inside the proxy, and how to choose between them.
Extend
Put your own logic in the request path: WASM filters with the Rust SDK, external processing over gRPC, or a native Rust HTTP filter.
6 pages
In this group
- Extending ArionChoose between a WASM filter, an external processing service, or a native Rust filter to run your own logic in the request path. Read →
- WASM filtersLoad a WebAssembly module into the HTTP filter chain: the wasm build feature, the filter config, plugin configuration, and instance lifecycle. Read →
- Rust SDKWrite a WASM filter in Rust: the arion_plugin entry point, lifecycle hooks, typestate handles, and building the module. Read →
- Callouts and shared stateAsync HTTP and gRPC callouts, timers, and host-backed shared memory for WASM filters: atomics and versioned compare-and-swap blobs. Read →
- External processingStream requests and responses to a gRPC service you run: processing modes, mutations, timeouts, failure mode, and per-route overrides. Read →
- Native HTTP filtersHow a native filter is wired into the Arion binary: the config enum, the type URL registry, the runtime dispatch, and per-route overrides. Read →