Stop the incident. Then remove the cause.
ZANALYSE is automated root cause analysis for IT operations. Upload your logs, timelines and incident notes, answer a guided set of problem management questions, and get a structured RCA that carries the evidence behind it, a confidence score, and corrective actions you can assign the same day.
General availability 1 October 2026 · Early-bird pricing until 31 December 2026 · Browser-based, nothing to install
Auditors, regulators and customers now expect this.
Structured problem management is no longer optional. ZANALYSE is built on the practice as it is defined which is a governed process with a clear history trail, ready for audit inspection.
Problem Management
Operational excellence, built on process maturity
Achieving operational excellence is built on process maturity and on working in a structured way with problem management, as defined by ITIL v4. Root cause analyses create strong organisational knowledge and identify business risks before they become incidents.
Achieve maturity
Evidence your regulator will accept
ZANALYSE helps you become ISO 27001, ISO 22301 and DORA compliant, with an intuitive problem management application that strengthens your company's security posture and process maturity.
Most teams close incidents. Far fewer close the cause.
Restoring service is urgent, so it gets done. Problem management is important but never urgent, so it slips, and the same incident returns next quarter with a different ticket number. ZANALYSE removes the two things that stop the analysis from happening: the blank page, and the hours.
The same incident, again
Repeat incidents are the clearest signal that the cause was never removed, only the symptom. Recurrence is the metric ZANALYSE is built to move.
Analysis takes a day you don't have
A proper RCA means collecting evidence, running a workshop and writing it up. ZANALYSE produces the first draft in minutes, so your people spend their time judging it rather than producing it.
Findings that survive review
Every conclusion traces back to the line of evidence that produced it, with a confidence score. Nothing is asserted without a source you can open.
Four steps, from raw evidence to signed-off report.
The order matters, because each step narrows the next. Stop after step three and export, or run the full loop through to corrective actions.
Upload the evidence
Log files, monitoring exports, change records, incident timelines, ticket dumps, screenshots. Drag in what you have; ZANALYSE works with partial data and tells you where it is thin.
Answer the guided questions
A structured ITIL v4 problem management interview: what changed, what was affected, when it started, what has been ruled out. Roughly ten minutes of your knowledge, captured properly.
Review the analysis
A cause chain, a fishbone breakdown, contributing factors and a confidence score per branch. Challenge any node and the analysis re-runs against your correction.
Assign corrective actions
Proposed permanent fixes and preventive measures, each tied to the cause it removes. Export the finished analysis as a PDF report to attach to your problem record and known error database.
Recognised techniques, run consistently.
ZANALYSE does not invent a methodology. It applies the ones your auditors, your customers and your own problem managers already accept, and it applies them the same way every time, on every problem record, regardless of who is on shift.
- 5 Whys: an iterative cause chain, each step held to the evidence that supports it
- Fishbone / Ishikawa: hypotheses sorted across people, process, technology, partners, governance, data and service design
- Confidence scoring: every branch rated, so weak reasoning is visible instead of buried
- Corrective and preventive actions: separated, prioritised, mapped to the cause each one removes
- Full audit trail: inputs, questions, answers and revisions retained for the life of the record
FISHBONE VIEW OF TICKET #APPA060, "VPN SERVICE DISRUPTED"
Built for the person who has to write the report.
Problem & incident managers
Clear the RCA backlog instead of triaging it. Consistent output across every analyst, every shift, every site.
Managed service providers
Deliver root cause reports as a contractual commitment, without adding senior headcount to every account.
Risk, compliance and IT leadership
Evidence a maturing problem management practice, and see which causes recur across the estate, the pattern behind the ticket volume rather than the volume alone.
Start monthly. Or take an annual licence.
Capacity you top up whenever you need it. Prices are per organisation, in EUR, excluding VAT. No per-seat charge, so you can invite as many colleagues as the work requires, within the concurrent-user limit of your subscription.
Monthly
A rolling subscription for teams who want to start now and commit later. Upgrade whenever it suits you.
- 100 named users, up to 25 at a time
- 25 RCA reports included per month
- Root Cause Analysis with confidence scoring
- PDF export
- Standard email support
Standard
The full analysis engine for teams running their own problem management process.
- Unlimited named users, up to 50 at a time
- 600 RCA reports included per year
- Root Cause Analysis with confidence scoring
- PDF export
- Standard email support
Full
Everything in Standard, plus higher capacity, hands-on onboarding and priority support.
- Unlimited named users, up to 100 at a time
- 1,000 RCA reports included per year
- Root Cause Analysis with confidence scoring
- PDF export
- Hands-on onboarding meeting
- Priority support with a named support contact
Additional RCA packs
Buy extra analysis capacity at any point in the licence year. Packs do not expire while your licence is active.
100 RCA reports
Suits a team clearing a modest backlog.
200 RCA reports
The common top-up for multi-site operations.
500 RCA reports
Best rate per run, for providers analysing at volume.
Commit longer, pay less
Configure your licence.
Set it up here and the price updates as you go. You will confirm company details and VAT number at checkout.
The most sensitive thing you will ever upload. We treat it that way.
Analysis data is processed and stored in the EU by default. Sub-processors are listed publicly and updated with notice.
A Data Processing Agreement is part of every subscription. International transfers are covered by Standard Contractual Clauses.
Uploaded content is never used to train models. It is processed to produce your analysis and nothing else.
Set a retention window per workspace, or permanently delete a case and its source files at any time.
Before you buy.
What is counted as 1 RCA report?
The Standard licence includes 600 Root Cause Analysis (RCA) reports, while the Full licence includes 1,000. Each RCA report is counted as a single ticket within the application, allowing you to process up to 600 or 1,000 RCA reports respectively.
What file types can I upload?
Plain text and structured logs, CSV and JSON exports, PDF and Word incident reports, monitoring and APM exports, and images such as dashboard screenshots. Archives are unpacked automatically.
How does this support an ISO 27001 or DORA audit?
Every analysis keeps a complete record of inputs, questions, answers, revisions and the resulting corrective actions. That record is exportable as evidence of a functioning problem management process, which is the part auditors most often find undocumented.
Do we need to connect ZANALYSE to our systems?
No. Manual upload is the standard route and needs no access to your environment. Nothing is installed, and no firewall rules or service accounts are required.
What happens if we run out of RCA reports mid-year?
Add a pack from your account and continue immediately. Packs stay valid for as long as your licence is active. RCA packs do not expire at year end.
Can I buy licences in my local currency?
All prices are set in EUR and invoiced in EUR.
Who is behind ZANALYSE?
ZANALYSE is owned and operated by ZANGAARD, a Danish-owned IT services group. The product is sold and supported worldwide as a standalone service.
Try it against an incident you have already solved.
It is the fastest way to judge the output: run a case where you know the answer, and see whether ZANALYSE finds it, and what it finds that you did not.