Where Kepler earns its keep

Use generative models for writing. Use Kepler 1.2 when the system only needs a decision.

System OneTyped outputsLocal first
01

Support

Support ticket routing

Classify queue, urgency, and churn risk from a single ticket payload, before an LLM writes a reply.

02

Inbox

Email & inbox triage

Spam, phishing, refund intent, and department ownership without streaming tokens.

03

Agents

Agent tool-call gates

Ask structured safety questions before a coding agent runs shell, writes files, or hits the network.

04

Retrieval

RAG relevance filters

Keep or drop passages with calibrated confidence instead of hoping a chat model “feels” relevant.

05

Ops

Invoice & ops alerts

Score severity and route finance vs engineering when documents mix numbers and prose.

06

Security

On-prem / air-gapped stacks

When data cannot leave the building, local System One decisions still ship.

Plug decisions into code, then keep the writer model for writing.

Docs cover install, primitives, and how to gate agent tools with Kepler before anything irreversible runs.