Simple pricing thatscales with your customers

Kini Core is billed per integrated end-customer, a single axis, and the price per customer drops in higher tiers. Kini Shop for partners has a monthly fee plus a margin split on shop revenue. Prices and starting points are on the cards above, and the exact tier (Lite, Basic, Grow or Enterprise) is confirmed in a short call.

A single value metric is a deliberate choice: it means your cost moves with the value you get rather than with API calls or seats, and it stays predictable as usage inside each customer grows.

No. We work in close partnerships rather than charging for onboarding. The minimum term is twelve months, and it comes with a 30-day money-back guarantee: cancel within 30 days, no reason needed, no charge.

Removing the setup fee shifts the risk to us on purpose. It also removes the negotiation that usually delays a first pilot by weeks.

For an ATS Kini already supports, the connection itself is set up in minutes once we have the credentials. What usually takes longer is getting them: some ATS vendors need a step on their side first, such as issuing an API key or a certificate, or allowlisting Kini. Kini then checks the setup with a test application and activates the integration.

If your first customer runs a system Kini has not connected yet, the timeline depends on building that connector, and we say so in the first call rather than afterwards.

A single axis. For Kini Core it is the number of integrated end-customers, not seats or API calls. Tiers are tied to minimum volumes and discounts apply at integration level, so the price per customer drops as you grow.

Billing starts when an integration for a customer is created through the onboarding app.

Yes. Tiers are tied to minimum volumes, so you can start on the Lite tier with a handful of integrated end-customers and move up as adoption grows. Discounts apply at integration level, which means the price per customer drops as you scale.

Higher tiers include more jobs and candidates and add features such as Slack-channel support, white-labeling and advanced ATS integrations.

Instead of a trial we offer a 30-day money-back guarantee: cancel within the first 30 days without giving a reason and without paying. A connectivity layer only proves itself against real customers and real data, which a limited trial account cannot provide.

That is also why the pilot end-customer is part of onboarding rather than an optional extra: the first real connection is the trial.

Yes. Kini operates under GDPR and provides an AVV/DPA template before sign-off, so your legal review can start before the contract closes. Security and data-handling questions are meant to be answerable without a sales call.

Getting the DPA out early is deliberate: in most partner deals legal review runs in parallel with the technical pilot, and a template that arrives late becomes the thing that delays go-live.

Yes, through the Kini Shop. It connects to the end-customer's ATS and lets them book recruiting products on demand, without a partnership contract. Recruiting teams use it to connect job boards and tools directly.

For partners this also works as a low-friction entry: customers who start in the Shop can later be moved into a managed partner setup without rebuilding their connections.

Kini operates integrations across ATS platforms, with a focus on the DACH recruiting stack. It also connects job boards and social recruiting tools. Every live connector is listed on the integrations page with setup time, synced fields and known limits.

If a system you need is missing, tell us. From the Basic tier on, you can request new connectors, and they are prioritised by partner demand.

For end customers, the Shop is free and they only pay per booking. For partners, the Shop comes with a low monthly fee, so both sides have a reason to integrate fast and work closely together.

Your systems keep their data. Kini moves records between the systems you own, the ATS stays the system of record, so cancelling does not strand anything. On request we delete processed data from our infrastructure in line with the AVV/DPA.

Export or handover of mapping documentation is part of offboarding, so a successor setup or an in-house takeover can continue from what already runs.