Integrations · drop-in, no SDK rewrite

Works with the stack you already run.

Point your existing OpenAI- and Anthropic-compatible calls at Kolm - keep your SDK exactly as it is. Capture from the gateways, traces, queues, warehouses, files, tickets, and approval flows you already use, then ship a signed model you own to the runtime you already have. No rewrite to get here. No lock-in once you do.

Open API Control Center See the API contract

17 channel families 12 ingress modes 10 export modes 8 policy layers

REG-04 claims-redactor.kolm SOURCE → PROOF · v3.3

Source: gateway / trace / queue
Schema: adapter manifest
Policy: fence · redact · route
Export: packet + receipt

Connect what you already use

17data-channel families

12ingress modes

10export modes

8policy layers

From your traffic to a shipped model

One path: capture, compile, ship.

The same steps run from the API Control Center and from GET /v1/account/api-control-center: connect a source, set the rules, fix what fails, compile the model, and export the proof. No new tools to adopt - Kolm meets your stack where it is.

One path end to end, with the limits shown at every step
Capture from systems you already run; ship a signed model you own
Take the proof with you - it works outside the Kolm UI

CAPTURE → SHIP · limits shown

source gateway, trace, webhook, queue 92%

schema adapter manifest or opaque marker 74%

policy fence, redaction, retention, routing 86%

improve taxonomy, review, eval, replay 68%

compile manifest, evaluators, target matrix 78%

export packet, receipt, OTLP/JSONL, catalog 88%

Switchboard · source → model → proof

From a live API call to a model you can verify.

Wire in workflow engines, OpenAPI assets, MCP tools, and approvals. Move and stream CDC, queues, topics, warehouses, and object stores. Kolm keeps unknown payloads sealed until an adapter proves what they mean - then the signed result flows out through every export you already use.

Wire in · workflow engines, OpenAPI assets, MCP tools, approvals
Move & stream · CDC, queues, topics, warehouses, object stores
Unknown payloads stay sealed until an adapter proves what they mean

SWITCHBOARD · limits shown

# wire in · workflow engines, OpenAPI assets, MCP tools, approvals
→ POST /v1/account/api-control-center/events
# move & stream · CDC, queues, topics, warehouses, object stores
→ /adapter-manifests/validate    # prove what the payload means
✓ claims-redactor.kolm          # signed model + eval report + recipe
# rule · payloads stay sealed until an adapter proves their meaning
→ export    # signed packet, verifier receipt, OTLP/JSONL, warehouse + ticket sinks

Sealed until adapter-provensigned model + eval report + recipe

Sources and sinks

Kolm slots in between the tools you already trust.

Nothing to rip out. Pull signals from the systems you already run, set the rules on what Kolm keeps, and ship signed models and proof anyone can verify - inside your stack or out.

Cluster	What connects	Role
gateway/provider	Provider gateways, routers, model APIs, and API management layers. Provider access, routing, keys, fallback, budgets, cache and usage signals.	source + route target
trace/eval	Trace stores, eval dashboards, annotation queues, and OpenTelemetry spans. Traces, prompt versions, eval sets, annotations, drift signals and release evidence.	import + evidence sink
data movement	Connectors, queues, topics, warehouses, lakehouses, and object-store drops. Connectors, topics, CDC, warehouse extracts, transforms, dead-letter context and export manifests.	batch + stream source
workflow/api	Workflow engines, API platforms, typed RPC systems, and approval callbacks. Triggers, actions, universal connectors, API management, agent-ready assets and approval callbacks.	automation handoff
catalog/lineage	Catalog, ownership, lineage, job metadata, and data-quality systems. Asset context, dataset ownership, lineage metadata, job/run facets and catalog references for evidence exports.	lineage sink
security/grc	SIEM, GRC, incident, API inventory, security review, and assurance systems. Control evidence, API discovery signals, log drains, incidents, guardrail verdicts and assurance packets.	verdict + proof sink
runtime/release	vLLM, SGLang, TensorRT-LLM, llama.cpp, Ollama, Core ML, LiteRT, ExecuTorch, ONNX, RunPod, Hugging Face. Target instructions, release gates, package manifests and runtime receipts.	deployment target

INGRESS → KOLM → EGRESSlive

ONE PATH capture → seal & compile → signed proof verify offline

One path: capture from the tools you already run, seal and compile in the center, then ship a signed model and proof anyone can verify.

Source or sink connection
Signed proof, the one verifiable export

Data-channel families

Capture from anything; ship proof to everything.

Each family spells out direction, payload style, product routes, and controls. Kolm keeps a payload sealed until a schema or adapter proves what it means - so nothing moves before you know what it is.

Reg · request

Request APIs

REST JSON, streaming/SSE, webhooks, OpenTelemetry GenAI spans, MCP tool calls, A2A handoffs, GraphQL/RPC and custom adapters.

Reg · batch

Batch and streams

JSONL, CSV, Parquet, files/blobs, warehouse and object-store drops, queues/topics, database CDC and lakehouse snapshots.

Reg · security

Security and operations

SIEM/log drains, collaboration and ticketing callbacks, approval events, guardrail verdicts and incident review markers.

Reg · release

Release and evidence

Signed artifacts, registry/package releases, receipts, manifests, eval reports, proof packets, runtime instructions and verifier links.

One chain, end to end

Keep your systems. Add a model you own.

You don't need another dashboard. You need one path from a live source event to a signed model on your hardware - with the rules you set and proof you can hand to anyone. That's what Kolm adds, without taking anything away.

Reg · handoff

Workflow handoff

Triggers, actions, approvals, and automation callbacks plug in as source or sink events, each with a delivery receipt.

Reg · data

Connectors and streams

Connectors, streams, schema drift, warehouse extracts, and dead-letter context tie straight to your model's rules and lineage.

Reg · lineage

Lineage you can trace

Dataset, job, run, owner, and catalog metadata stay attached to the model, the receipt, and the signed proof packet.

Reg · assurance

Assurance packet

API discovery, security review, incidents, controls, questionnaires, and remediation evidence export as proof anyone can verify.

You set the rules

Capture wide. Keep tight.

By default Kolm keeps metadata plus redacted bodies, sends nothing anywhere until you name the destination, isolates each tenant's cache keys, and seals unknown payloads until you approve an adapter. Broad reach, on your terms.

Secrets stripped before anything is written to disk
Nothing leaves until you declare where it goes
Unknown payloads stay sealed until you approve an adapter

Get an API key See the security scope

Reg · identity

Identity and vault

Tenant keys, scoped keys, RBAC, SSO/SAML/SCIM hooks, central provider keys, BYOK/BYOC paths and model entitlements.

Reg · capture

Capture and routing

Sample rate, body retention, namespace windows, redaction before storage, destination allowlists and PII/secret blocking.

Reg · eval

Eval and compile

Production evals, drift alerts, regression gates, human review queues, corpus selection, evidence DAGs and artifact receipts.

Reg · export

Export you can verify

OpenAPI, JSONL/CSV, OTLP metrics, signed receipts, assurance cases - exports that stay useful long after they leave the UI.

Start small · prove it on real traffic

Connect one namespace. Own the model it makes.

Point real traffic at Kolm, set the rules on what it keeps, and walk away with a signed model plus proof you can verify - before you connect a second thing. No rewrite to start. No lock-in to leave.

Wire up your first connector today and ship a signed model this week - start on the API and add the rest as you grow.

Get an API key See the platform Runtime targets See pricing