What leaves my environment?
It depends on which part you use. We state each flow separately.
Playground, no account
The pre-generated examples run entirely in your browser; running them makes no request to Telamin’s compiler. Examples that generate or interpret your own processor send its graph model to the hosted compiler, as described below, and ask you to sign in first.
Hosted generation
Generating a processor sends its graph model to the hosted compiler: each node’s class, callback signatures, wiring and handled events, and its configured field values, private fields included, in clear text. Don’t put credentials or other secrets in node fields; supply them at runtime, after the processor is built. The Fluxtion README lists exactly what is sent.
The compiler does not keep the graph or source you send; your account’s usage ledger records a hash of each request, not its content. A generated result is kept for 24 hours, so that a request retried after a lost response can still collect it, and is then deleted. Sign-in is provided by WorkOS, and hosting by Railway and Cloudflare. The playground privacy notice has the details.
The Analyser and your AI assistant
The Analyser runs on your machine and has no telemetry. It contacts Telamin only when you ask it to: signing in to a compiler account, or downloading a starter project or skill pack. If you use the built-in assistant with your own API key, the Analyser sends the conversation and the context it reads to that AI provider; an external assistant connected through the local MCP bridge sends what it reads to its own provider. Either way it goes to the provider you chose, under your agreement with them.
How can we deploy?
Embed a generated processor in your own Java application, or host it on Mongoose. Generation runs as a hosted service today; private generation, a generator you deploy yourself under a production licence, is In development