every morning,
the same decision, made the same way.
Before the early shift, a container terminal decides how many cranes and carriers each vessel gets. In production, kint takes the same steps for that decision each day. Last night's data comes in, the model solves, the stated rules are checked, and the plan waits for the shift lead's release. Each step lands in the record, and kint calls that sequence a workflow.
- Steps 1 to 5 · kint
- data in, plan solved, rules checked
- Step 6 · the shift lead
- approves the plan or objects
- Steps 7 and 8 · your systems
- back through your API, on record
each decision gets its own sequence of steps.
kint's forward deployed engineers (FDEs) build each decision with your team. Together they work out what it takes to make it well. That means which data, which model, which checks and who signs off. kint calls that sequence a workflow. An approved workflow runs whenever your systems call it. A person on your team releases each plan before it is written back.
work out the steps
Where the data lives, what has to be estimated, which rules must hold and who approves the result.
build the workflow
Steps for data, models, checks and people, joined in the order the decision needs. kint's decision agent drafts steps; a person reviews each one.
release it into production
A released version runs whenever an outside system calls it. A new version is released on purpose, and can be withdrawn.
from last night's data to an approved shift plan.
An illustrative container terminal. The workflow runs before the early shift. The decision stays with the shift lead. The workflow makes sure it rests on checked data and on a plan with a stated gap to the best one within the rules.
interrupted, it resumes. questioned, it shows its work.
after a restart, the run continues.
After a crash or restart, the run continues at the step where it stopped.
inputs, outputs, version and who acted.
A run pins the workflow version and the data snapshot it used, so the plan can be re-checked against the record.
released on purpose.
A person reviews and releases each workflow version. A release can be withdrawn; the runs it made stay on record.
asks, then continues.
Missing data, an open question or an approval: the run pauses and goes on when someone answers.
change one input. compare.
New data or a changed parameter starts a new study, comparable with the last one.
watch it run.
Every step shows its state while the run works: running, waiting for you, done.
ten kinds of step, combined per decision.
kint's FDEs assemble each decision from these steps, with the planners. Steps run in parallel where they can, loop with a cap and send failures to a handler step. A run starts when one of your systems calls.
- fetchRead the data the decision needs, as read-only exports.
- prepareProfile the data, read column meaning, fill gaps and mark them as estimates.
- model and solveSolve an exact model, fit and search a surrogate, or fit the learned parts and then solve exactly.
- aiA single language model call, a tool-using agent, or a plain-language explanation of the result.
- mcp toolsMCP tools as workflow steps are on the roadmap.
- checkThe plan is checked against the stated rules before it goes to approval.
- peopleWait for an answer, a missing value or an approval, then continue.
- report and notifyPut the result where the team reads it.
- write backApproved plans only, through an API you control.
- composeReuse a whole workflow as one step, or loop it over many items.
the agent proposes. your people decide.
the agent drafts and explains.
- draftsDrafts the steps of a decision with planners and kint's FDEs.
- narratesExplains a run in plain language while it works.
- proposesSuggests a change; your team decides.
- asks firstAsks when something is unclear, before it drafts further.
your people see what needs them.
- rolesPlanner, approver, reader: roles separate who may model, run, release and read.
- inboxOpen questions and approvals in one place, answered in bulk.
- the run viewEach run as named step groups. Internals stay folded.
- the resultThe plan with its binding limits, studies side by side.
Both act inside the same run and leave their mark in the record. Every run ends in one of three places: an approved plan, a decision waiting for a person, or a documented hand-over.
a run, step by step.
Each step shows its state while the run works, and the finished run keeps every check with it.
Loading the product screen
bring the decision your team makes every morning.
We work out its steps with the planners, build the workflow and run it on real data. You see each step, and the plan waits for your release.
- Steps
- Fetch · prepare · model · check · approve · write back
- Record
- Every step with inputs, outputs, version and who acted
- Back to your systems
- Only through an API you control
- Contact
- hello@kint.pro