Docs

Enough to get monitoring in about five minutes.

1. Create an organization

Sign up with an email address or with Google, Microsoft or Apple. You get your own organization — nobody else’s data is ever in it.

2. Make a group

A group is the unit of alerting: a client, an environment, a team. Endpoints live in groups, and contacts are attached to groups with a severity level, so the right people get the right messages.

3. Add an endpoint

A hostname and a port. HTTPS on 443 is the common case; SMTP, IMAP and POP over TLS work the same way. SSLup checks it immediately so you can see the result rather than waiting for the next sweep.

4. Add contacts and channels

Email needs nothing but an address. Slack, Teams and Discord take an incoming webhook URL. Telegram needs a chat id. Pushover needs a user key. Each contact chooses which kinds of event they want.

5. Add uptime monitors

On paid plans, an uptime monitor checks whether the thing is actually reachable, as often as every five minutes. If you already have certificate endpoints in a group, SSLup offers to copy them across rather than making you type the hostnames twice.

Things worth knowing

• Alerts are deduplicated. One problem is one alert, with repeats on the schedule the group sets, not one message per check.
• Maintenance windows suppress alerts for a period without stopping the checks, so the history stays honest.
• The activity log is the answer to “what changed” — it records certificate changes, alerts, sign-ins and administrative actions.
• Paused endpoints are shown as paused. If a plan change puts you over your limit, the excess is paused and visible, never silently unwatched.

Something missing here? Ask — the gaps people ask about are the ones that get written first.