Tenant-isolatedAudit-logged every callNo persistent storagePHI-aware recognizersPer-tenant LLM routing · BYOK
Live in production
Three building blocks. Already in production.
Summariser
Available
One-line pinpoint + structured intent for tickets, approvals and knowledge articles. Drop in any ticket body, support thread or approval note — get back the one-line summary your agent needs, plus action_needed, due_date, urgency_score and sensitivity as structured fields.
Pinpoint summary + structured intent fields in a single call
POST /api/v1/summarise{
"summary": "VPN drops every ~10 min since the 4.2 client update.",
"intent": {
"action_needed": true,
"urgency_score": 0.82,
"due_date": "2026-06-05",
"sensitivity": "internal"
},
"sentiment": { "label": "frustrated", "score": 0.74 }
}
Policy Engine
Available
Policy as code, authored in plain English. Each policy is English text plus a declared input schema, usable in five modes — validate, generate, decide, score, classify. Compose into chains or graphs (DAGs) with conditional branching. One call returns per-step results plus a weighted aggregate score, bucketed pass / review / block.
Validate mode: pure DSL, deterministic verdicts in < 50 ms (no LLM hop)
Plain-English authoring — paste, preview, publish. No DSL, no code review, no compiler step in your CI
Chain or DAG of N policies in a single API call — weighted aggregate back, no glue code
Schema-driven JSON, HTML fields, or full semantic HTML from text, image, or PDF. Every value comes with a 0–1 confidence score and an anchor pointing at the exact source phrase the model read — so your workflow can auto-approve the easy cases and escalate the uncertain ones without re-parsing the LLM's prose.
Three output modes — JSON for automation, HTML fields for ticket comments, full document HTML for re-flowing scans
No persistent storage — file bytes live in memory only, cleared before the response returns
Anchors mandatory — hallucinations drop to 0.2 confidence; auditors can cite the exact source phrase
PII visibility — Presidio on every text input, pii_detected events with per-category counts in your audit feed
POST /api/v1/extract{
"fields": {
"invoice_total": {
"value": "1,240.00",
"confidence": 0.97,
"anchor": "Total Due $1,240.00"
}
}
}
Coming next
Two surfaces building on what already ships.
The next things we ship slot into the same engine the three products above already use — same per-tenant LLM routing, same audit feed, same residency + isolation guarantees. Built once, consumed many times.
Upcoming
Knowledge Hub
The currency layer for enterprise AI. Retrieval tells you what exists; Knowledge Hub tells you what's true right now — freshness signal + verified-at timestamp on every chunk — and verifies against the source before an agent acts on it. When two sources disagree, you get the authoritative answer and the reason, not both.
Currency-scored retrieval — every chunk carries freshness + confidence + verified-at, so agents can decide whether to trust it
Verify-before-act — a dedicated path confirms against the source system before an agentic action runs
Depth over breadth — ServiceNow ITSM semantics first (SLA, CIs, resolution validity), not 100 generic connectors
Design locked, engine build in progress.
Private beta · Q4 2026
Mobile Interface
Native iOS and Android app for end-users. Raise tickets, track approvals, query the assistant — all on the same engine your team integrates over HTTPS. A thumb-friendly surface that respects every tenant-isolation, audit, and policy guarantee the API enforces.
Same engine, mobile shell — no separate backend, no parallel audit trail to reconcile
SSO + biometric unlock — WorkOS AuthKit + device-native Face ID / fingerprint
Offline drafts — ticket bodies + approvals are draft-saved locally and synced when the device reconnects