Deployment
This page describes CertWatch's own hosting for context — it isn't a guide to deploying CertWatch yourself; there is no self-hosted distribution today.
The product
CertWatch runs on Fly.io. The marketing site (certwatch.sh) and
the authenticated app (app.certwatch.sh) are one deployment that renders differently by
hostname. Keeping those two product surfaces together avoids a second auth, cookie, and CORS boundary
while they share the same API and release cadence. A separate scheduled process runs the actual
TLS/domain checks and alert delivery. Every change is reviewed and tested through a pull request, merged
to a shared integration branch that deploys to a persistent staging environment, then promoted to
production.
This docs site
docs.certwatch.sh (issue #220) is an intentionally separate, independently built and styled
static site - its own directory (docs-site/) in the CertWatch repository, with its own build
and test commands, not bundled into the app's frontend build. That separation is deliberate: documentation
should not share a build or an outage with the product it's documenting. It is hosted on Cloudflare Pages
as the certwatch-docs project, with no database, API, authentication, or checker process.
The docs are published with each production release, from the same commit as the app that release deploys, so they describe the behavior production has, not changes still on staging. Rolling production back to an earlier release rolls these docs back with it. The product's staging host uses this production docs site.
Releases
The product ships through pull requests merged to a shared integration branch. Each merge is tested and deployed to the shared staging environment, and a release promotes a staging-tested commit to production after its tests run again — every change is reviewed, tested, and running on staging before it reaches real accounts.