Signal · Sign · Seal.
Receive, interpret, act — the architecture of the platform, expressed in the etymology of its name. Three loops, each doing one job, all writing back to the system of record you already trust.
Every signal, captured where the work happens.
An incident channel opens; a ticket is raised. Signum binds the two by naming convention — no inbound webhook into your ITSM — and captures the conversation losslessly, writing it back to the ticket as versioned transcript revisions while the incident is still live.
No webhook into your ITSM. Channels bind by convention; the ticket stays the record.
Every action carries its provenance.
From one incident, generate a customer-facing summary, an internal RCA, or a regulator-ready analysis — each with its own redaction policy. The model runs only when you ask, and every result is cached by the incident's content hash, so a re-read costs nothing and a regeneration happens only when the underlying logs actually change.
The LLM runs only when you ask. Grounded in citations back to the source timeline.
What your auditor reads when something runs.
Configuration, requirements, report types and policy are drafted, reviewed, and propagated only on administrator confirmation. Every change lands in a hash-chained, append-only audit trail — verifiable, exportable — and a last-known-stable snapshot you can restore in a single step.
Append-only, tamper-evident audit. A stable state you can roll back to.
Make your ITIL/ITSM process regulator-ready.
The same captured record drives five on-demand reports that judge an incident — or your whole quarter — against regulation, your own process and policy, and good practice, and propose the fix.
- ITSM process analysis
- Enacted vs designed process — ITIL lifecycle, SLA/OLA, classification, escalation, approvals and RACI gaps.
- Regulatory gap analysis
- Findings vs FCA · DORA · MiCA · MAS · ADGM, by obligation and priority, with notification triggers and a remediation backlog.
- Policy conformance & document gap
- Conformance to your documented process, and the gaps in the documents themselves.
- To-be process & implementation guide
- Human-requested redesign mapped to your tool, with implementation steps — a draft to review and apply.
- Improvement / automation blueprint
- Automations in your tool's own primitives, mapped to the gaps — proposals, never auto-applied.
Single incident or portfolio. Traceable, cited, redacted, human-signed-off. Pricing & tiers →
A pure core, behind ports.
The business logic never imports a vendor SDK. Collaboration, ITSM and model are adapters chosen at deployment — which is what lets you swap any one of them without a rewrite.
- Vendor-agnostic
- Hexagonal core with ports for collaboration, ITSM, model and identity; an import-linter contract keeps the core free of SDK and transport dependencies.
- System of record
- Transcripts and signals live on your ITSM ticket as versioned attachments — there is no parallel datastore to secure, reconcile or explain.
- On-demand cost
- Generation is metered and budgeted per tenant; the content-hash cache means you pay for a report once per state, not once per read.
- Read-time redaction
- Raw, redacted and pseudonymous modes are applied per consumer at read time — names for investigators, tokens for analytics and regulators.
See it against your own stack.
A 30-minute walkthrough — capture, provenance and the audit chain, no slideware.
Request a demo