Wanaku is live · free · last verified 30 Oct 2026 · viability monitor
Wanaku
Open-source governed action proxy that runs MCP tool calls through Apache Camel routes, with policy and audit enforced before agents touch
Wanaku earns its place when your agents must act on systems you already run and someone will ask you to prove what happened. Executing the Camel route inside the proxy, rather than forwarding the call, is a genuinely different posture from a traffic gateway. Just budget for Java and Camel fluency, and watch the Barn-to-Next runtime transition before you customize deeply.
Verdict generatedVerified 7h ago · liveness 60/100 · cite: rightaichoice.com/tools/wanaku
- Integration developers who want to publish existing Apache Camel routes as governed MCP tools
- Teams whose AI agents must act on enterprise backends under policy and audit
- Organizations that need credentials and governance kept outside the agent
- Kubernetes-based production deployments of self-hosted agent infrastructure
- Non-technical teams wanting a no-code integration or connector platform
- Python-only shops unwilling to learn Java and the Apache Camel route DSL
- Projects that only need a thin MCP passthrough with no routing logic
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Wanaku if nobody on your team writes Java or Apache Camel routes and you don't want to acquire that skill — the governance only works once an integration developer has published the route.
Nothing is charged for the software, but the Camel routes and service templates you need are engineering work your team pays for in developer time before the first governed tool call runs.
Wanaku is Apache-licensed open-source software at $0, so the pricing comparison that matters isn't tier versus tier — it's build-and-run-it-yourself against a commercial agent gateway or MCP platform with a subscription and a support contract. For teams with existing Camel skills the total cost is mostly hosting plus route-writing time; for teams without them, add the cost of learning a Java integration framework on top.
In short
Wanaku — Open-source governed action proxy that runs MCP tool calls through Apache Camel routes, with policy and audit enforced before agents touch. Best for Integration developers who want to publish existing Apache Camel routes as governed MCP tools, Teams whose AI agents must act on enterprise backends under policy and audit, Organizations that need credentials and governance kept outside the agent. Free to use.
What is Wanaku?
Wanaku — Open-source governed action proxy that runs MCP tool calls through Apache Camel routes, with policy and audit enforced before agents touch. Best for Integration developers who want to publish existing Apache Camel routes as governed MCP tools, Teams whose AI agents must act on enterprise backends under policy and audit, Organizations that need credentials and governance kept outside the agent. Free to use.
Wanaku is an open-source governed action proxy for AI agents. It sits between an agent and the backends it acts on, intercepting tool calls, agent-to-agent messages and inference traffic. Integration developers write Apache Camel routes and publish them as tools; agents supply parameters, but Wanaku executes the work itself rather than forwarding the call. The point of that design is accountability. Policy, identity, data controls and audit live in the proxy layer, so an agent never holds credentials to a database, queue or SaaS API and cannot route around governance. Roughly 300 Apache Camel components are exposed as MCP tools, covering HTTP, Kafka, FTP, SQL databases and GitHub, and a SQL tool service template handles connecting LLMs to relational databases. Recent releases push it toward production use. The 0.2.0 release on July 23, 2026 added hardening work, security improvements, a Kubernetes operator and better developer tooling; the 0.1.3 line before it brought GitHub tools, non-blocking MCP operations and a Quarkus 3.33.2 upgrade. Two runtimes are documented — the Java/Quarkus Wanaku Barn and a Rust-based Wanaku Next marked pre-release. This is infrastructure for people who already think in Camel routes. If your shop lives in Java and Quarkus, publishing governed MCP tools is a short step. Teams wanting a no-code connector, or a Python-first stack, will find the entry cost real. Positioned against commercial agent gateway vendors, Wanaku's argument is open source plus execution-in-proxy rather than traffic passthrough.
Key features
- Executes tool calls through Apache Camel routes rather than forwarding to backends
- Intercepts tool calls, agent-to-agent messages and inference traffic
- Enforces policy, identity, data controls and audit inside the proxy
- Keeps backend credentials out of the agent's hands
- Exposes 300+ Apache Camel components as MCP tools
- SQL tool service template for querying relational databases over MCP
- GitHub tools integration
- Non-blocking MCP operations
- Kubernetes operator for production deployment
- Service templates for reusable integrations
- Custom Wanaku Capabilities SDK in plain Java
- MCP router
- CLI and web UI for setup and management
- Java/Quarkus (Wanaku Barn) and Rust-based (Wanaku Next, pre-release) runtimes
Behind the verdict
The first question with any agent-governance tool is where the credentials live. In Wanaku they don't live with the agent at all — the proxy holds them, runs the route, and logs the result. That single architectural choice answers most of the audit questions that show up after an incident, and it's the reason we'd shortlist it. Pick this if you already run Apache Camel. The 300+ components mean the connector for your mainframe adapter, Kafka topic or SQL database probably exists, and integration developers can wrap a route as a governed MCP tool without learning a new programming model. The July 2026 Kubernetes operator matters here too: it turns a demo into something an ops team can actually deploy and upgrade. Pass if nobody on the team writes Java or the Camel DSL. There is no no-code path, and a Python-only shop will spend more time on the ramp than on the agents. Same answer for teams that just need a thin MCP passthrough — you'd be paying governance complexity for a problem you don't have. Watch the runtime split. Docs describe both the Java/Quarkus Barn and a Rust-based Wanaku Next that is still pre-release. If you plan heavy customization, pin to one and keep an eye on which gets the feature work, because that's the kind of churn that hurts six months in. In practice the SQL tool service template is the fastest way to see whether the model fits: point it at a relational database, run a handful of queries through MCP, and inspect what the proxy logged. That tells you more than any architecture diagram. The closest alternative depends on your gap. If you need execution logic and governance together, this is the open-source option worth testing against commercial agent gateways. If you only need cataloguing and access control in front of existing MCP servers,
Limitations
- Wanaku is an action proxy, not a model provider — it ships no AI models of its own and works through the MCP standard to link agents to external systems.
- Adopting it requires integration developers to build Apache Camel routes and publish them as tools, which is a real ramp if nobody on the team has touched Camel or Quarkus.
- The project is young: 0.2.0, the release that added the Kubernetes operator and production hardening, shipped July 23, 2026, and GitHub tools plus non-blocking MCP operations only arrived with 0.1.3 on June 5, 2026.
- Documentation currently covers two runtimes, the Java/Quarkus Wanaku Barn and a Rust-based Wanaku Next marked pre-release, so teams should decide which one they are standardizing on before investing in deep customization.
- Policy, identity and audit are only as good as the routes you write against them.
as of 2026-10-10
Researching Wanaku? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Is Wanaku still active?
Wanaku is live · free · last verified 30 Oct 2026 · viability monitor.
Viability score
How well maintained and how widely used is Wanaku? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: October 2026
How we score →What's new in Wanaku
Checked 4 days agoAcross the latest 4 updates: 1 launch, 1 changelog entry and 2 news mentions.
Wanaku 0.2.0 Released: Production Hardening and Enhanced Security
Wanaku 0.2.0 brings production hardening, enhanced security, a Kubernetes operator and improved developer tooling, marking a major step toward enterprise readiness.
Building an MCP SQL Tool for LLMs with Wanaku and Apache Camel
A walkthrough of using Wanaku's SQL tool service template to connect LLMs to relational databases over MCP for real-time queries.
Wanaku 0.1.3 Released
Adds GitHub tools, service template improvements, non-blocking MCP operations, and upgrades to Quarkus 3.33.2.
Welcome to the New Wanaku Website
Launched a new website with a homepage, blog, community page, and reorganized documentation, including docs for the Rust-based Wanaku Next and the Java/Quarkus Wanaku Barn.
What do users say about Wanaku?
What people actually say about Wanaku — is it worth it?
We scanned public community sources for Wanaku on Aug 5, 2026 and could not establish that the discussion we found is about this tool rather than something else sharing its name. Our own analysis of that scan says the posts were off-subject. Rather than publish a sentiment score built on the wrong subject, we publish nothing here and re-run the scan.
How we verified this
Every listed fact about Wanaku— pricing, features, links, status — is re-read from the vendor's own pages by our verification pipeline and each change is logged with a date; the last pass ran on 30 Oct 2026. Pages mix model-assisted synthesis with human review; see how we verify.
Verification history
We have re-verified Wanaku 11 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — changed pricing tiers, who it suits, who should skip it, our verdict, summary, features, description
- — changed setup time, hidden costs, limitations, pricing fit, switching in, our verdict, who should skip it, who it suits, switching out, description, features, summary, use cases
- — changed who should skip it, summary, our verdict, features, pricing tiers, description, integrations, who it suits
- — changed pricing tiers
- — changed limitations
- — changed who should skip it, who it suits, description, our verdict, features, hidden costs, limitations, switching in, switching out, pricing fit, setup time, summary, use cases
Showing the 6 most recent of 11 verification passes.
Free to cite with attribution — this page re-verifies continuously.
How much does Wanaku cost in 2026?
Wanaku: Free to use. Pricing last verified 30 Oct 2026.
Plans compared
Every published Wanaku tier, its price as the vendor publishes it, who it fits, and what it adds over the tier below. The 12-month cost projection follows.
| Plan | Price | Billing | Who it's for |
|---|---|---|---|
| Open Source | Free | — | Platform and integration teams with Java and Apache Camel skills who will self-host and can absorb the operational work of running the proxy alongside their agents.Adds: Starting tier — the whole project under an Apache license at $0: the governed action proxy, 300+ Camel components as MCP tools, the SQL tool template, the Kubernetes operator, the CLI and web UI, and the Java Capabilities SDK. |
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Where the pricing makes sense
The company stage and team size where Wanaku's pricing actually pencils out — and where peers do it cheaper.
Wanaku is Apache-licensed open-source software at $0, so the pricing comparison that matters isn't tier versus tier — it's build-and-run-it-yourself against a commercial agent gateway or MCP platform with a subscription and a support contract. For teams with existing Camel skills the total cost is mostly hosting plus route-writing time; for teams without them, add the cost of learning a Java integration framework on top.
Has Wanaku's pricing changed?
No plan price for Wanaku has moved since we began logging in Aug 2026; the pricing page is re-read on every verification pass.
Who should pick Wanaku?
Pick Wanaku if you are Integration developers who want to publish existing Apache Camel routes as governed MCP tools, Teams whose AI agents must act on enterprise backends under policy and audit, Organizations that need credentials and governance kept outside the agent, Kubernetes-based production deployments of self-hosted agent infrastructure.
Look elsewhere if you are Non-technical teams wanting a no-code integration or connector platform, Python-only shops unwilling to learn Java and the Apache Camel route DSL, Projects that only need a thin MCP passthrough with no routing logic, Teams that want to wait for the Rust Wanaku Next runtime to leave pre-release before standardizing.
Skip it if Skip Wanaku if nobody on your team writes Java or Apache Camel routes and you don't want to acquire that skill — the governance only works once an integration developer has published the route.
GeneratedReal-world workflow fit
Concrete scenarios for the personas Wanaku actually fits — and what changes day-one when you adopt it.
They take an existing Camel route against a customer database, publish it as a Wanaku tool, and point their agent at it. The agent supplies query parameters; Wanaku executes the route and logs the call.
Outcome: The agent reaches production data without ever holding a database credential, and every query is auditable from the proxy layer.
They install the 0.2.0 Kubernetes operator, deploy Wanaku alongside their agent workloads, and register service templates for the internal APIs agents are allowed to touch.
Outcome: Agent integration endpoints scale with the cluster instead of through hand-managed connections, and policy changes ship as config rather than code.
They use the SQL tool service template documented in the June 2026 walkthrough to expose a relational database to an LLM over MCP, with the proxy in the request path.
Outcome: The LLM can run real-time queries against the database while identity checks and query logging happen in Wanaku rather than in the model's prompt.
Use cases
- Route AI agent tool calls to enterprise databases and APIs under enforced policy
- Audit and control agent actions on sensitive systems from the proxy layer
- Expose Apache Camel integrations as MCP tools so agents can reach existing backends
- Scale agent integration endpoints using the 0.2.0 Kubernetes operator
- Build reusable service templates for common enterprise integrations
- Give LLMs governed access to relational databases through the SQL tool template
- Intercept and govern agent-to-agent delegations and inference traffic
- Package custom Java capabilities via the Wanaku Capabilities SDK
Setup time & first value
How long it actually takes to get something useful out of Wanaku — broken out by persona, not the marketing-page minute.
For a developer who already knows Apache Camel and Quarkus, the first governed tool is a matter of hours — write a route, publish it, point an agent at the Wanaku endpoint. For a Python-only team, budget days to weeks for the Camel and Quarkus ramp before the first useful tool exists. Kubernetes deployments add the operator install and manifest work on top.
Switching to or from Wanaku
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From a direct MCP server: repoint the agent at Wanaku and reimplement the backend call as a Camel route published as a tool.
- →From hand-rolled agent tool functions: move the backend logic into a Camel route and let the proxy hold the credentials instead of the agent.
- →From a passthrough API gateway: keep the gateway for traffic and move agent tool execution behind Wanaku so policy and audit sit in the action path.
- ↗To a managed agent-gateway vendor: reimplement each published tool as the vendor's connector format and move policy rules into their console.
- ↗To plain MCP servers: export the route logic as standalone services and accept losing the central policy and audit layer.
Integrations
Resources & guides
Tutorials & Learning
YouTube returned 6 videos for “Wanaku”, and we withheld 4: 4 could not be judged, because “Wanaku” is a single word that other videos use for other things. Showing the 2 we can prove are about Wanaku.
Official links
What are the best Wanaku alternatives?
The closest alternatives to Wanaku we list are Mcp Scanner, Kindly Web Search Mcp Server and FetchSandbox MCP. Ranked by direct product-type match, not category overlap.
| Alternative | Pricing | Starts at | Last verified |
|---|---|---|---|
| Mcp Scanner | Free | Free | — |
| Kindly Web Search Mcp Server | Freemium | Pricing not published | — |
| FetchSandbox MCP | Freemium | Pricing not published | — |
Alternatives to Wanaku
View all
Mcp Scanner
Use Cisco's open-source MCP Scanner to audit MCP servers for tool poisoning, rug pulls, and over-privileged permissions before agents wire
Kindly Web Search Mcp Server
Open-source MCP web search server that gives coding agents live results plus clean full-page extraction.
FetchSandbox MCP
FetchSandbox runs AI coding agent fixes through deterministic API sandbox evals — proving integrations fail before and pass after.
Tools that pair well with Wanaku
Common stack mates teams adopt alongside Wanaku, with the specific reason each pairing earns its keep.
Mcp Scanner
Use Cisco's open-source MCP Scanner to audit MCP servers for tool poisoning, rug pulls, and over-privileged permissions before agents wire
Kindly Web Search Mcp Server
Open-source MCP web search server that gives coding agents live results plus clean full-page extraction.
FetchSandbox MCP
FetchSandbox runs AI coding agent fixes through deterministic API sandbox evals — proving integrations fail before and pass after.
Wanaku vs its closest rival
Wanaku's closest head-to-head is with Spider Cloud — Spider Cloud and Wanaku serve fundamentally different purposes. Spider Cloud is a high-performance web scraping API for feeding real-time data into AI agents, while Wanaku is an MCP router for connecting AI agents to enterprise systems. Choose Spider Cloud if you need fast, cheap web data extraction; choose Wanaku if you need to securely integrate LLMs with internal tools and databases. Verdict generated
Head-to-head comparisons
Wanaku vs Spider Cloud
Spider Cloud and Wanaku serve fundamentally different purposes. Spider Cloud is a high-performance web scraping API for feeding real-time data into AI agents, while Wanaku is an MCP router for connecting AI agents to enterprise systems. Choose Spider Cloud if you need fast, cheap web data extraction; choose Wanaku if you need to securely integrate LLMs with internal tools and databases.
GeneratedWanaku vs Temporal Ai
Choose Temporal AI if you need bulletproof durability for AI agents and long-running workflows, with rich SDKs and human-in-the-loop. Choose Wanaku if your priority is securely routing MCP calls from LLMs to enterprise systems (databases, protocols) with access control and auditing. They solve different problems: Temporal orchestrates execution reliability, Wanaku bridges AI agents to backends.
GeneratedWanaku vs Presto Voice
Presto Voice and Wanaku solve completely different problems. If you run a multi-location QSR wanting to automate drive-thru orders and boost revenue via voice AI upselling, Presto Voice is the purpose-built choice though it requires a sales call for pricing. If you're a developer or team building autonomous AI agents that need secure, scalable integration with enterprise systems via MCP, the free open-source Wanaku router is a no-brainer.
GeneratedFrequently asked questions
Best-of guides
Used Wanaku? Help shape our editorial sentiment research.