Cloud deployment and ongoing support

We take software from launch into reliable daily operation. Cloud architecture, automated deployments, monitoring, maintenance, and the product improvements that follow real user feedback.

For our own builds this is Phase 3 and it is part of the project rather than an upsell. See how we deliver. We also do it for software we did not build, which is the more common reason people arrive on this page.

When this is the right choice

When software is live and keeping it running is nobody's actual job. When the developer who built it has moved on and releases have started to feel risky. When something breaks and the first question is who to call. When you are paying for cloud infrastructure nobody has looked at in a year. Or when the product has stopped improving because there is no capacity to improve it.

What we do

Cloud environments designed to be understood rather than inherited. Automated, repeatable deployments so a release is routine instead of an event. Monitoring and backups, and someone who notices before your customers do. Dependency maintenance, security patching and defect fixes. Performance work. And continuing product improvement on agreed monthly hours, with scope set together each month.

Unused hours go into optimisation or a head start on what is next. They are never lost and never pocketed.

Software we did not build

Most of the support work we take on is somebody else's code. That is normal and we are comfortable with it.

We will be straight about one thing though. Taking over an unfamiliar system without reading it properly first is how support arrangements go wrong for both sides. So for anything substantial we start by understanding what is actually there, and if the system turns out to be carrying more risk than anyone realised, you will hear that from us before you sign a support agreement rather than six months into one. That is what a code audit is for.

When something else fits better

If the software does not exist yet, this is not your starting point. A build comes first, and support is included in it.

If you have inherited something and genuinely do not know what is in it, start with a code audit instead. It costs less, it takes less time, and it tells you whether the right move is to support this system, rebuild it, or retire it. Committing to a monthly support arrangement before you know that is how people end up paying to maintain something that should have been replaced.

How we already work

This is not an occasional engagement we can point at three examples of. We manage the cloud environments for our clients as a matter of course, and most of them stay with us on a monthly retainer after launch. It is how the business runs rather than a product we sell now and then.

That is worth saying plainly, because it answers the question behind the question. When you hand software to a development partner, the risk you are taking is that they build it, invoice it, and move on. We do not have a separate support department to hand you over to. The team that built your product is the team that keeps it running, and the reason we can say that with confidence is that it is already true of almost every client we have.