Shipping is the cheap half.

Software decays. Dependencies get security advisories, platforms change their APIs, certificates expire, and traffic patterns shift. We stay on the deployment pipeline and the error budget after launch, because we run our own sites the same way and know what breaks quietly.

What usually goes wrong

The problems we are normally called in to fix.

Nobody is watching

The first you hear of an outage is a customer telling you, which means it has been down for a while.

Updates left undone

Dependencies with known vulnerabilities sit unpatched because nobody owns the job.

The developer disappeared

The agency that built it moved on, nobody has the credentials, and a small change is now a project.

What is included

What hosting and support means here.

Managed hosting

Deployed on infrastructure suited to the application, with staging environments and rollback.

Updates and security patching

Dependencies kept current and advisories acted on, rather than accumulating.

Backups and recovery

Automated backups that are actually tested, because an untested backup is a hope.

Monitoring and alerting

Uptime, errors and performance watched, so we know before your customers do.

Ongoing changes

A predictable amount of development time each month for the changes every live site needs.

What it is for

The outcome we aim at.

  • Problems found before customers find them
  • Known vulnerabilities patched rather than accumulating
  • Backups that have been proven to restore
  • A named person to contact when something breaks
What it costs

What actually moves the price.

  • Traffic and infrastructure requirements
  • How critical uptime is to the business
  • How much monthly development time is included
  • Whether we built the system or are inheriting it

We quote a fixed shape of work with a price and a date on it, rather than an hourly rate that grows.

Who buys this

Sectors that need this most.

Questions we get asked

Straight answers.

Can you support a site you did not build?

Usually. We would start with an audit of the code, dependencies and deployment, and tell you honestly what state it is in before committing to a monthly arrangement.

What is the response time?

It depends on what the business needs. A brochure site and a system your operation runs on deserve different commitments, and we would rather agree a realistic one than a heroic one.

Are we tied into a contract?

Monthly, with your data and code exportable at any point. Lock-in is not a business model we are interested in.

Does support include changes?

A set amount of development time each month is included, and anything larger is quoted separately so a big piece of work does not quietly consume your support hours.

Tell us what you need building.

A couple of lines is enough to start. You will get a straight answer on scope, cost and timeline within one working day.