Software
Cloud and DevOps
The part that decides whether your software is still running on a Sunday, and whether anyone finds out before your customers do.
What this is
The work, described plainly
Infrastructure work is invisible when it is right. It becomes visible during an outage, a failed deployment, or the afternoon someone discovers the backups have not run since March.
We favour the simplest infrastructure that meets the requirement. A single well-configured server with monitoring and tested backups beats a cluster nobody on your team can debug, and it costs a fraction as much.
Deployment should be boring: automated checks, a repeatable path to production, and a way back. If shipping is frightening, it happens rarely, and rare deployments are large ones — which is what makes them frightening.
What you get
What is actually handed over
Concrete deliverables, not phases on a timeline.
Infrastructure setup
Sized to your actual load, with the reasoning documented so the next person understands the choices.
CI/CD pipeline
Typecheck, lint, tests, and build on every change, with a deployment that anyone on the team can run.
Monitoring and alerting
Uptime, errors, and performance, with alerts that go to a person rather than a dashboard nobody opens.
Backup and recovery
Automated, and — the part usually missing — actually restored once to prove it works.
Is this you
Signals this is the right fit
- Deployment is manual and only one person is confident doing it.
- You find out about outages from customers.
- Backups exist but have never been restored.
- Cloud spend is rising and nobody can explain why.
Typical stack
Chosen per project against your constraints, not applied by default. This is what the work usually involves.
- Docker
- GitHub Actions
- Nginx and Caddy
- Managed Node and VPS hosting
- Uptime and error monitoring
FAQ
Questions people actually ask
Do we need Kubernetes?
Almost certainly not. It solves problems of scale and team size that most businesses do not have, and it adds an operational burden that outlasts the project. We will recommend it only if your load genuinely calls for it.
Can you work with our existing hosting?
Yes, including shared and managed hosting with real constraints. We would rather work inside your limits than propose a migration you did not ask for.
What does handover look like?
Documented infrastructure, credentials transferred properly, and a runbook for the failures we can anticipate. You should not need us on retainer to keep it up.
Start here
Tell us what is slow, manual, or breaking.
Answer a few questions and get a written brief back — scope, proposed architecture, and what it would take to build.