CHANGELOG · SHIPPED THIS CYCLE

Every release gets you closer to owning what you rent.

Point your live OpenAI and Anthropic calls at Kolm, and ship a signed model you run on your own hardware. Here's what we shipped to make that path shorter, cheaper, and easier to prove - with the limits shown, in plain sight.

SHIPPED THIS CYCLE

8buyer journeys sharpened
13tests guarding what you read
4claims we won't make until we can prove them
0broken links shipped

01 - Shipped This Cycle

A shorter path from your live calls to a model you own.

Each release leads with what you get: lower cost, a model you keep, a deploy target that fits, proof anyone can check.

Capture

Point your calls at Kolm

Your live OpenAI and Anthropic traffic is recorded as it happens. No SDK rewrite.

12400 calls captured
Compile

Turn behavior into a model

Captured behavior compiles into one portable file you keep.

1 .kolm file out
Deploy

Run it on your hardware

Deploy to a target that fits, from a laptop to a private fleet.

yours to run anywhere
Verify

Prove what it is

A signed receipt anyone on your team can check, offline.

Ed25519 signed
RELEASE LEDGER / SHIPPED THIS CYCLElive
  1. 2026-06-13 The whole site now says what you getproduct

    Trust, Security, Enterprise, Contact, Platform, Capabilities, Research, and Changelog now lead with one promise: turn the AI you rent into a signed model you own and run on your own hardware.

  2. 2026-06-13 One place to capture, compile, deploy, and exportcontrol

    The API Control Center is in your hands. Capture from the tools you already use, set the rules, run the evals, compile the model, deploy it, and export the file. It is yours to move. Open control center.

  3. 2026-06-13 Every page loads fast and on its ownrouting

    Each product page now serves its own HTML directly, so what you click is what you get. Quicker loads, no detours.

  4. 2026-06-13 We only say what we can proveclaims

    If a claim is not backed by evidence you can check today, you will not read it here. What is true ships; what is not waits. No surprises in procurement. See the trust center.

  5. 2026-06-13 What buyers need, built into the productresearch

    What AI and platform teams told us they need, clear controls, a model they own, evidence they can export, now shapes the product, not just the pitch. Read the research.

LATEST 2026-06-13 verified

02 - What Guards What You Read

Every line on this site has to pass before it ships.

We run our own copy through the same discipline we built the product on. If a page loads, it earned it - routing, fresh copy, working links, claims tied to proof, and real screenshots all checked first.

Site tests

You land on the page you clicked

Direct route fetches confirm titles and current copy for trust, security, enterprise, contact, platform, capabilities, research, and changelog - no wrong turns.

Rewrite tests

No page can quietly serve the wrong thing

Rewrite checks keep every product page on its own content, so a stale alias can't take its place.

Stale-copy tests

Old messaging can't sneak back in

Automated searches block outdated copy and broken characters from returning to a rebuilt page after we've moved on.

Reference lint

Every link and asset resolves

A reference audit checks internal links, images, manifests, docs paths, and route targets across the whole site - so nothing you click goes nowhere.

Claim scope

The copy can't outrun the proof

Claim checks keep certification, benchmark, partner, and adoption statements tied to evidence you can verify - or off the page entirely.

UI screenshots

Readable on the device you're on

Full-page screenshots check spacing, stacking, and layout across desktop and mobile, so the page reads clean wherever you open it.

03 - What We Won't Claim Yet

The claims we're holding back - and why.

You deserve to know what we haven't earned the right to say. These stay off the page until there's evidence you can check for yourself.

Awaiting partner proof

We won't name partners or third-party validation until there's named, checkable evidence behind it. No borrowed credibility.

partner
Awaiting certification

We won't make certification claims until there's live, reviewable evidence you can pull straight from the trust page.

cert
Awaiting a shipped package

We won't advertise a package, SDK, or CLI until you can install a real version and run a real verification command against it.

package
Awaiting public benchmarks

We won't post performance or "better than" claims without public data, method, sample, and limitations you can rerun yourself.

benchmark

04 - What's In It For Your Team

Whoever signs off, the answer they need is on the page.

From the engineer wiring it up to the leader approving the spend, every role now gets a straight answer to the one question they ask.

Product owner

See exactly what you'll own

Your captured behavior becomes one portable file - model, recipe, evals, and receipt - that you keep and can move anywhere.

Enterprise admin

Run it all from one place

Keys, providers, connectors, quotas, retention, exports, usage, and cost - in your hands, where you can see what's spent and what's saved.

Security reviewer

Know where your data goes

Redaction, retention, provider rules, access scope, and tenant isolation - spelled out, with the open questions named in plain sight so you can review them.

Developer

Wire it up without a rewrite

Point your existing calls at Kolm and keep your SDK as it is. API docs, OpenAPI JSON, examples, and error contracts are all there.

Procurement

Buy on evidence, not adjectives

An evidence center, machine-readable readiness, and clear policy boundaries - with no claim we can't back up. Verify before you sign.

05 - Shipping Next

What's coming to make ownership even easier.

Here's where we're headed next - more control in your hands, faster setup, and proof you can pull on demand.

Control center

See and steer every control

Source scopes, connector health, provider rules, retention, eval gates, exports, usage, and cost - all live in your account, so you run the whole thing yourself.

Docs

Copy-paste your way to a shipped model

Worked examples for the full path: capture a trace, classify a schema, run an eval, compile the artifact, pull its receipt, export your evidence, and verify it where it runs.

Routing

Keep every page current

We're sweeping old copy and aliases out of docs, pricing, signup, dashboard, compare, integrations, and runtimes so what you read is always what's true.

Verification

Catch layout breaks before you do

More pages join the automated screenshot checks, so spacing and layout regressions get caught on desktop and mobile before they ever reach you.

Ready to own what you're renting?

Point your calls at Kolm, capture the behavior you already use, and ship a signed model you run on your own hardware - with proof anyone can check.