For agencies and freelancers
Your clients shouldn't be the ones warning you.
Five to fifty sites, delivered then forgotten until the phone call. PostShip checks them on every release, keeps a status page in each client's name, and sends on the 1st of the month the report you should have written.
What happens, with nothing
The client calls: “the site is broken”
An updated plugin, an expired certificate, a form that no longer sends.
The monthly report, promised, never sent
Uptime, incidents, what was deployed: the client asks for it, you compile it by hand, two hours per client, or not at all.
Thirty sites, thirty accounts, thirty tools
Every site has its probe, its dashboard, its password.
What PostShip does for you
A status page in each client's name
status.theclient.com, in their colours, kept up to date by the checks, with no mention of PostShip.
How it worksThe monthly report, sent on its own
On the 1st, to their addresses: uptime, incidents, deploys, site checks.
How it worksThe thirteen site checks, outside the quota
Indexability, header security, domain email, certificate, sitemap, third-party scripts — on every site, on every deploy, without using up a URL.
How it worksYour collaborators on every project, no seats
A developer, a project manager, a read-only client: roles per project, not seats to count.
How it works
What we're often asked
My clients are on WordPress, Webflow, Shopify — not on Vercel.
PostShip checks any https site, at its own pace, with no host connected. Triggering on release requires a connected host or a webhook; without it, the cycle does the job.
Will the client see that it's PostShip?
From Team, the status page is at their address, in their colours, without our mention; the monthly report carries your name. PostShip is your tool, not your brand.
And if I have fifteen sites?
Team covers 10 projects, Agence 30. In between, Agence — and you change plan whenever you want, pro rata.