Hosting

Hosting is configured to scale with demand — whether that's a marketing campaign or unexpected press coverage — so the site doesn't go down under load. Resource limits are set with headroom and monitored for spikes so I can adjust before they become outages. If sustained growth requires a bigger infrastructure tier, that's discussed ahead of time, not discovered mid-crisis.

Hosting is billed separately as an ongoing monthly cost — website design is a one-time build, hosting is the infrastructure that keeps it live. This keeps the two decoupled: you can move hosting elsewhere later without renegotiating the build. Pricing depends on the stack and expected traffic, quoted upfront.

Server-level monitoring flags outages automatically and triggers a response rather than waiting until morning. For critical infrastructure failures, you get contacted directly instead of discovering it yourself. This is what separates managed hosting from a self-service hosting panel.

Yes — if you already have infrastructure such as AWS, an existing VPS, or a company-standard provider, the site can be deployed there instead of through me. In that case, ongoing server management becomes your team's responsibility, or it's added as a separate cloud solutions engagement. Either path works as long as it's decided before launch, not after.