Building a PoC is easy now. Surviving production isn't. That part is already built.
kOS is the platform every KlusAI use case lands on.
The parts nobody demos
A proof of concept can skip all of this. A system in production cannot. These are built once, into the platform, so no use case has to build them again.
Identity done right
Microsoft and Google sign-in, per-org domain control, 2FA and role-based access, on day one.
True multi-tenancy
Every record belongs to one organization's workspace; access follows assigned roles, and cross-tenant isolation is tested on every change.
Tamper-evident by design
An append-only audit log. Who did what, when, and with which model version.
European privacy posture
Per-org data residency, Private Mode, and GDPR retention rules that run themselves.
Ships daily
Daily releases with automated rollback. The platform you buy keeps moving.
Tested before it ships
7,600+ automated tests behind a release gate that runs end to end.
Ask your platform a question
Klu is the governed AI layer inside kOS. It answers against your own records rather than a general model, every answer carries an audit trail, and the cost of each conversation is on the screen. Private mode keeps inference on EU-resident compute instead of sending it to a cloud provider, or on an Outpost Blade inside your own network.
Context-aware assistant
It answers against your own records, not a general model's memory.
Governed LLM gateway
Requests reach only the model providers your deployment allows.
Drivable over MCP
The same tools your team uses are callable by an agent.
The AI proposes, a person approves
Every change Klu wants to make waits on an approval card, and the page updates the moment you accept it.
Screened before any model sees it
Documents and filenames are checked for personal data before a model reads them, and the check fails closed.
Cost on the screen
Spend per conversation, per user, visible while it happens.
From an ERP export to a working case desk in under two weeks
A German office-technology provider's contract renewals, built on kOS. Nothing here was written for one customer only: the import, the rules and the approvals are platform parts the next use case reuses.
-
1
The export goes in
A declared mapping turns the ERP export into versioned, organization-scoped records. No integration project first.
-
2
Rules do the casework
A rules engine evaluates every contract, and a daily run imports, evaluates, notifies and sends the digest.
-
3
People decide, the assistant helps
A case board and offer letters for the team, and an assistant whose every change waits for a person's approval.
kOS runs on razorBridge
razorBridge is KlusAI's infrastructure: kOS and razorBridge AI Blades run on it, operated by KlusAI in third-party data centres in the EU. razorBridge Managed kOS — Dedicated, a single-tenant kOS environment that is EU-hosted with named exceptions and includes private inference, is for organizations that need their own environment and will be asked to show where their data goes.
Turn on private mode and inference stays on that compute. The screen beside this one is the setting, not a diagram of it.
razorBridge.eu
kOS, inside your network
Some systems never leave the building. razorBridge Outpost is an appliance we place in your network. It dials out to your kOS workspace over an encrypted link, so no inbound port is opened, and it brings in the records a use case needs from the systems that stay on your premises.
Outpost
Connects kOS to on-premises systems such as your ERP, mail server and file shares. Outbound only. We install, update and monitor it.
Outpost Blade
Everything Outpost does, plus private mode on your premises. Inference and embeddings run on the appliance, not at a cloud AI provider.
Available to design partners. Records a use case syncs are stored in kOS; Outpost Blade keeps the AI processing on site. One appliance per internal network.
One engine, deployed as your own
Customers do not get a tenant inside our product. They get their own product: their domain, their language, their legal imprint and emails, and an assistant that carries their name. A new brand is a small configuration package on the same engine, never a fork.
- Their brand, end to end
- Domain, sign-in page, emails, error pages and link previews carry the customer's brand. No vendor chrome.
- An assistant under their name
- Klu takes the customer's name for its assistant and uses only the tools their workspace switches on.
- Use cases switch on per organization
- Each use case is a platform module enabled by entitlement, so one customer's work becomes a capability for the next.
- Scoped per organization, dedicated on demand
- Every record belongs to one organization's workspace, and Managed kOS Dedicated, a single-tenant cell that is EU-hosted with named exceptions, is available when policy requires it.
- The platform beneath stays KlusAI IP
- A signed contract term, not an assumption. One engine, many deployments.
Provable, not asserted
ISO 27001
Certified information security management.
GDPR
Data residency, retention and subject rights built into the platform.
EU AI Act readiness
Audit trails, model provenance and human review, ready for the obligations as they land.
See it running
A walkthrough of the real platform, not a slide deck about it. Bring a use case and we will scope it on the call.