Install & first steps

From zero to a working programme, in the order that works.

Run it

One container, one data volume:

docker run -d --name continuum -p 8080:8080 -v continuum-data:/data continuum/continuum

Every install starts a built-in 6-month trial — no license file, no registration, no call-home. The continuum-data volume holds everything; back it up by copying it.

Connect your directory

Add an LDAP provider under Admin → Providers: server address, a bind account, one query for people and one for groups. Map directory groups to Continuum roles under Access & Security, and sign-in is directory-backed from then on. People sync on a schedule — leavers lose access when the directory says so.

Feed your estate

You don't write integrations — you pick the system you have. The integration catalog (vCenter, OpenShift, SolarWinds and the rest) opens a pre-filled provider dialog where only the real address and secret remain to type. Every feed lands as ordinary records: applications, assets, people, relations — nothing to model twice.

First assessment → criticality → plan → exercise

Score your first application through its questionnaire — criticality falls out of the score bands, not a dropdown. Build the recovery plan from steps with dependencies and watch the calculated recovery time against the RTO. Then exercise it in simulation mode: the gaps the run finds become tracked actions, and the loop starts again.

Go live with Life

Configure at least two message channels — SMS, WhatsApp, push; message templates are approved texts with slots, edited in one place. Set the escalation flow: which channels fire together, how long to wait, when to fall back to emergency contacts. Run a drill with communications on hold first — the board behaves exactly like the real day, without messaging anyone.

License it when the trial ends

Buy the band you need on this site. Resiliency signs the license file offline — the signing key never touches this server — and it appears on your account as a plain .lic. Upload it once on Admin → License: it verifies against the keys built into the product, with nothing to activate and nobody to call.

Licenses issued here also carry a serial and a renewal endpoint, which turns next year's chore into nothing at all. Your installation asks https://resiliency.biz/renew?serial=… once a day from 60 days before expiry and applies a bought renewal by itself — nothing to download, nothing to re-upload. The request carries the license serial and nothing else; the vendor cannot initiate it. An instance with no route out keeps renewing the offline way — buy, download, upload — and loses nothing but the convenience.

The full, always-current guide lives inside the product (/guide) and is answerable to AI clients through the MCP how_to tool — the two share one source.