Hosting

Someone has to keep it running.

Hosting, monitoring, backups, updates and the steady stream of small changes a live property needs. Billed to your account, not resold through ours.

Start a project See the work

What you get

Deliverables, not capabilities.

Hosting Set up in your account on infrastructure you control, with us administering it.
Monitoring Uptime and error checks that alert a person, not a dashboard nobody opens.
Backups Automated, off the primary machine, and restore-tested rather than assumed.
Updates Dependency and security patching before it becomes an incident.
Changes The ongoing edits, new pages and fixes that every live site accumulates.
Reporting What changed, what broke, what was fixed.

Why this way

A green status page is not proof.

The most common failure on a live site is not an outage. It is something that returns a perfectly healthy response code while being completely broken: a stylesheet that stopped loading, a form that submits into nothing, a page that renders but no longer contains the thing it is supposed to sell.

Every one of those returns 200. Uptime monitoring reports all clear. The business finds out when someone mentions it in passing weeks later.

So checks here look at the body of the response, not the status code. Does the form actually deliver. Did the CSS actually load. Is the page still the page. That is a more annoying way to monitor a site and it is the only kind that catches the failures that cost money.

Practice

This site is deployed with the full response verified after every release, not just the status code. The deployment process, including a mistake that shipped inert security headers and how it was caught, is documented in the repository rather than quietly fixed.

Locally

The person running it has a name and a phone number.

Every property on the work page is hosted and maintained here. Nothing is handed to a hosting company and forgotten, which is why the certificates, the mail records and the uptime on those five sites are things this house can answer for directly rather than escalate.

None of that requires being in Orlando, and it would be dishonest to claim otherwise. What being local changes is who you reach when something is down at seven in the morning: a person in your own city who already knows how your site is put together, instead of a ticket queue that opens by asking you to describe the problem.

Questions

Asked and answered straight.

Do you mark up hosting?

No. Hosting is billed directly to your account by the provider. For a static site that is often free or close to it. You pay us for work, not for reselling infrastructure.

What happens if we stop working together?

Nothing switches off. The hosting account is yours, the domain is yours, the code is yours. You remove our access and the site keeps serving.

How fast are changes?

Small changes are usually same or next day. Larger work is scheduled. What we will not do is let a broken thing sit because it was not on the plan.

Work that used this (3)

Tell us what needs building.

Send what you have and what is not working. You will get a straight answer about whether this house is the right fit, including when it is not.

Start a project hello@corsamediahouse.com