Glossary

Lansky​

Lansky is the internal application that executes business calculators within the platform.
It can refer to either the .xlsx calculator file itself or the calculation engine that reads, executes, and returns structured data.
A Lansky uses Excel as its logic layer, allowing complex formulas, iterations, and conditional outputs to be defined directly in spreadsheets. See more about Lansky on the detailed documentation

Watson​

Watson is the document generation system of the platform.
It interprets .docx template files, replaces placeholders with real data, and outputs filled documents in Word or PDF format.
Watson enables easy creation of personalized documents using Microsoft Word’s layout and formatting capabilities. See more about Lansky on the detailed documentation

Schema​

A Schema defines the structure of a page displayed to a customer or broker.
It represents the logical model of a form used to collect and validate data, which is then processed by other components such as Lansky or Watson. See more about Lansky on the detailed documentation

Workflow​

A Workflow is a process defined within Insurgate, composed of multiple steps of data entry and automated actions that a broker or agent follows.
It orchestrates the entire business flow — collecting data, performing premium calculations, generating documents, and interacting with APIs.
Each workflow defines the user journey and logic that guide how data moves through the system, as configured by the Insurgate implementer.

Request​

A Request represents an insurance application or “demand” initiated by a broker or agent.
When a broker starts a new insurance request (“I want to create an insurance demand”), a Request object is created and linked to a specific workflow.
This Request acts as the data container for the entire process — storing all values, results, and documents generated throughout the workflow.
Each Request is unique and maintains its own state, data, and outputs based on the actions performed within its associated workflow.

Paul​

Paul is the core server responsible for orchestrating the entire execution of workflows and requests within the platform.
It instantiates new requests, initializes their associated workflows, and manages every action defined in those workflows.
When new data is received — for example, from a form input — Paul analyzes the workflow configuration and executes all relevant actions, such as recalculations, document generation, or API calls.
In short, Paul is the operational engine that ensures every workflow runs correctly and every request remains up to date with the latest data.