Crosser Concepts

Crosser Control Center
The Crosser Control Center is the part of the solution where the users spend most of their time. This is where you design, test, deploy your Flows and manage resources, credentials, Nodes and so on.

It acts as a centralized control plane which allows you to control all Flows on all Nodes in your organization.

We offer the Control Center as a SaaS application which runs in Microsoft Azure, but it can also be installed on-prem if that is required.

Flows
Flows are a combination of modules which represent your use case. You build Flows in the Control Center using pre-defined modules or using custom code functionality. Once tested you can deploy your Flow(s) to one or multiple Nodes depending on where you want to execute that logic. Flows are version controlled in the Control Center. Every Flow will end up as an isolated process once deployed in a Node and you can run multiple Flows in parallel on one Node.

Crosser Node
The Crosser Node is the runtime for Flows. The Node can either be installed as a single docker container (preferred) or as a Windows Service, if that is required.

The Node itself is a use-case independent and hardware agnostic runtime which communicates outbound via HTTPS to the Control Center. Due to this concept you have full control over every Node in your environment.

Working with Crosser

The starting point is the Flow Studio which is a tool in the Control Center. Here you find the module library which holds hundreds of pre-build modules, ready for you to use. Based on your use case you pick the relevant source, analytic and destination modules, plug them together and specify setting to realize your integration or data processing pipeline. Afterwards you connect into a Node to test and verify the logic. Once you are happy with the result, you deploy the Flow to one or multiple Nodes depending on where the Flow should be executed.