Documentation
How PostShip checks your site, connects to your tools, and only alerts when something breaks. Each page says what the feature does, how to set it up, what triggers an alert, and what your plan allows.
Create a projectYour first URL checked in 5 minutes.Connect your hostEvery deploy checked to the second.Get alertedEmail, Discord, Slack — and when to stay quiet.From your CIOne request, one Ship Score, one exit code.
Getting started
2What PostShip does, and your first project in five minutes.
Checks
8What PostShip looks at on your pages, on every pass and every deploy.
- HTTP and assetsThe default check — the page responds, with the right status, within the timeout, and its JS and CSS files still exist.
- Allow PostShip in your firewallWhen your host puts an anti-bot challenge in front of PostShip — Vercel Security Checkpoint, Cloudflare — what to allow, and where.
- The payment pagesPostShip reads your site, finds the pages that lose money when they break — pricing, sign-up, log-in, checkout —, checks each one, and you choose.
- Click-through journeysA starting page and steps — click, fill in —, replayed in a real browser up to the payment page, without ever paying.
- IndexabilityCan Google still crawl and index your site after this deploy? robots.txt, noindex, canonical, sitemap and share cards, checked on every release.
- API contractPostShip learns the shape of a JSON response over 3 runs, then alerts as soon as it drifts.
- PerformanceEach page's response time over time, the before/after deploy, and the “normal” band.
- Accessibilityaxe-core on each monitored page, in a real browser, contrast included — a score, the defects with the offending element, the trend.
Deployments
4Checking at deploy time: webhooks, hosts, GitHub, Ship Score.
- Connect your hostTrigger a full check within the second following every release, and what that run produces in addition.
- Connect GitHubPublish the result of every checked deploy on the commit, as a Check Run named PostShip.
- Ship ScoreThe grade out of 100 of every production deploy, category by category, and what becomes of it.
- PreviewsCheck every preview deploy on its own address, before it goes to production, and decide separately whether to be alerted about it.
Alerts & incidents
3Where and when PostShip warns you, and how it keeps quiet when it should.
- Email, Discord, SlackWho receives what, through which channel, and why an alert sometimes doesn't go out.
- RulesConfirmation before alert, quiet hours, minimum outage, working hours, severity by page type, grouping, muting the project and silencing a URL.
- IncidentsHow an incident opens and closes by itself, what the Incidents page shows, and how to publish it.
Security & integrity
2What must stay closed, what must stay the same, and what must stay yours.
- Site securityA score out of 100 and the list of what to fix, assembled from the checks that run on every deployment — headers, exposed files, secrets, cookies, redirects, third-party scripts, TLS.
- Domains and certificatesThe full DNS, the served certificate, the domain's registry record and email, checked every 6 hours for the production domain and its subdomains — with the history of what changed and 3 alerts.
Public pages
2What your clients see: status page, badge, ship cards, reports.
Automation
2API, CI, exports: PostShip from your tools.
Account & plans
3Plans, billing, team, data.
- Discover / Pro / Pro Plus plansThe full table of what each plan allows, limit by limit — projects, URLs, cadence, collaborators, host, probes.
- ProjectsCreate a project, what the base URL imposes on monitored URLs, pausing, labels, deletion and quotas.
- Account securityHow you sign in to PostShip — passkeys, email code, Google, GitHub —, two-factor authentication, linked accounts, changing your address and what a session protects.