Camel YAML you can keep
Flows are Apache Camel YAML files you can read and keep. Pipebase runs Apache Camel 4.18.
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
Live YAML — what will deploy
- route:
id: orders
from:
uri: platform-http:/orders
steps:
- setBody:
simple: ${body}
- log: received
Flows are Apache Camel YAML files you can read and keep. Pipebase runs Apache Camel 4.18.
The visual editor reads and writes that YAML. A live drawer shows the YAML that will deploy.
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.
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
| Feature | Self-hosted | Hosted beta |
|---|---|---|
| Flow tests | Today | At launch |
| Live data on the canvas | Today | At launch |
| Live Trace | Today | At launch |
| Logs | Today | At launch |
| Event Designs and the Pulsar mesh | Today | Self-hosted only |
Planned for the hosted beta
You need Docker on a machine you control.
Create your tenant.
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-runtimeSee your Pipe come online in the designer.
Run your first flow.
The beta will be free, with no card. No SLA. Hosted runtimes: later. The beta will open with a small number of seats.
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.
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.
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.
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.
In the hosted beta, on your Pipe, on a machine you control; no flow code will run on our host.
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
Yes. You need Docker Engine or a compatible runtime on a Linux x86-64 machine you control; only Docker has been tested.
Nothing: the beta will be free, with no card.
Not yet: self-hosting comes when the source opens. What it adds
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
No date yet. hello@pipebase.dev