YOUR QUESTIONS. ONE CONNECTED SYSTEM.

Build faster.
Run with control.
Explain the result.

AI helps you assemble the application. Fluxtion compiles its coordination. Mongoose runs it. The Analyser turns recorded behaviour into an investigation your team can act on.

01

How do I build it?

LLM + FLUXTION SKILLS + ANALYSER

Give AI a smaller job.
Build a more capable system.

Describe the outcome and constraints. Your AI coding assistant uses Fluxtion skills and working examples to select components and write the application-specific logic. The compiler handles their coordination; the Analyser closes the loop with recorded behaviour.

What you gain

Less glue to generate, fewer tokens spent rediscovering integration, and a bounded task that makes smaller models a practical option for more complex applications.

Explore AI-assisted authoring
Human intent guides an AI assistant using skills and reusable components. Fluxtion compiles the coordination; the Analyser informs the next checked change.
The model focuses on intent and components. Compilation and recorded feedback supply structure instead of another long prompt.
02

What makes execution predictable?

FLUXTION COMPILER

Compile the coordination.
Deploy the resulting software.

Fluxtion builds the event orchestrator from your components and their dependencies. Dispatch and propagation become explicit generated code your team can inspect, test and approve. The deployed application executes that code; it does not ask the authoring LLM what to do next.

What you gain

Repeatable orchestration under defined inputs and state, with less hand-written coordination to review and maintain.

Inside the platform: determinism explained
Components and dependencies become a generated orchestrator, reviewed application and repeatable event execution.
The coordination is resolved at build time. The generated processor calls the application components at run time.
03

Can I use what we already trust?

FLUXTION COMPONENT INTEGRATION

Don’t rewrite it.
Reuse it. Rewire it.

Bring supported third-party libraries and in-house components into the same application. Your team guides the AI’s selection; Fluxtion derives their event coordination. Keep the useful engineering already done and add the business logic that makes your application different.

What you gain

Less replacement code for the LLM to get wrong, more reuse of reviewed capabilities, and integration work you can carry into the next application.

See the reusable integration advantage
Existing vendor and in-house components are selected with human-guided AI, coordinated by Fluxtion, operated by Mongoose and investigated in the Analyser.
Use supported component contracts to turn library adoption into assembly rather than repeated orchestration work.
04

Where does it run?

MONGOOSE OR YOUR EXISTING APPLICATION

Your application.
Your infrastructure. Your data.

Run the compiled application on Mongoose for feeds, sinks, lifecycle and operational controls, or embed it in your own application. Deploy in your environment and keep processing there. The generated application does not need a call to the hosted compiler for each event.

What you gain

Choose the operating model that fits your systems. Keep ownership of deployment and avoid an authoring-service dependency in the compiled execution path.

Explore deployment and enterprise fit
Your review and delivery controls lead to an embedded application or Mongoose host, with operational evidence for investigation.
Mongoose is Telamin’s server software, not a requirement to send production events to a Telamin-hosted service.
05

How does it connect to my systems?

MONGOOSE PLUGINS

Connect the systems
you already run.

Mongoose plugins connect your application to event streams, services and outputs. Use connectors for Kafka, Aeron, Chronicle, files or multicast, alongside services for databases, configuration and administration. Choose the plugins your deployment needs and configure them around the same compiled application.

What you gain

Reuse production connectors and operational services. Spend less time building transport plumbing and more time on the business behaviour that makes your application valuable.

Explore Mongoose plugins
Existing event sources connect through Mongoose plugins to the compiled application and its output systems, with shared operational services.
Plugins provide the connections and operating services around your application, so its business logic can stay focused.
06

How do I know what it did?

GENERATED AUDIT HOOKS + ANALYSER + YOUR AI ASSISTANT

Investigate the facts.
Check the change.

Audit instrumentation is built into the generated application; your capture configuration determines the facts it records. The Analyser pairs those logs with the compiled graph and your local source. A connected AI coding assistant can follow the evidence, diagnose a problem and propose a targeted fix.

What you gain

Shorter investigations, a shared explanation grounded in recorded behaviour, and a fix your team can review, test or replay before approval. Export the investigation as an evidence bundle.

See investigation and evidence bundles
Application audit records enter the Analyser with a local AI assistant, leading to a proposed change, test and replay, and a shared evidence bundle.
The same application structure connects the recorded event to the investigation and the checked change.
07

What am I paying for?

GENERATION CREDITS + LEAN COMPILED EXECUTION

Generate when you change it.
Run without a token meter per event.

Hosted compiler credits cover generation and interpretation requests. An ahead-of-time compiled application runs the generated code, so processing another event does not spend another compiler credit or require the authoring LLM. Skills and reusable components also reduce the amount of new code the model must produce.

What you gain

Separate the cost of building from the cost of operating. Fluxtion and Mongoose are designed for low-overhead event processing; measure the runtime savings on your workload.

AI-provider usage, your infrastructure and applicable product licences are separate costs. Talk to us about generation allowances and commercial terms.

Generation and licensing
Generation requests use compiler credits at build time. The approved application is deployed and processes events on your infrastructure without per-event compiler credits.
Build-time generation and deployed execution have different cost models. Hosted interpretation remains a compiler request.

EXPLORE THE NEXT STEP

See the difference on your application.

Bring an existing library, an event-driven workflow or a difficult investigation. We’ll show how the connected system reduces the work between intent and evidence.

Request a walkthrough