Planned for the hosted beta
How it works
In the hosted beta, the designer will run on our server in Nuremberg, Germany. Your flows will run on your Pipe, on a machine you control; no flow code will run on our host.
Where things run
A Pipe dials out to the designer over a single outbound WebSocket. The designer never connects in to your Pipe; nothing on it has to be reachable from the internet.
Stored in the hosted designer planned
The hosted designer will store these in your tenant's own volume on our host in Germany:
- your flow definitions
- mappings
- parameters
- connection settings
- the secrets you enter
Sent by your Pipe planned
In the beta, your Pipe will send the designer:
- for each run, the route, status, duration and error text;
- every warning- and error-level log line, including what your flows log at those levels;
- a resource sample every ten seconds;
- message bodies and headers only in the live traces and test runs you start, unless you switch previews on.
Self-hosting adds a central runtime beside your Pipes. It comes when the source opens. Self-host
What a self-hosted Pipe sends today
The planned list above needs a runtime release that is not out yet; until then, a Pipe sends this:
- For every completed or failed run: the route, status, duration and error text, plus a 200-character body preview and up to ten header values.
- Every warning- and error-level log line: the logger, the message, and the exception's class and message.
- A resource sample every ten seconds: load average, JVM memory used and maximum, route count, in-flight exchanges and JMS queue depth.
Each time a Pipe connects
It reports its hostname, operating system and architecture, runtime version, CPU count and memory, and the designer stores the address it connected from.
Environments as Pipes
Environments are runtimes: dev, test, stag and prod. Each Pipe is tagged with its environment. You promote a flow from one environment to the next, and parameters can take a different value in each environment.
This is how the designer works on a self-hosted install today; the hosted beta will keep it.
Requirements
- Docker Engine or a compatible runtime on a Linux x86-64 machine you control; only Docker has been tested.
- The Pipe image is built for x86-64 only; Apple Silicon Macs run it under emulation, which we have not tested.
- Your Pipe needs outbound HTTPS (port 443), and nothing on it has to be reachable from the internet.