System of record, meet system of action.
Fusion Framework is the gold-standard system of record for Business Continuity Management. AirTee.ai is a system of action — the same workspace runs the incident, drafts the regulator notification, updates the resilience plan, and writes the After-Action Report. Here's where they overlap, where they don't, and how to choose.
Choose Fusion if you need a documents-first BCM system. Choose AirTee if you need the documents to follow what actually happens.
Fusion Framework was designed in an era when Business Continuity was a quarterly artefact: the BIA was finalised once a year, the BCPs were approved by sign-off cycle, and the dependency map was a slide deck. Fusion did this category better than anyone else, and for organisations that still operate on that cadence, it remains a defensible choice.
AirTee.ai was built for the opposite assumption: that critical services change weekly, vendors are switched in a sprint, regulators ask 24-hour and 72-hour questions during the incident, and the BIA is wrong by the time it's signed off. The platform is event-first. Every resilience artefact — BIA, BCP, vendor profile, exercise, control update — is a property of a live model kept current by real incidents and real exercises.
Practically: if you ran a tabletop in Fusion last quarter, the lessons are in a PDF. If you ran the same tabletop in AirTee, the BIA already reflects the divergence between assumed RTO and real recovery time, the BCP was edited automatically against the new dependency, the exercise schedule queues the next iteration, and the auditor sees the change log. That is the difference between a system of record and a system of action.
Side-by-side, by capability.
Honest scoring. Where Fusion is genuinely strong, we say so. Where AirTee is the only one that ships the capability, we say that too.
| Capability | Fusion Framework | AirTee.ai |
|---|---|---|
Business Impact Assessment RTO/RPO/MTPD per service | ●Form-driven, periodic | ●Living BIA, updates from telemetry |
Resilience / Continuity Plans BCPs, IT-DR runbooks | ●Strong template engine | ●Plans tied to live dependency graph |
Live incident command | ○System of record only | ●AI-augmented commander surface |
Regulator notification clocks DORA 24h initial · GDPR 72h · NIS2 24h early warning | ◐Manual tracking | ●Automatic, per-jurisdiction templates |
AI After-Action Report Drafted from incident telemetry | ○No | ●AI-drafted from the incident record |
Vendor & supply-chain risk | ●Questionnaire-native | ●Graph-native, concentration and country risk visualised |
Exercises & tabletops | ●Manual scheduling | ●AI-generated scenarios and grading; annual planner |
DORA ICT third-party register | ◐Hand-maintained | ●Vendor register with attestations, linked to services |
Frameworks out-of-box | ISO 22301, NIST, custom | ISO 22301, ISO 27001, SOC 2, DORA, NIS2, NIST SP 800-61, UK/EU GDPR, PRA SS1/21; MITRE ATT&CK mapping on request |
Integrations w/ ITSM/SIEM/identity | ◐API + selected connectors | ●Native: Sentinel, Splunk SOAR, ServiceNow, Jira, PagerDuty, Opsgenie, Datadog; Okta and Entra directory sync + SCIM |
Pricing model | Per-user + module licensing | Monthly self-serve from $500; Enterprise on custom contract |
Single-tenant / EU residency | ●Yes | ●UK / EU / US dedicated environment, Enterprise tier |
Three scenarios where Fusion stays.
- ▍Your enterprise risk team owns Fusion as part of a wider GRC suite (with Audit, Policy, Vendor) and the resilience module is one of many.
- ▍You have deep custom integrations into Fusion (e.g., a regulator extract feeding a parent group's reporting) that would take 6+ months to rebuild.
- ▍Your operating model is genuinely document-cycle driven — your regulator accepts annual artefacts and your incidents are rare and small.
Three scenarios where AirTee replaces Fusion outright.
- ▍You're under DORA, NIS2, PRA SS1/21 or HKMA OR-2 and the regulator's clocks are now part of your incident workflow, not your reporting cycle.
- ▍Your resilience team is the same humans who run live incidents — and they're tired of switching between Fusion (the plan) and ServiceNow / PagerDuty (the action).
- ▍You want exercises to be useful — not a calendar event, but a feedback loop that updates the BIA, the BCP, and the controls automatically.
How a Fusion → AirTee migration actually goes.
The migration is a guided, three-stage programme. Stage one is import: AirTee ingests Fusion BIA records, BCP templates, dependency models, vendor records and exercise history via the Fusion API or CSV export. Most customers' Fusion data lands in AirTee within the first week. Service ownership is reconfirmed during stage one because the most common Fusion data-quality issue is stale ownership.
Stage two is wiring: AirTee connects to your live signal sources (Sentinel / Splunk for security, ServiceNow / Jira for ITSM, Okta / Entra for identity, your cloud accounts for posture, your vendor stack for third-party telemetry). This is where the BIA goes from static to living — when a dependency changes, the BIA flags itself for review.
Stage three is parallel-run: AirTee runs the next quarter's exercises and any live incidents, with Fusion still receiving exports for reporting continuity. After one full incident or one full exercise, customers can retire Fusion as the resilience system. Self-serve tenants are live the same day; enterprise rollout is planned with you.
Quick answers
- Does AirTee replace Fusion Framework entirely?
- For most customers, yes. AirTee handles Business Impact Assessments, Resilience Plans, exercises, vendor risk and incident command in one workspace, and exports to whatever system of record the rest of the business needs. A minority of customers keep Fusion for legacy reporting integrations and run AirTee for active operations.
- What's the biggest functional difference?
- Fusion Framework is built around the document. AirTee is built around the event. When an incident occurs, AirTee runs it, drafts the regulator notification, writes the AAR and updates the resilience plan — without leaving the platform.
- What about migrating from Fusion Framework?
- AirTee imports Fusion BIAs, resilience plans and dependency models via a guided migration. Self-serve tenants are live the same day; enterprise rollout is planned with you.
- Does AirTee support DORA, NIS2 and PRA SS1/21 the same way Fusion does?
- Yes, with one important difference: AirTee generates the DORA ICT third-party register and the SS1/21 important-business-services list directly from the dependency graph, rather than asking analysts to re-enter the data. The artefacts are derived, not maintained.
- What about cost?
- AirTee is self-serve from $500 per month, with Enterprise on a custom contract. The operational tooling — incident command and After-Action Reports — sits in the same subscription as the plans and exercises.
See AirTee in your environment.
We'll model one of your real scenarios live.