Integration flows you can read.

Pipebase is a visual designer for Apache Camel. Every flow is plain Camel YAML, and it runs on a Pipe on your own machines.

Apache Camel 4 runtime · Flows stored as Camel YAML · Hosted beta: Germany

Webhookplatform-http:/ordersSet bodysimple: ${body}Logreceived

Live YAML — what will deploy

- route:
    id: orders
    from:
      uri: platform-http:/orders
      steps:
        - setBody:
            simple: ${body}
        - log: received

What makes it different

Camel YAML you can keep

Flows are Apache Camel YAML files you can read and keep. Pipebase runs Apache Camel 4.18.

A visual editor for that YAML

The visual editor reads and writes that YAML. A live drawer shows the YAML that will deploy.

Flows run on your Pipe

A Pipe runs your flows on a Docker host you control. It dials out to the designer over a single outbound WebSocket. The designer never connects in, and nothing on your side needs to be reachable from the internet.

Self-hosted today, in the hosted beta at launch

These work on a self-hosted install today and will be in the hosted beta at launch. Self-hosting itself comes when the source opens. What self-hosting adds

FeatureSelf-hostedHosted beta
Flow testsTodayAt launch
Live data on the canvasTodayAt launch
Live TraceTodayAt launch
LogsTodayAt launch
Event Designs and the Pulsar meshTodaySelf-hosted only

Planned for the hosted beta

The first ten minutes

You need Docker on a machine you control.

  1. Create your tenant.

  2. Start your Pipe with one docker run command.

    docker run -d --name pipebase-pipe --restart unless-stopped \
      -e PIPEBASE_RUNTIME_ID=… \
      -e PIPEBASE_DESIGNER_URL=… \
      -e PIPEBASE_PIPE_TOKEN=… \
      -e PIPEBASE_DEPLOY_TOKEN=… \
      -v pipebase-routes:/opt/pipebase/routes \
      ghcr.io/…/pipebase-runtime
    The four values come with your tenant.
  3. See your Pipe come online in the designer.

  4. Run your first flow.

The free beta

planned

The beta will be free, with no card. No SLA. Hosted runtimes: later. The beta will open with a small number of seats.

Pricing

Where it fits

If you use SAP Cloud Integration

SAP describes Cloud Integration's integration flows as transformed, at runtime, into a structure compatible with Apache Camel. In Pipebase, the Camel route file is what you edit and keep.

SAP's description

If you used MuleSoft Community Edition

MuleSoft's Mule Community Edition is licensed under CPAL-1.0, and its GitHub repository is archived. Pipebase flows are plain Apache Camel YAML, and when the repository opens, the runtime will be published under Apache-2.0.

If you want to run it yourself

Self-hosting comes when the source opens. It adds a central runtime, so live data, flow tests, Live Trace, Logs and the run monitor work.

Self-host

Not yet

  • Hosted runtimes: later.
  • Not in the beta: Mesh, Event Designs, Schemas, pools and custom domains.
  • AMQP 1.0 is not supported.
  • No date yet.

Questions

Is it open source?

Not yet. When the repository opens, the designer will be published under AGPL-3.0 and the runtime under Apache-2.0. No date yet.

Where do my flows run?

In the hosted beta, on your Pipe, on a machine you control; no flow code will run on our host.

What does the designer receive from my Pipe?

This is planned for the beta. For each run, your Pipe will send the designer the route, status, duration and error text. It will send every warning- and error-level log line, including what your flows log at those levels, and a resource sample every ten seconds. Message bodies and headers will reach the designer only in the live traces and test runs you start, unless you switch previews on. Each time it connects, a Pipe reports its hostname, operating system and architecture, runtime version, CPU count and memory, and the designer stores the address it connected from. Today a self-hosted Pipe also sends a 200-character body preview and up to ten header values with every run record. How it works

Does it need Docker?

Yes. You need Docker Engine or a compatible runtime on a Linux x86-64 machine you control; only Docker has been tested.

What does the beta cost?

Nothing: the beta will be free, with no card.

Can I self-host instead?

Not yet: self-hosting comes when the source opens. What it adds

Is my data in the EU?

The hosted designer will run on our server in Nuremberg, Germany. Your flows and their data will stay on your Pipe, apart from what the Pipe sends to the designer. This site is hosted by Hetzner in Germany. Mail you send us is routed by Cloudflare, a US company, to a mailbox at a Swiss provider, which stores it in Switzerland, Germany or Norway. Providers

Is there a date?

No date yet. hello@pipebase.dev