HaloPSA
Tickets arrive in HaloPSA against the right client, with the priority set.
Connect once and forget about it.
Tidehawk finds every SSL certificate and domain across all your clients, keeps watch on them, and raises a ticket in your PSA while there is still time to renew. No spreadsheet, no agent to install, no Monday morning surprise.
No credit card required · Cancel anytime · UK data residency
The maximum life of a public TLS certificate is falling from 398 days to 47 days by 15 March 2029. Every certificate for every client will need renewing about every six weeks. MSPs that get ready now will barely notice. The rest will find out one outage at a time.
Until March 2026
398 days
about 1 renewal a year
15 March 2026
200 days
about 2 renewals a year
In force now
15 March 2027
100 days
about 4 renewals a year
In 116 days
15 March 2029
47 days
about 8 renewals a year
Domain validation must be repeated every 10 days by 2029, down from 398. Read the ballot
Tidehawk finds every certificate from the public certificate logs and live checks. A certificate that was renewed by someone else, or one nobody knew about, still shows up. No agent, no spreadsheet.
A 30-day warning is no use on a 47-day certificate. You choose how many days before expiry to be told, for all clients or for one, so the ticket arrives while there is still time to renew.
Every expiry becomes a ticket in your PSA, and the ticket closes itself when the renewed certificate is seen. You pay per client, not per certificate or per renewal, so the change costs you nothing extra.
2
PSAs integrated
HaloPSA · ConnectWise · 3 coming soon
LON1
Hosted in London
Servers, data, backups and email
24/7
Certificate discovery
From public certificate logs and live checks
Logged
Every action recorded
Who did what, and when, for your audits
Finding the certificates, watching them, and getting the ticket to the right engineer. One tool for the whole job.
Give Tidehawk a client's domains and it finds every certificate issued for them, including the ones nobody wrote down.
When a new certificate is issued for any of your clients, it shows up in your inventory within minutes. Renewals are matched to the certificate they replace.
The renewal date of every domain is tracked as well, so a lapsed registration never takes a client offline.
When a certificate gets close to expiry, a ticket lands in your PSA against the right client, with the priority you chose. It closes itself once the renewal is seen.
Choose how many days before expiry to be told, by email or ticket, for all clients or one at a time.
PDF and CSV expiry reports per client, with your branding, ready for a quarterly review or an audit.
When a certificate needs attention, the ticket is already in your PSA. Same board, same queue, same process your engineers use today. HaloPSA and ConnectWise are live today; Autotask, NinjaOne and Syncro are coming soon.
Tickets arrive in HaloPSA against the right client, with the priority set.
Connect once and forget about it.
Tickets appear on your ConnectWise board, attached to the right company.
Pick the board, and that is it.
Tickets go to the right Autotask queue with a priority to match the urgency.
Works with any Autotask region.
Tickets open in NinjaOne with the certificate details your engineers need.
Connect once and tickets land where your team already works.
Tickets go into Syncro and are matched to the right customer for you.
Sign in once. Every expiry becomes a Syncro ticket.
Use one PSA, several, or none. Change your mind at any time.
Connect yours in a couple of minutesAdd a client, paste in their domains, and Tidehawk takes it from there.
One client per end customer. Paste in their domains, as many as you like. Duplicates are tidied up for you.
It searches the public certificate logs and checks the live servers. Everything it finds appears in your inventory within minutes.
As a certificate or domain nears expiry, your team gets an email, a PSA ticket, or both, with everything they need to renew it.
What you get from the day you add your first client.
No more finding out a certificate expired because a client rang. Tidehawk is watching all the time, so your engineers are not.
A branded report per client whenever you need one, and a record of every alert and renewal to show what you did and when.
Expiry tickets go straight into HaloPSA or ConnectWise with the client, the certificate and the priority already filled in. Nothing new for the team to learn. Autotask, NinjaOne and Syncro: coming soon.
Everything runs in London. Credentials are encrypted at rest, and each MSP's data is kept apart at the database level, not just in the application.
// data residency
Set it up in an afternoon. Your first client is monitored within minutes.