The pilot
One workflow, your criteria, your machines.
A kibbu pilot runs one real workflow on your own machines for 6 to 8 weeks, against acceptance criteria you set before it starts. It begins with a scoping call and ends with a written result: whether the workflow met your criteria, what it needed, and what to change before going further.
How it runs
Five steps.
Minutes, not weeks, for a first machine. kibbu has not published a measured setup time, because model download time depends on the model and your network.
- 01Scoping callAn hour on the workflow, the data it touches, the machines you could use and the deployment that fits.
- 02PlanOne workflow, a baseline from how it runs today, acceptance criteria you set, and the machines that take part.
- 03Set upEnroll the machines, set the key policy, choose the models and point the workflow at kibbu.
- 04Run and measureRun the workflow on your fleet and record quality, completion time, failures and retries against your criteria.
- 05ReviewA written result against your criteria, with what to change before going further, or a clear no.
Before it starts
What you bring.
Most of it is a decision rather than work.
- One workflow with an owner, and the data it touches.
- A baseline: how the workflow runs today, and what good output looks like.
- Acceptance criteria, written down before the pilot starts.
- A set of machines you can enroll through your MDM, and the people who use them know it is coming.
- An admin who can create API keys and set the key policy.
- For kibbu On-Prem, the infrastructure on the On-Prem page.
The workloads page suggests a first pilot for each kind of work.
How it is judged
Against your criteria, not ours.
These are the questions a pilot answers. The numbers come from your run.
| Question | How the pilot answers it |
|---|---|
| Does the workflow complete inside your environment? | Run it end to end on your machines with the key policy you would use in production. |
| What network access does it need? | Record every destination the deployment reaches. With kibbu On-Prem, run the egress check. |
| What happens when machines become unavailable? | Watch retries, failovers and queue waits as people come back to their machines. |
| What can administrators see and control? | Review the request log, the audit log and the key policy in the console. |
| Does it meet your acceptance criteria? | Compare output quality, completion time and failures with your baseline. |
Evaluating any platform
Questions to ask a private inference platform.
Useful whether or not you choose kibbu.
- Where does a request go, hop by hop, and who operates each hop?
- What does the vendor store, for how long, and does it include prompt or response text?
- Can it run with no connection to the vendor at all, and how do updates and models arrive then?
- When can a request reach a cloud provider? kibbu's answer: kibbu does not run a cloud of its own. A request can only reach a cloud provider if your organization has added that provider's API key, the model allows cloud, and the key's policy does not deny it. With cloud denied, a request that no machine can serve returns an error (HTTP 503 with a Retry-After header) rather than leaving your fleet.
- Which API endpoints and features are supported, and which are not?
- What happens to a request when the machine serving it goes away?
- Which certifications are held today, and which are only in progress?
At the end
What you get.
Enough to decide, whatever the answer.
- A written result against your acceptance criteria, with the measurements behind it.
- The setup you ran: machines, models, key policy and deployment.
- What would need to change to go further, or a clear no.
Questions
Frequently asked.
How long does a kibbu pilot take?
A pilot is scoped at 6 to 8 weeks, for one workflow. Setting up the first machines takes minutes, not weeks; most of the pilot is running the workflow and measuring it against your criteria.
What do we need before a pilot starts?
One workflow and an owner for it, a baseline from how it runs today, acceptance criteria, a group of machines you can enroll through your MDM, and an admin who can create API keys and set policies.
Does any data leave our environment during a pilot?
With kibbu On-Prem, nothing reaches kibbu. Hosted, requests pass through kibbu's control plane on the way to your machines, and kibbu keeps metadata, not prompt or response text, except where you use a feature that stores it. Cloud providers are only used if you add your own key and allow them.
What does a pilot cost?
Pricing is agreed per pilot.
Does kibbu hold SOC 2 or ISO 27001 certification?
SOC 2 Type II and ISO 27001 are in progress, not yet certified. kibbu holds no other certification. Ask hello@kibbu.io for the current security questionnaire.
Keep reading
Start with one workflow.
Tell us about the work you want to keep private, and we will scope a pilot on your own machines.