A little longer, a little less · Save 28% for 6 months or 50% for a year, paid once See the plans ↗

Illustrative service scenario

Plan a shared project wiki with a backup maintainer

Map page history, attachments and database state, then rehearse a restore that a second person can follow.

Starting point

Map page history, attachments and database state, then rehearse a restore that a second person can follow.

Workflow boundary

Name the replacement maintainer before an update and have them locate the recovery record unaided.

Resource boundary

Grove is a starting catalogue allocation to evaluate: 2 vCPU, 4 GB RAM, 60 GB SSD and 2 TB monthly transfer. Measure the actual application; no service count or performance result is implied.

Ownership

Give members application accounts, keep host administration limited, and identify a backup maintainer.

Recovery outcome

Complete the recovery kit and test a separate restore before relying on the design.