talk to us
Pricing

priced per engagement.
starting with one decision.

In this first phase, kint works closely with a limited number of customers. Every engagement follows one of three structures. Start by telling us about the decision you want to get right.

describe a decisionthe three structures
You describe
one recurring decision
We scope
data, rules and hosting
You commit
to the platform only after results
Engagements

three ways to work with kint.

01

pilot

For teams that want to see kint on one of their own decisions before committing. kint's forward deployed engineers (FDEs), who work directly with customers, build the model with your team.

Scope
One recurring decision, your data, a fixed period
You get
A reviewed model, plans next to today's, binding limits, the record
Priced as
A price agreed upfront for the fixed scope
Next
Your team decides whether to go to production
pilot for enterprises
02

platform

For operators running decisions in production on kint. FDEs build the first workflows and join again for each new decision.

Scope
Decisions in production, added one at a time
You get
The agent, the engine, scenarios, the record and EU AI Act documentation drafts
Priced as
A subscription, scaled by decisions and hosting
Hosting
Hosted in Germany, or a scoped installation in your network
platform for planning teams
03

oem licensing

For software vendors who put kint inside their product. FDEs enable your engineering team, and delivery to customers stays with you.

Scope
The engine via API, under your brand
You get
Co-developed models for your segments, support from kint's FDEs
Priced as
A volume-based licence or a revenue share. No large upfront fee.
Start
A first test on one decision from your product
oem partnership in detail
How a price is set

what moves the number.

We price what the engagement needs, not seats you will not use. These are the factors we ask about.

  • decisionsHow many decisions run on kint, and how often they are solved.
  • sizeThe size of the models: assets, shifts, sites, time horizon.
  • hostingHosted in Germany, or a scoped installation inside your network.
  • serviceManaged operation by kint, on request.
  • modelling supportHow much of the modelling kint's FDEs do with your team.
Always included

the essentials are included.

The gap, the record and the documentation are part of the product, not priced as extras.

bound and gap with every exact plan

Binding limit and sensitivity, stored with the run.

the record

Versioned data and models, releases, and runs you can re-check against the record.

EU AI Act documentation drafts

Drafts of the technical documentation and a risk register, kept current from the running system, for your compliance team to review.

onboarding

kint's FDEs work with your team on the first decision.

the data stays yours

kint trains no models for other organisations on it. Data and records can be exported as JSON and CSV.

Questions

about money.

Short answers to what purchasing asks first.

Why is there no price list?
Engagements differ too much. A grid operator hosting in its own network and a startup calling the API need different terms.
Does the pilot commit us to the platform?
No. The pilot ends with results and your decision. Going on is a separate order.
Are solver licences extra?
Open-source solvers are included. Commercial solvers are supported; their licences are arranged per engagement, and you can bring and use your own commercial solver licence.
How is OEM priced?
As a volume-based licence or a revenue share, agreed per partner. It starts with a first test on one decision from your product.

one decision. one offer.

Describe the decision you want to improve. You get a scope and a price for a pilot.

describe a decision
Pilot
Fixed scope, price agreed upfront
Platform
Subscription per decisions and hosting
OEM
Volume-based licence or revenue share
Contact
hello@kint.pro