Connect what you have.
Feeds adapt incoming events. Services provide shared capabilities. Sinks publish decisions to the systems that need them.
HOW IT WORKS / RUNTIME AND PLUGINS
Run the application.
Connect the systems you have.
Fluxtion compiles the coordination. Mongoose provides the runtime host. Plugins connect your application to real feeds, services and outputs—without asking an LLM to rebuild the surrounding infrastructure.
Run your compiled processors.
Mongoose hosts the compiled Fluxtion processors and manages their configured lifecycle and event delivery.
Explain the observed outcome.
Open selected records in the Analyser with the matching application context. Investigate with or without an AI assistant, then export the findings for others to examine.
THE ROLE OF MONGOOSE
Give the application
an operational home.
Your compiled processor knows how its components work together. Mongoose supplies the surrounding runtime: event delivery, processor execution, service wiring and startup and shutdown.
Keep coordination out of the business code.
Mongoose manages configured feeds and processor groups, so your application can focus on its rules. Within a processor’s event loop, events are handled serially; the server can run separate groups on different threads. External services and shared state still need appropriate integration.
Fit your deployment.
Run Mongoose as a standalone Java application or embed it in a larger JVM application. Use your own machines, containers or cloud environment. A processor built ahead of time needs no hosted compiler request for each production event.
Explore MongooseREUSE THE CONNECTIONS
Plugins carry the infrastructure work.
Choose the modules your process needs. A feed brings events in; a service provides a capability; a sink carries results out. Reuse those connections across applications and keep their configuration separate from business rules.
Bring events in.
Connect to files, Kafka, Aeron, Chronicle or multicast. The selected feed plugin adapts incoming data to the application’s event flow.
Value: less repeated input and transport code to author and maintain.
Supply shared capabilities.
Use services for reference-data caches, JDBC access, loading and administration. Configure the capabilities the application needs.
Value: reuse operational and data-access building blocks.
Deliver results.
Configure supported output connectors for files or messaging systems. Keep the business decision separate from the mechanism that publishes it.
Value: integrate with existing downstream systems without rewriting the decision logic.
Plugins have specific contracts and delivery behaviours; choose and test them for the workload. Some integrations need adapters. Browse the maintained plugin catalogue.
ONE EXAMPLE DEPLOYMENT
An order check in its working environment.
A proposed deployment pattern, not a claim about the connectors used in the downloadable order demonstration.
Receive the request.
A configured feed receives an order from a file or messaging system.
Apply the business rules.
The compiled application uses the order and supplied reference values to calculate, check and decide.
Publish the outcome.
An output plugin sends the decision to the next system. Configure and test the required failure and delivery behaviour.
Investigate the run.
Configured audit records go to storage you choose. A person and their LLM direct the Analyser to inspect them and produce an evidence bundle.
TWO WAYS TO RUN
Mongoose, or your own host.
Use Mongoose when you want its runtime and plugin system. Embed the generated processor directly when your existing application already owns the surrounding lifecycle and integration.
Keep your deployment responsibilities explicit.
Your team controls runtime configuration, credentials, network access, storage, monitoring and recovery. Mongoose is not a hosted Telamin runtime service, and it does not automatically cluster servers or replicate processor state.
EXPLORE THE NEXT STEP
Walk through the connections your process needs.
Start with the feeds, services and outputs you already use. A pilot can test the integration, runtime behaviour and evidence needed for your deployment.