pmsudhi/cameleer repository overview

⁠Cameleer

Apache Camel routes, rebuilt in Rust. If you know Apache Camel⁠, you already know Cameleer: the same YAML DSL, endpoint URIs, Enterprise Integration Patterns and Simple expressions, in a single native binary.

• 450x faster startup than Apache Camel (3 ms vs 1.1 s), up to 54x less memory, 1.7–8.7x the throughput in every scenario (comparison⁠)
• About 230 components: Kafka, HTTP/REST, AMQP, MQTT, JMS, SQL/PostgreSQL, Redis, MongoDB, AWS, Azure, GCP, OpenAI, Slack, files, FTP/SFTP and more
• Routes as MCP tools for AI agents (--mcp, or --mcp-stdio for Claude Desktop): schema checks, approvals, run-once, timeouts and audit on every call; official MCP conformance 39/39 and 26/26 (MCP⁠)
• Built for AI agents (the integration and action layer), serverless and the edge
• Image: one native binary on distroless, linux/amd64 and linux/arm64, non-root, no shell, about 20 MB to download

Website: https://cameleer.ing/⁠ · Source: https://github.com/pmsudhi/cameleer⁠

⁠Quick start

Save a route as hello-api.camel.yaml:

- rest:
    path: /orders
    get:
      - path: /{id}
        to: direct:getOrder
- route:
    from:
      uri: direct:getOrder
      steps:
        - setBody:
            simple: '{"id": "${header.id}", "status": "shipped"}'

Run it and call it:

docker run --rm -p 8080:8080 -v "$PWD:/routes:ro" pmsudhi/cameleer run /routes/hello-api.camel.yaml
curl localhost:8080/orders/42        # {"id": "42", "status": "shipped"}

Any route written for Apache Camel's YAML DSL runs the same way.

⁠Real use cases

Each of these runs end to end in the project's test suite. Each file's header lists the environment variables it needs.

docker run --rm -e KAFKA_BROKERS=kafka:9092 -e OPENAI_API_KEY \
  -v "$PWD:/routes:ro" pmsudhi/cameleer run /routes/ai-ticket-triage.camel.yaml

⁠Tags

The same image is published to ghcr.io/pmsudhi/cameleer. Every push carries an SBOM, build provenance and a GitHub attestation: gh attestation verify oci://ghcr.io/pmsudhi/cameleer:latest --owner pmsudhi.

⁠Configuration

Kubernetes, Docker Compose and Cloud Run setups are in the deployment guide⁠.

⁠A smaller image

This image includes every component. To build one with only the component families your routes use, clone the repository and pass them as FEATURES:

docker build --build-arg FEATURES=cloud,jq -t my-cameleer .

A feature list replaces the default, so name every family you use (templates, jq, xpath, http2 and validate are features too). The build features guide⁠ lists them and what each adds.

⁠Rust crates and CLI

The same engine is on crates.io: cargo install cameleer-main gives you the CLI, and cameleer-core and the component crates let you embed it in your own Rust program.

⁠License

Apache License 2.0. The license and NOTICE are in the image under /usr/share/doc/cameleer/.

Cameleer is an independent project. It is not affiliated with or endorsed by the Apache Software Foundation. Apache, Apache Camel and Camel are trademarks of the ASF.