test it on one decision.
then roll it out.
Ports, grid operators, manufacturers, rail companies and utilities buy with care, and they should. kint fits that: a contained pilot on one recurring decision, measured against today's plans, then a rollout one decision at a time. Hosted in Germany. Every decision on record.
one decision first. the next one when your team is ready.
- wherehosted in germanykint hosts and operates the platform for you.
- dataread-only exportsApproved plans go back only through an API you control, and the control system decides whether to apply them.
- recordevery decisionData version, model version, settings and who released the plan.
pilot, review, rollout.
Each phase ends with a result you can take to a board meeting. You decide at every step whether to go on.
one decision
We pick one recurring decision with the planners: crane deployment per shift, a redispatch measure, a renewal list. kint's decision agent builds the model with them, and it runs next to today's plans.
your verdict
In the pilot, kint's forward deployed engineers (FDEs), who work directly with the customer, build the one decision with your team. They review the model with domain experts. Then planners, management and IT look at the results together. Is the model right? Is the gain real? Does it fit the process?
decision by decision
An approved workflow runs whenever your systems call it. A person on your team releases each plan before it is written back. FDEs build the first workflows and join again for each new decision, when the organisation is ready for it. Models, data and records stay in one place.
kint sits next to the systems you already run: an ERP, a terminal operating system, a grid control system, a spreadsheet. Data comes in as read-only exports. Approved plans go back only through an API you control; the control system decides whether to apply them.
At a large operator, regulated, public or private, a planning tool needs more than a convinced planner. Procurement, IT security, the auditor and the works council each need a straight answer. kint is built to give one.
a scoped first order
One decision, one pilot, a fixed scope. No platform commitment before results exist.
hosting in germany
Hosted in Germany and operated by kint. For operations that must not leave your network, we scope an installation inside it.
a record per decision
Data version, model version, release and reason. Each run can be replayed.
the record holds roles and releases. that is all it needs about people.
In Germany the works council has a say in any system that records what employees do, in public and private companies alike. Of the stakeholders above, it asks the most specific questions. Here is kint's answer in full: what is stored, who can see it, and how the agreement shapes it.
- plan
- berth plan, week 41
- released by
- shift planner, terminal 2
- time
- 2026-10-09 06:12
- reason
- crane 4 in maintenance
- What is stored
role and release decisions
The record keeps who released or changed a plan, in which role, and when. Accountability for a decision needs exactly that.
- What it is for
reports compare plans
Reports compare plans, limits and results.
- Who can see it
a view per role
Roles separate who may model, run, release and read the record.
- The agreement
a basis for your works agreement
We give HR and the works council a description of what the system stores, who sees it and for how long. It is a basis for your works agreement (Betriebsvereinbarung).
two places. one engine.
The same engine and the same record, hosted in Germany or as a scoped installation inside your perimeter.
hosted in germany
- locationGermany. For each setup, the documentation lists which components process the data and where.
- operationskint hosts and operates the platform: engine, decision agent and record.
- updateskint keeps the engine and the models up to date. Your team keeps working on the same decision.
inside your network
- perimeterFor control rooms and operations that must not leave your network, we scope an installation inside it.
- isolationThe data is not shared with other customers, and kint trains no models for other organisations on it.
- exitData and records can be exported as JSON and CSV. Model export is agreed per engagement.
the questions an auditor asks. answered by the record.
kint writes the evidence while it works. Drafts of the technical documentation and a risk register stay current from the running system, for your compliance team to review.
| Question | Where the answer lives | Reference |
|---|---|---|
| Who released this plan? | Named release with time stamp, per decision. | Art. 14 |
| Which data was it based on? | Versioned upload, frozen at the time of the run, in the audit trail. | Art. 12 |
| Why this plan and not another? | Binding limit, sensitivity, and the solver's bound and gap, stored with the run. | Art. 13 |
| Can you show it again? | Each run pins the data version, the model version and the solver settings, so the plan can be re-checked against the record. | Art. 12 |
| Who changed the model? | Model versions with author and review. | Art. 17 |
| Where are the risks documented? | Drafts of the risk register and technical documentation, for your compliance team to review. | Art. 9 · Annex IV |
Do we need a tender for the pilot?
What happens to our data if we stop?
How does kint work with our planning and control systems?
start with one decision your team makes every week.
Name it. We prepare a pilot scope procurement can work with, and a first model planners can read.
- Pilot
- One decision, your data, compared with today's plans
- Hosting
- hosted in Germany, or an installation in your network
- Contact
- hello@kint.pro