Create a care plan

A care package ties a set of features Hyperion already has to a customer who pays for them. It switches them on, keeps them on, records the price and a billing reminder date, and puts the site back when the package is cancelled. Hyperion never invoices or charges anyone. Packages are defined once, on the master, and activated per hosting; see Put a site on a care plan. The documentation uses the term care plan for what the panel calls a care package.

Before you start

You hold the Manage hosting profiles permission. Owners and Administrators have it. Others are sent to the dashboard with “admin role required”.
You know which features the package should sell. Only the features you set are touched. Everything else on a site stays as it is.
To send the care report, the node that owns a customer’s site needs a mail relay (Settings, then Mail) and the site needs a recipient. See Send care reports to customers.

Steps

Open Care packages in the sidebar. With no package yet, the page explains the idea and shows the New package form. Otherwise click New package.
Under Name:
- Name: what the customer sees, such as “Care plan”. At most 64 characters.
- Handle: used by the API. Blank derives it from the name (lowercase letters, digits and -, at most 64).
- Customer-facing description: shown to the customer on their own hosting. Write what they get.
Under Price (optional):
- Price: in major units, such as 490.00. A comma works as the decimal separator. Zero is allowed, a negative price is refused.
- Currency: free text up to 8 characters, such as Kč.
- Billing interval: No interval — no reminder, Monthly, Quarterly or Yearly.
Under Kept switched on, set each feature to Leave alone — not part of this package, On — included, keep it on, or Off — keep it switched off:
- Automatic WordPress updates
- File integrity & malware scanning
- Uptime monitoring
- Brute-force protection
Leave alone is not Off. A package touches only what it includes, so two packages can share a site without fighting.
Under Firewall:
- Firewall rules: Leave alone, Standard — at least Standard, keep it on, Strict — keep it on Strict, or Off — keep the firewall switched off. Standard keeps a Strict level someone set by hand.
- OWASP Core Rule Set: Leave alone, Detection only — log, never block, Blocking, or Off — keep it switched off. Start with detection on a live site.
Under Backups, choose Automatic backups: Leave alone, Daily, Weekly, Monthly, Custom — every N days, or Off — keep scheduled backups switched off. These fields apply only when a cadence is set:
- Custom period: 1 to 365 days, for Custom.
- Keep backups for: days, 0 to 36500. Blank keeps the node’s default.
- Always keep latest: backups per site, 0 to 1000. Blank keeps the node’s default.
Under What the customer receives:
- Care report e-mail: Leave alone, Monthly, Weekly, Quarterly or Off — send no report.
- Language of letters: Leave alone — use the panel-wide language, English or Čeština. A site with its own setting keeps it.
- Report sections: tick what this plan’s customers receive: Attacks blocked, Updates applied, Traffic and disk, Availability, Backups, Integrity scan, Speed and Core Web Vitals, Monthly service checks. At least one must stay ticked. To send nothing, set the report to Off.
Under Monthly checks by hand, write one check per line as name | what you actually did. The note after the bar is optional. A line starting with # is a comment. At most 30 items, 120 characters per name and 300 per note. Empty means the four built-in checks: Pages and navigation, Forms and their delivery, Speed and Core Web Vitals, Still working after updates. Your own items appear in the customer’s report as written, so write them in the report’s language.
Tick Offered — show it in the activate picker on hosting pages, then click Create package.

The page answers Package "<name>" created. Activate it on a hosting from that site's detail page.

Edit, retire or delete a package

Click Edit package on a package, change the form and click Save changes.
What an edit reaches: the language, the monthly checklist and the report sections follow the edit onto sites already on the package. The price does not, unless you tick Also apply this price to the <n> sites already on this package. The features, backup cadence, firewall and care report cadence are copied to each site when you activate the package. A site that is already on it keeps what it was activated with. To move such a site to the edited package, cancel its activation and activate it again.
To stop selling a package without touching sites that hold it, untick Offered. The package is marked retired and cannot be activated on more sites.
A package that sets nothing shows sells nothing on its card.

Check that it worked

The package appears under Packages you sell with a green offered pill, its price, and one line per included feature. The monthly checks appear as <n> monthly checks by hand with this plan's list or built-in list.
A hosting’s Overview tab now shows a Care packages card and offers the package in Activate a package. The card is absent from every hosting until at least one package exists.

If it fails

“package name must not be empty” or “package name max 64 chars”: fix the name.
“could not derive a slug from the package name — set one explicitly (a-z, 0-9, -)”: the name has no letters or digits. Fill in Handle.
“price interval must be monthly | quarterly | yearly”: pick one of the interval choices.
“price not numeric” or “price must be ≥ 0”: enter a number such as 490.00.
“a care plan must send at least one report section — to send no report, set the report cadence to off”: tick at least one section.
“Package … was saved, but <node> did not answer …” after an edit: that node still holds the old checklist, language and report sections. Save the package again once the node is reachable.