Maintenance Checklist Builder

Generate a copyable maintenance checklist for self-hosted services.

Status: Live · Processing: the checklist logic runs locally in your browser. Fill in the service basics, risk, dependencies, and readiness answers, then copy the Markdown into a note, ticket, runbook, or maintenance log.

This does not connect to servers, inspect patches, verify backups, or magically make maintenance less boring. It just turns the usual hand-wavy “I should probably document this” into a practical checklist before the window starts.

Maintenance Checklist Builder

Answer a few boring-but-important questions and generate a copyable maintenance checklist for a self-hosted service.

Privacy note: the checklist logic runs locally in your browser. Your form answers are not intentionally submitted to CyganLabs, stored in WordPress, or sent to a server by this tool. Like the rest of the public site, this page may still load normal WordPress, security, analytics, or ad scripts. Do not paste secrets here.

No secrets: do not paste passwords, API keys, SSH keys, tokens, recovery codes, private keys, or other secrets here. This page only needs yes/no readiness answers.

Service basics

Name the thing, pick the closest type, and set the normal maintenance rhythm.

Service name

Service type

Environment

Maintenance cadence

Risk and exposure

This controls how cautious the checklist gets. Public and user-impacting services earn less cowboy behavior.

Risk level

Public internet exposure

Users affected

Dependencies

Tell the tool whether backups and databases matter. If you are not sure, say that; the checklist will be more cautious.

Backup dependency

Database dependency

Maintenance readiness

The dangerous part is not updating. The dangerous part is updating without knowing how to undo it.

Update method known

Rollback method known

Empty state: fill in the required fields, then generate a checklist.

Generated Markdown checklist Copy this into a note, ticket, runbook, or change record.

Incomplete form warnings will appear above instead of generating a half-baked checklist. Half-baked maintenance is how servers become archaeology.

When to use it

Before updating a self-hosted app, database, reverse proxy, media service, identity system, or automation job.
When you need a maintenance note that covers pre-checks, backups, rollback, update steps, health checks, security checks, and documentation.
When “I know how this works” has quietly become “future me can excavate the ruins.”
When a service affects other people and you need a copyable Markdown checklist before touching production.
When the honest answer is “not sure” and you want the risky unknowns called out clearly.

What it does not do

It does not connect to servers, dashboards, repositories, databases, backup systems, monitoring tools, or package managers.
It does not verify patch status, uptime, public exposure, vulnerabilities, backup quality, restore readiness, or compliance.
It does not replace real backups, restore tests, monitoring, documentation, change control, or human judgment.
It does not ask for passwords, API keys, SSH keys, tokens, recovery codes, private keys, or other secrets.
It does not store maintenance details, create accounts, add tool-specific telemetry, or intentionally submit your answers. Normal site scripts may still load around the tool page.