Reliable hosting needs backups, observability, deployment discipline, recovery planning, access control, and a clear response model.
Managed hosting is not just a server running your application. It’s a set of operational practices that keep the system reliable, recoverable, and understood.
Most hosting failures aren’t hardware failures. They’re operational failures — missing backups, unmonitored errors, deployments without rollback plans, and access credentials no one can locate.
What should actually be included
Backups with tested restores. A backup that has never been restored is not a backup — it’s a hope. Any serious hosting arrangement should include scheduled backups and documented restore procedures that have been verified.
Observability. You should know when your system is slow before your users tell you. That means uptime monitoring, error rate tracking, and alerts that go to someone who can act on them.
Deployment discipline. Every change to a production system should be tracked, reversible, and applied through a consistent process. Ad hoc changes made directly to production are how stable systems become unstable ones.
Access control. Who has access to what, and why? Production credentials should not live in Slack messages or personal email. Access should be provisioned, documented, and revocable.
A response model. When something breaks at 2am, what happens? Who gets alerted? Who has the access and the knowledge to respond? This is not a question to answer during an incident.
A managed hosting arrangement that doesn’t include these things is just rented infrastructure with someone else’s risk.