Manage several projects on your own server.

Each project gets its own port, nginx site and process. A single small server can carry a marketing site, a side project and a staging copy without them interfering.

Release-based deployments build beside the current release. A build failure before switchover leaves that release selected; shared configuration, database changes and resource pressure can still affect the running application.

TLS is issued and renewed per domain, cron entries and background workers are configured next to the project they belong to, and both are restarted after a deploy.

A health check requests the URL every 60 seconds and reads the status code. A heartbeat is switched on from a scheduled job or a background worker itself, so a cron that quietly stopped running becomes a notification instead of a discovery three weeks later. Three consecutive failures is what counts as down, and both kinds of monitor are on every plan.

Pick the threshold and a notification arrives when it trips, then another when it clears, so a disk filling up is something you are told about while there is still room. Alerting on server metrics is a Business feature; the uptime monitors are not.

Depfloy charges a flat plan. Your provider bills separately for server capacity and any metered storage or bandwidth; traffic may change those costs.