Credits are your engineering capacity. They are spent only when KESDONE works, on work you approved: scoping is free, a build costs what it engineers, and keeping a product right in production costs a little every day it is live. No seats, no platform tier, no retainer. You see the estimate before anything starts, and the meter while it runs.
The conversation in the studio, the questions, the meanings it proposes for your fields, the contract written in your words. All of it costs nothing, so you can see exactly what would be built before spending a credit.
A build is metered by what it engineers: sources connected, documents or records processed, checks run, infrastructure provisioned. A small retrieval corpus on three sources and a business graph on thirty do not cost the same, so the studio writes the estimate in the contract, you approve, and the build runs. A rebuild after your correction is included until you approve the sample.
Every day a product is live, KESDONE watches it, diagnoses what breaks, and prepares or applies the fix at the autonomy you set. Metered per product and per day, so it stops the day you retire the product.
Set your situation with the sliders. KESDONE costs at most a fifth of a data engineer, delivers a data product fifteen times faster, and fixes an incident in minutes instead of hours. Priced in credits, so you never pay for a product you no longer run.
Illustrative: KESDONE at a fifth of what a data engineer costs you, delivery 15× faster, incident fixes 24× faster. Your exact estimate, in credits, is written in your contract, free, before anything is built.
Because the work is not the same every month. A build is a burst of engineering; operation is a low, steady effort that stops when a product is retired. Credits follow the work, and you never pay for a product that no longer exists.
No. The estimate in your contract is a ceiling. If the build needs more than planned, KESDONE stops and asks before spending. Rebuilds after your corrections, until you approve the sample, are included.
A small daily amount per product in production covers the watching, the diagnosis and the prepared or applied fixes, at the autonomy you set, plus the knowledge kept for the next product. A fix that is a new version passes the same checks as the first build, and is included. How it works in practice is on the Product page, step five.
Credits do not. On KESDONE cloud, infrastructure is billed at provider cost and shown separately; on your cloud, you pay your provider directly. The two modes.
No. KESDONE is deployed globally. Regional data residency and in-VPC inference are options for any customer who needs them, in either mode.