Continuity
A recovery plan is only as good as its last test.
Write down what you would do when disaster strikes, rehearse it, and see which recovery plans are proven and which are going stale. Plans with RTO and RPO targets, versioned runbooks, dated tests with findings and sign-off, and a backup and recovery register.
Free while in beta
In beta: open to invited organisations and not billed yet. Write to us and we add yours.
What it does
- Each plan tested, due soon, overdue or never tested, from its last signed-off test
- Achieved RTO and RPO against the plan’s targets
- Findings as corrective actions with fix-by dates, Jira tickets when Jira is connected
- Backup and recovery register: retention, restore tests, 3-2-1 gaps
- Branded PDF of every plan and test, with a SHA-256 document register
How this tool bills
Today's list prices in EUR, read from the qzila price list when this page was built. You are billed monthly for what you used.
In beta: open to invited organisations and not billed yet. Write to us and we add yours.
The API
Every qzila tool is a GraphQL API first; the web UI is one client of it. Anything you can do in the browser you can do from a script, a CI job or the Asign platform.
https://continuity.tools.qzila.com/graphqlPOST · application/json · { "query": "…" }
Requests are authenticated with your qzila session (the same sign-in as the browser). For automation, sign in once at identity.qzila.com and reuse the session cookie; API keys for service accounts are on the roadmap.
Whatever this tool detects — a verdict flip, a regression, a change, an incident — is emitted as a signal to the qzila alert hub, which forwards it to email, Slack, a webhook, SMS or Jira, and to ServiceWatch. Each signal carries the asset it belongs to, so you can correlate it back to your own inventory (or to an Asign asset).
Main operations
createScenariomutationCreate a recovery plan: name, recovery type, RTO and RPO targets, test cadence.
mutation { createScenario(input: { name: "Ransomware on file servers", threat: "Ransomware", targetRtoMinutes: 240, targetRpoMinutes: 60, cadenceDays: 182 }) { id state } }scenariosqueryEvery plan with its state, last test and next due date.
query { scenarios { name state lastExercisedAt nextExerciseDueAt } }scheduleExercisemutationSchedule a test of a plan: tabletop, walkthrough, simulation and more.
mutation { scheduleExercise(scenarioId: "s_1", input: { title: "H2 tabletop", type: tabletop, plannedAt: "2026-11-12T09:00:00Z" }) { id status plannedAt } }
Send requests to https://continuity.tools.qzila.com/graphql
Questions about Continuity
Where do alerts go?
Every tool reports through one alert hub. You choose per destination: email, Slack, a webhook, SMS or a Jira ticket — and ServiceWatch shows the same signals on one board.
Where is my data kept?
The tools run on AWS in the EU (Frankfurt), operated by adcore s.r.o., a Slovak company. A few services they rely on sit outside the EU — Stripe for card payments, Google for analytics after your consent, the threat-intelligence lookups behind SafeCheck — and the privacy policy lists each one.
Start with one tool. Add the rest when you need them.
In beta: open to invited organisations and not billed yet. Write to us and we add yours.