talk to us
For software vendors

your product.
our engine inside.

Give customers better plans and the numbers behind them, under your brand. You build planning software for terminals, utilities, plants or ERP users. kint runs inside it as a white-label decision engine, called through an API. Each plan comes back with its bound and gap.

talk about a partnershipsee the api
who owns what

your brand on the screen. kint's engine underneath.

  1. yoursinterface and usersScreens, name and customer relationship stay yours.
  2. yoursthe workflowVersioned and released with the product.
  3. kintthe engineModel, solvers, bound and gap, the record. Called through the API.
How it fits

one call between your screen and the plan.

Your product

the planner asks

A dispatcher in your software asks for tomorrow's plan, or a what-if scenario. The interface and the workflow stay as they are.request · your data · your rules
kint engine

model and solve

The versioned model for this customer runs on the matching solver. Each run pins the data version, the model version and the solver settings, so the plan can be re-checked against the record.model v12 · solver · bound and gap
Your product

the plan returns

Plan, binding limit and sensitivity come back as typed JSON. You render them as you like. The record stays retrievable.plan · binding limit · record id

Customers see your brand. Models per customer are built with kint's decision agent, reviewed by your domain experts and versioned in the platform. The workflow ships as a versioned product under your brand. the platform

Why embed

your team builds the product. kint runs the math.

Building optimization in-house means hiring operations research specialists, licensing solvers and maintaining a model per customer. Embedding kint covers that layer, so developers stay on the product.

ship it sooner

A first model on your data within the pilot.

answers you can defend

Plans from exact models name the binding limit and what one more unit of it is worth. Bound and gap are stored with the run, so customers can defend the plan.

one api, maintained for you

You pin a model version and upgrade when you choose. You call the same API.

Stays yours

the customer and the product

  • brand
    Called through the API under your brand; a white-label interface on request. The release cycle is yours.
  • relationship
    You own the contract and the contact with your customers.
  • domain
    Your experts define what a good plan means in the market you serve.
kint runs

the math and the evidence

  • engine
    Whitebox, blackbox and simulation behind one API. Open-source LP, MIP and CP solvers included; commercial solvers supported, licences arranged per engagement.
  • models
    Built with the agent, versioned, replayable per customer.
  • record
    Data version, model version and release for every result, plus EU AI Act documentation drafts for review.
Partnership

from a first test to your release.

01

first test

One decision from the product, run on real or synthetic customer data. You see the results before you commit.

02

integration

Your developers connect the API. kint's forward deployed engineers (FDEs), engineers who work directly with partner teams, enable your developers from authentication to error handling.

03

co-development

Your domain knowledge and kint's engine form a model per customer segment.

04

launch

Optimization ships as part of your product. With a revenue share, cost grows with customer usage.

Partner questions

what vendors ask first.

Pricing, hosting, support and explainability. More in the faq.

How is an OEM partnership priced?
OEM partnerships run on a revenue share, agreed per partnership, so cost grows with customer usage. There is no large upfront fee. See pricing for how engagements are structured.
Can we host the engine ourselves?
Yes. kint is hosted in Germany and operates the platform itself. For operations that must not leave a network, yours or a customer's, we scope an installation inside it.
Who supports our customers?
Delivery to your customers stays with you. kint's FDEs enable your engineering team, with a direct line for its questions.
What if our customers ask how a plan was made?
Plans from exact models name the binding limit and what one more unit of it is worth, with the gap and a record id. You decide how much of that the interface shows.

which decision do your customers ask you for?

Bring one. We run it through kint and show you what it would look like inside the product.

talk about a partnership
Model
Under your brand, via API, on a revenue share
Hosting
Hosted in Germany, or a scoped installation in your infrastructure
Developers
the api in detail
Contact
hello@kint.pro