Post

1/4 Wanaku is evolving — and our MCP routing ecosystem now uses both Rust and Java. The core routing engine is moving to Rust, while the Camel Integration Capability, CLI, and Kubernetes Operator remain Java/Quarkus. Why? Different problems, different strengths. 🧵

Otavio R. Piske

@orpiske.net

2/4 The Rust side is becoming our LLM / A2A / MCP routing engine, built on Praxis. Its filter pipeline handles namespace isolation, conversation classification, tool execution, response interception — and WASM-based governance, with custom logic written in Rust or JavaScript.

18/8/26, 6:47 am0 reposts0 likes

Otavio R. Piske

@orpiske.net

18 Aug

3/4 Java isn’t going anywhere. Wanaku Barn remains the home for the Camel-based integration layer, CLI, Kubernetes Operator, service catalogs, templates, and artifact registry. Rust handles the proxy/routing problem. Java + Camel handles enterprise integration.

Otavio R. Piske

@orpiske.net

18 Aug

4/4 Camel’s evolving AI capabilities also let us simplify the architecture: we’ve removed the old gRPC bridge and are starting fresh where it makes sense. One month from concept → working router with WASM evaluation, admin UI & single-binary deployment. Open source: github.com/wanaku-ai

github.comWanaku MCP RouterWanaku MCP Router. Wanaku MCP Router has 13 repositories available. Follow their code on GitHub.