Do I have to rewrite my SDK calls?
No. Point your existing OpenAI- or Anthropic-compatible calls at Kolm and keep your SDK exactly as it is. It captures and routes everything for you - no rewrite to get here.
The compiler for teams on OpenAI and Anthropic · drop-in proxy, no SDK rewrite
Point your API calls. Own the model.
Kolm sits in front of your OpenAI and Anthropic calls - no SDK rewrite. It captures the behavior you already use, compiles it into a signed model in one portable .kolm file, and runs it on your own hardware. Pay to run the behavior you’ve already established - not frontier prices to rent it again, forever.
No SDK rewrite to get here
Secrets stripped before anything is written to disk
Every model signed - verify it yourself
Runs on the hardware you already have
Shipping today
12ways in - capture from the tools you already use
5places to run it - laptop to server
Ed25519signed - verify it yourself
142 MBmedian model - small enough to move
Why own it
You already paid to establish this behavior. Stop renting it back.
Calling a frontier API charges you every time you re-run behavior you have already proven works. Kolm captures that behavior once and compiles it into a model you run yourself, so repeat calls cost what your own hardware costs, not a frontier rate, forever.
- Rent (frontier API): low effort to start, but you pay a per-call rate on every repeat, with no artifact to keep.
- Own (a .kolm): one capture, one signed file at a median 142 MB, then run it on hardware you already have at your own cost.
- See the worked path: follow capture to deploy step by step in how it works, or read the .kolm spec.
BEST QUADRANT high ownership, low recurring cost verified
Capture → Compile → Compose → Deploy
From your live API calls to a model you own.
Point your traffic at Kolm. It captures the behavior you already use, compiles it into a signed .kolm file, and runs it on the hardware that fits - with a receipt you can verify at every step.
Capture
Point your existing calls. No rewrite.
One drop-in endpoint sees every call - replay it, export it to JSONL, OTLP, or a signed receipt. Your provider keys stay in one vault; secrets are stripped before anything is written to disk.
12,408callsCompile
Turn that behavior into one signed file.
Model, recipe, evals, and receipt pack into one portable .kolm - Ed25519-signed and reproducible, so anyone can check exactly what it is and how it behaves.
Compose
Pack it into one portable file.
The model, recipe, evals and receipt compose into a single signed .kolm - small enough to move, open to inspect layer by layer, with no provider lock-in.
Deploy
Run it on the hardware you already have.
Kolm ranks hosted, server, laptop, edge and phone by cost, latency and fit, then serves the same file wherever you choose - with the limits shown up front, and rollback built in.
5places to runRECEIPT signed at every step verified
Capture
Point your existing calls at Kolm. No rewrite.
Keep your SDK exactly as it is. One drop-in endpoint sees every prompt, completion, tool call and routing decision - ready to replay, export, and compile.
- Drop-in proxy · keep your provider keys in one vault
- Secrets stripped before anything is written to disk
- Export to JSONL, OTLP, or a signed receipt
CAPTURE secrets stripped before write verified
Compile
Your API calls, compiled into a model you own.
Model, recipe, evals, and receipt pack into one portable .kolm file - signed with Ed25519, reproducible, and open to inspect layer by layer. Export it, move it, keep it. No provider lock-in.
- Reproducible build · content-addressed receipts
- Evals run before any model ships
- Open the file - read exactly what’s inside
Ed25519 one signature over four layers verified
Deploy
Run it on the laptop you have, the cloud you trust.
Kolm ranks every target - hosted, server, laptop, edge, phone - by cost, latency and fit, then serves the same file wherever you pick. Pay to run the behavior you’ve already established, not frontier prices to rent it again.
- Picks the runtime that fits · with the limits shown
- One file, many targets · hosted or run it yourself
- Rollback, receipts, and exports included
SELECTED phone · smallest runtime that fits in spec
Proof · the receipt
Verify it yourself. No trust required.
Every model ships with a signed receipt: which checks ran, what passed, and the signature that ties the report to the build. Anyone can check it without trusting us - and the same receipt exports clean for procurement and audit.
- Content-addressed · sha-256 over every layer
- Ed25519 signature · report binds to the build
- Nothing ships silently · every promotion is on the record
- Portable · check it yourself at /verify
claims-redactor.kolm
a1f0c4…9e
Pass
Behavior held · checked before ship
6 evaluators · 0 regressions · 2,140 examples
Recipe 18 / 18 reproduced
Pass
Secrets stripped before write
3 spans redacted before write · vault-held keys
Capture export · 12,408 calls
algEd25519verified
sig9c2e7b41a0f5d83e6b1c…
VERDICT signature checked offline valid
Frequently asked
Straight answers before you start.
The questions a platform team asks first - answered the way they’d want to hear them.
Where do my secrets live?
Secrets are stripped before anything is written, so they never reach the captured record. Your provider keys stay in one vault.
What do I actually own?
One portable .kolm file - model, recipe, evals, and receipt. Ed25519-signed and yours to export, move, and keep. No provider lock-in.
Where can I run it?
Wherever it fits. Kolm ranks hosted, server, laptop, edge and phone by cost, latency and fit, then runs the same file on the target you pick - with the limits shown.
Ready to own what you’re renting?
Point one namespace at Kolm and compile your first model this afternoon - no rewrite, no lock-in.