Installation licence
One Thulpar installation covers the api, gateway, detectors and console on one hardware tier. For high availability, several nodes join the same installation.
Contact us for a quote → Licensing
One licence per installation, metering per tenant.
The licence is a signed document. It verifies on a closed network and is uploaded in the console. One licence covers an installation. Tenants are licensed for a fixed term or metered per transaction. Sector templates are optional. Figures are given on quote. The trial licence for a pilot is free.
Signed document
The licence verifies on a closed network and is uploaded in the console.
One licence covers an installation. Tenants are licensed for a fixed term or metered per transaction. Sector templates are optional; the trial licence for a pilot is free.
Contact us for a quote →Model
Installation, tenant, transaction, sector template, managed instance.
Tenant, fixed term
An organisation or business unit with its own policy pack, ledger chain and approval inbox. Independent of the number of checks.
Contact us for a quote →Tenant, per transaction
Checks completed in enforce mode are counted. Shadow, audit and async follow-up events are not. Metering runs locally and is chained into the ledger.
Contact us for a quote →Sector template
BDDK banking, SEDDK insurance, public sector, defence and EU AI Act high risk. Each is a signed policy template with its evidence profiles and updates.
Contact us for a quote →Managed private instance
A dedicated installation in verified data centres in Türkiye. Operations, monitoring, upgrades and backups are included.
Contact us for a quote →Scope
Included in every licence
- Policy decision point, rail graph, shadow / enforce / audit modes
- The tier’s detector catalogue and signed model bundle
- Hash-chained evidence ledger, daily anchors, evidence packs in 7 profiles
- Approval inbox: four-eyes, SLA, escalation, webhooks
- OpenAI-compatible gateway and MCP proxy
- Console: findings, ledger, detectors, policies, approvals, API keys, health
- Install kit, Helm chart, upgrade and backup tooling
- Red-team suite and benchmark evidence
FAQ
Frequently asked questions
How is the licence verified on a closed network?
The licence is an Ed25519-signed JSON document. The verification key is compiled into the image, so no outbound call is made. The document is uploaded in the console or mounted as a file. A renewal is a new document.
What if the clock is set back?
The installation keeps a clock high-water mark that never moves backwards. If the clock falls behind it, enforce checks are refused. Shadow mode never blocks a licensed tenant. The first detection is written to the ledger.
How is per-transaction metering tamper-evident?
Counters are written to the ledger’s installation chain as daily checkpoints. Deleting rows can only raise the count. The renewal report lists every checkpoint with its hash and verifies offline.
What can an unlicensed tenant do?
It can run shadow and audit checks for a limited period. The default is 30 days. During that period nothing is blocked, nothing is counted and everything is written to the ledger. It ends when the period expires or a licence is uploaded.
Why are there no prices on the site?
Tier, tenant count, transaction volume and the operating model differ between organisations. We quote in writing after a short discovery call. The trial licence for a pilot is free.
See it in your own environment.
A one-hour technical demo: your scenario, your policy pack, on a closed-circuit install. Then the install kit and a trial licence for a pilot.