Ignition software · module catalog

Modules for capability that belongs beyond one project.

i4Cortex modules package repeatable Ignition capability into supported software. This is the home for the current module catalog and future platform extensions.

i4Cortex module layerReusable capability, delivered as software.

Components, integration logic, and specialist workflows that belong above the project layer.

01 / VISUALIZEAdvanced interfaces
02 / INTEGRATESpecialist workflows
03 / STANDARDIZEMulti-project reuse
04 / SUPPORTVersioned delivery
Module catalog

Each card is a distinct supported module. Details, documentation, pricing, and trials belong on the individual module page.

COMING NEXT

Future module

New i4Cortex modules will appear here as separately supported products.

Why a module

Use a module when the capability should outlive a single project.

Modules are for platform-level requirements that need an intentional release, documentation, compatibility path, and support model.

Custom module development

A focused extension for a requirement unique to your operation.

When an integration, component, or workflow should become a maintained platform capability, i4Cortex can help define the boundary, build the module, and enable the team that will own it.

Discuss a Custom Module
01Feasibility and platform fit
02Public contract and UX definition
03Implementation and compatibility
04Documentation and team handover

Start with vCortex—or define the module your project is missing.

Explore the current product or bring us the platform-level problem you need to solve.