Managed Continuity.
Managed operations for critical sovereign platforms. Selective, founder-led, with a closed contract and operational metrics. Continuation opens only on platforms we have already reviewed, stabilized or hardened — the evidence base that makes a serious operating commitment possible.
- ✓Your platform has gone through a Kverno Platform Review, Rescue or Hardening.
- ✓You need to externalize recurring operations under a closed contract.
- ✓You expect reusable runbooks, operational metrics and quarterly CISO/CIO review.
- ✓Selective intake and a 6-month contractual minimum work for you.
- ✗You are looking for a generic MSSP with open coverage.
- ✗You need standardized 24/7 — extended coverage is contracted case by case.
- ✗You expect us to take on operation of a platform without prior engagement.
- ✗You have an active incident: route to a dedicated incident response team.
What the operation includes.
- 01
Prior platform knowledge.
Operations begin on the technical base of a prior Review, Rescue or Hardening. Inherited runbooks, configs and reference architectures from day one.
- 02
Closed contract and metrics.
Scope, service window, SLO/SLA and responsibilities agreed in writing before kickoff. No inflatable options, no open-ended scope.
- 03
Real operational continuity.
6-month minimum to build operating cadence, run-in runbooks and an evidence base. 60-day exit notice from either party, no penalty.
- 04
Reporting your CISO can use.
Monthly operational report and quarterly review with CISO/CIO. Shared access to repositories, changelogs and observability where applicable.
- 05
Credential and secret custody.
Chain of custody, break-glass and rotation procedures documented before the first service window. Encrypted secrets, auditable accesses.
- 06
Extended coverage under contract.
Extended availability, including 24/7, contracted case by case for environments where it adds real value. Window, on-call and escalation defined in writing.
From engagement to recurring operations.
- 01 Review / Rescue / Hardening
Prior engagement
The first operational contact is never Managed. It goes through Review, Rescue or Hardening. There we assess whether the platform fits managed continuation.
- 02 1-2 weeks
Qualification
If it fits, we open qualification: operational scope, service window, metrics, custody, inherited runbooks, gaps. If it does not fit, we say so directly.
- 03 1-2 weeks
Contract and onboarding
Specific operations contract signed. Technical onboarding: accesses, observability, incident channels, operating calendar, first quarterly review planned.
- 04 ≥ 6 months
Recurring operations
Operations under contract. Monthly reporting cadence, quarterly review with CISO/CIO. 60-day notice from either party to terminate; documented handover at no additional cost.
What's not included.
- Generic MSSP nor open coverage over any platform.
- Active incident response in progress (we route to a dedicated team).
- Official support or Enterprise licensing — that belongs to Filigran and to each vendor.
- Operation of platforms we have not been able to review first.
Start with the right format.
If you have not worked with Kverno before, start with a Platform Review (2 weeks, from 12 k€) or Rescue & Hardening (from 40 k€) depending on the state of your platform. Managed Continuity opens from there, never as the entry point.
See Rescue & Hardening →Frequently asked.
01 How is the scope designed?
02 What hours of coverage do you offer?
03 Do you work on platforms you didn't deploy?
04 What happens if I decide to internalize later?
Coming from a prior engagement?
If we have already worked on your platform, or you are considering starting, let's talk. If it fits, we'll say so. If not, we'll point you elsewhere.