About

SSLup is built by Michael Ginsberg, who spent years running networks and getting caught by the same two problems.

Why it exists

Certificate expiry and uptime are the same job wearing two hats. Something you depend on stops working, and you would rather know before your customers tell you. Yet the tools are usually separate: one product watches certificates, another watches whether the site responds, and you pay for both and correlate them by hand at two in the morning.

SSLup does both, in one place, and tells you through the channel you already read.

How it is built

Deliberately unglamorous. PHP and MariaDB, no framework, running on a server we control. Every deploy runs a set of checks that refuse to ship: undefined functions, columns that do not exist, forms whose handler cannot run, and a test that signs in as one organization and tries to read another’s data through the real code paths.

The last one matters most. Multi-tenancy done badly is not a bug, it is a breach, so it is the thing that is tested hardest.

What we will not do

• Sell an interval we cannot deliver. If a plan says five minutes, the scheduler does five minutes. A monitoring product that quietly checks less often than it claims is worse than no monitoring, because you stopped watching.
• Show a green tick for something nobody is checking. Paused is shown as paused, and a stalled scan says so on the dashboard rather than leaving yesterday’s numbers looking current.
• Make the free plan a trap. One certificate, forever, no card. If you outgrow it, that is a good day for both of us.

Where it is up to

Early, and honest about it. The monitoring works and is watching real production certificates today. Billing is not switched on yet, so paid plans are arranged directly. If you want to use it, get in touch — early users get more attention, not less.