The Fluxtion starter and playground. No-friction development, right in your browser.
New to Fluxtion? Read the developer guide.
One graph, four stops on the path. You begin embedded and interpreted, running straight in the browser, which is keyless. From there you grow into real I/O, host the graph inside Mongoose, then deploy it as a native binary. Everything below is a project you can run.
Fluxtion in your app
The graph runs inside your app. You feed events straight in and it reacts, with no server and no infrastructure. The quickest way to get a feel for the model.
Feeds → graph → sinks
Wire up real inputs and outputs. File or in-memory feeds flow into the graph and named sinks take the results, all run on an agent thread. A proper multi-input, multi-output graph.
The same graph, hosted
Run the same graph inside a Mongoose server. Connector plugins handle the enterprise integration for Kafka, files and the rest, with agent threads and an admin web console. One artefact, two runtimes.
Zero-overhead start-up
Compile the AOT graph to a GraalVM native image. It starts in milliseconds, with no JVM warm-up and no compiler at runtime.
Start from a community example or publish your own from any GitHub gallery. Every template opens here as a real, runnable project.
Connect a hosted graph to the enterprise with ready-made plugins for Kafka, files and more. Browse the catalogue for the industrial server tier.
The cloud service is a hosted source generator. For a downloaded project, the builder sends your graph to the service and gets back the dispatcher or optimised event processor, so you never install a generator toolchain yourself.