Pricing
The numbers, printed.
Priced per module, because Causa and Custos are bought by different people for different reasons, and a ladder of tiers can only ever say “more” when the honest answer is “different”. Integration is quoted separately and is not a recurring charge.
Signum Causa
“What happened, and why?”
One service-delivery team, every incident on the record.
- Up to 200 incidents a month
- One collaboration and one ITSM connector
- Sealed transcripts and evidence drill-down
- Core reports: summary, customer note, RCA
- Content-hash caching and a hash-chained audit trail
Multi-team operations across more than one platform.
- Unlimited incidents
- All connectors, multi-tenant
- SSO, SAML and SCIM
- Governance workflow and cost budgets
Signum Custos
“Can we show the control operated?”
Evidence for one regulated service, incident by incident.
- Your policy and process documents as a governed corpus
- Built-in report types with per-report redaction
- Single-incident evidence packs
- The audit trail as a screen, not a file you request
A compliance function reporting across a portfolio.
- Custom report types — name, instructions, redaction, no code
- Aggregate reporting across a quarter or a service
- Compliance and process intelligence reports
- Policy conformance and regulatory gap analysis
Signum Memoria · still being built
No licence fee, because it is not finished.
Memoria does not meet its own retrieval gate yet, and we publish the numbers that say so. Charging a subscription for that would be selling you something we have already told you is not good enough. So there is no licence fee while it is being built: design partners pay corpus onboarding only, and get the module as it lands.
When retrieval clears the gate it will be priced on the size of the corpus it holds — not on how many incidents you had, which is a number with nothing to do with what Memoria costs to run.
Enterprise
Talk to us.
Self-managed deployment, customer-managed keys, private model serving and bespoke regulatory scope are arranged rather than listed, because the shape of them depends on your estate and your regulator. Both modules are included; the commercial terms follow the scope.
- Self-managed in your cloud, or private SaaS
- Customer-managed encryption keys
- On-premises or private model serving
- Bespoke regulatory scope and portfolio reporting
- Dedicated support, security review and DPA
Integration and go-live
Priced once, not every month.
Standing Signum up against your platforms is finite work: scoping, configuration, connectors, redaction and report types tuned to your policy, then go-live. It is quoted after a consultation, against what you actually run, and it includes one month of support afterwards. The figures below are starting points, not an estimate of your job.
Hosted, one collaboration platform and one ITSM.
- Scoping consultation and deployment design
- Connector configuration and channel-to-ticket binding
- Redaction rules and report types set against your own policy
- Go-live, with one month of support included
Your cloud, several platforms, enterprise sign-on.
- Everything in standard deployment
- Deployment into your own cloud, or private SaaS
- Multiple collaboration and ITSM connectors
- SSO, SAML and SCIM wiring against your identity provider
- Go-live, with one month of support included
Getting your knowledge into a shape that can be asked.
- Source allow-listing and classification review
- Gate vocabulary tuned to your own terms
- Initial index, and review of the first pages through the gate
- Handover, with one month of support included
One-off. After the included month, support is part of the subscription.
Questions
Pricing, answered.
No. Generation is metered and budgeted, and every report is cached by the incident’s content hash — you pay for a report once per state of the record, not once per read. Cache hits are free.
Yes. That is the point of pricing them separately. Causa and Custos each stand alone, and a module you do not hold is absent from your console rather than shown to you locked.
Because it is finite work that ends. Rolling it into the subscription would charge you in the second year for something delivered in the first month. It is quoted after a consultation, against the platforms you actually run, and it includes one month of support after go-live.
One bound channel-to-ticket case. Re-reads, regenerations on unchanged records and historical reports do not add to the count.
Yes. Self-managed deployment is an Enterprise arrangement; operational data partitions by deployment, and customer-managed keys are available.
Yes — Causa Team starts as a trial against a sandbox of your stack. Request a demo to provision it.
Not sure which modules you need?
Tell us your stack, your volume and who is asking the questions. We will say which modules apply to your shape — including when the answer is only one of them.