VPS or server fleet
Choose an environment based on workload, data and reliability needs. Physical servers, virtualisation or a VPS — not complexity for its own sake.
02 / Infrastructure & DevOps
An application is more than its code. I build a suitable server environment and a considered way to deploy, manage and recover it.
From change to running service
In version control
Tests and review
Into the agreed environment
Monitoring and recovery
Choose an environment based on workload, data and reliability needs. Physical servers, virtualisation or a VPS — not complexity for its own sake.
Design container environments and version-controlled deployment where they provide real value. Account for environments, permissions and dependencies.
Networks, access controls, service monitoring and alerts belong in the design, not on a list of last-minute additions.
Agree on what needs protecting and how recovery should work. Alongside checking backups, test restoration of the agreed data.
I start with the need, not with Kubernetes. When a simpler solution does the job better, I build the simpler solution.
A clear handover
Scope, checks, documentation and handover are agreed before implementation. Ongoing maintenance, support and response times are a separate agreement, not an open-ended promise.
The process
Map the problem, people and workflow. Before choosing technology, we establish what the system needs to solve.
Define the logic, data, interface and infrastructure. Agree on the scope of work.
Develop the solution in stages. Test workflows, integrations and operation.
Put the system into use, deliver the agreed documentation and define ongoing support.
Need a new application as well as infrastructure?
Custom systemsStart with the problem
Tell me what is not working, or what you want to build. We’ll work out which software and infrastructure would actually solve it.