For operations teams

your decisions.
we run the platform.

For operations and planning teams that have no planning software to build kint into and no developers free to call its API. kint hosts and runs the full platform for you: the engine, the decision agent and the record. Your team brings the decision and the data, and releases every plan.

who does what

your team decides. kint runs the software.

  1. your teamthe decision questionWhich plan you need, by when, under which rules.
  2. your teamthe releaseA person on your team approves every plan before it is used.
  3. kintthe platformEngine, decision agent and record, hosted and updated by kint.
How it runs

your data in. a plan back for release.

Your team

the data arrives

The team uploads a file, or a system sends an export on a schedule the team sets. You choose which data leaves your systems.file upload · scheduled export
kint platform

kint runs the model

The model for your decision runs on the platform kint hosts for you. kint keeps the engine and the models up to date and writes the record of every run.engine · decision agent · record
Your team

your team releases

The plan comes back with the limit that binds it and what changes when a rule moves. A person on your team reviews it and releases it.plan · binding limit · release

Models for the decision are built with kint's decision agent and reviewed by your experts before they run. the platform

Your team does

the decision and the release

  • question
    Which decision, which goal, which rules count.
  • data
    A file upload or a scheduled export from your systems.
  • release
    Your team reviews each plan and approves it. No plan is used without a person's release.
kint runs

the platform and the record

  • platform
    Engine, decision agent and models, hosted by kint.
  • updates
    kint updates the engine and the models. Your team keeps working on the same decision.
  • record
    Data version, model version and release for every plan.

kint hosts and operates the platform for you, in Germany. Where it runs

Start

one decision first. then the next.

01

pilot on one decision

Your team picks one decision and hands over its data. kint builds the model with your experts and shows you the plans before you commit.

02

operate

kint runs the decision on its platform. Your team receives each plan and releases it.

03

extend

Add the next decision on the same platform, with the same record.

Questions

what operations teams ask first.

Data handover, the other paths, pricing and who decides. More in the faq.

How does our data get to kint?
The team uploads a file, or a system sends an export on a schedule the team sets. You decide which data leaves your systems and how often.
How does managed differ from oem and api?
With oem, kint runs inside the product of a planning software vendor. With the API, developers call kint from the systems they build. With managed, kint runs the platform and your team works with the plans directly.
How is managed priced?
Pricing is agreed per engagement, based on the decisions kint runs for you. See pricing for how engagements are structured.
Does our team keep the decision?
Yes. kint proposes the plan and shows the limit that binds it, with the solver's bound and gap: how far from best the plan can be. A person on your team approves or changes it, and the record notes who released what.

which decision should kint run for you?

Bring one. We show you how it would run, with your team releasing every plan.

Model
kint hosts and runs the platform, your team releases
Security
security details
Other paths
oem or api
Contact
hello@kint.pro