One person holds the keys
The developer or contractor who set it up has moved on, and the passwords, the deployment steps and the reasons behind the setup went with them.
Infrastructure support
Cloud Infrastructure Support for UK Businesses
The servers, databases and cloud accounts behind your software kept patched, monitored, backed up and sensibly priced — in UK business hours, including infrastructure someone else built.
- Alerts routed to engineers who know your setup
- Runbooks written down, not held in one head
- Inherited infrastructure taken on after an audit
Why infrastructure becomes a risk
Infrastructure that nobody is really looking after.
Most cloud problems are not dramatic failures. They are small jobs left undone — an unpatched server, a backup nobody has restored, a bill nobody reads — until the day they matter.
What routine support gives you
The same checks every month, whether or not anything is on fire:
- Alerts that reach someone who knows your setup
- Patches and upgrades applied on a schedule
- Backups proven by test restores
- Spend reviewed against what you actually use
- Runbooks so any engineer can handle an incident
Backups nobody has restored
Backups run every night, but nobody has tried restoring one — so the first real test would happen during an outage, with customers waiting.
Patching that slipped
Operating systems, databases and runtimes drift past end of support, and every postponed upgrade makes the next one bigger and riskier.
A bill that only goes up
Oversized servers, forgotten test environments and orphaned storage add to the monthly invoice, and nobody has time to work out why.
What we look after
Infrastructure support, done as a routine.
A monthly retainer covering an agreed scope. We work inside your cloud accounts, under your ownership, and document everything we touch.
Monitoring and alerting
Uptime checks, error rates, server and database metrics, with alerts tuned until they mean something and routed to the right person.
Learn more
Patching and upgrades
Operating system, runtime, database and framework upgrades, tested on staging first and rolled out in agreed maintenance windows.
Learn more
Backup checks and test restores
Backup coverage audited, retention set to your needs and restores rehearsed on a schedule, so recovery time is known rather than hoped for.
Learn more
Capacity and cost reviews
Usage and spend reviewed regularly: servers rightsized, idle resources removed, and reserved capacity bought only where usage is steady.
Learn more
Security hardening
Least-privilege access, MFA on every admin account, closed ports, encrypted storage and logs you could actually use in an investigation.
Learn more
Incident response and runbooks
Outages investigated and service restored in UK business hours, a written cause and fix afterwards, and runbooks updated so the next incident is quicker to resolve.
Learn more
How we work
How infrastructure support starts and runs.
Support begins with an onboarding audit rather than a signature and a hope. After that it becomes a routine: the same checks every month, and a clear path when something breaks.
- 01
Discovery
An onboarding audit of your cloud accounts: what is running, who has access, how it is deployed, what it costs and where the single points of failure are.
An infrastructure audit and risk list
- 02
Strategy
We agree the scope, response targets for each severity, maintenance windows, hours of cover and a fixed monthly fee, then rank the risks to fix first.
A written support scope
- 03
UX & architecture
We document the architecture as it actually is, set up access properly — named accounts, MFA, no shared passwords — and put monitoring in place.
Architecture diagram and monitoring live
- 04
Development
Fixes from the audit worked through in priority order alongside the routine work, with every change made through version control rather than by hand.
Highest risks closed first
- 05
Testing
Upgrades tried on staging first, backups restored into a test environment on a schedule, and alerts triggered deliberately to prove they reach someone.
Tested restores and verified alerts
- 06
Launch
Production changes made in agreed maintenance windows with a rollback plan, and the runbook updated whenever something new is learned.
Planned changes, not surprises
- 07
Optimisation & support
A monthly report on incidents, patches, backups, spend and open risks, and a regular review of what to improve next.
A monthly report and review
Technology
What we support day to day.
Mostly AWS, plus the servers, databases and tooling that usually sit around it — including environments on other providers where your systems already run.
Platforms
AWSAzure and Google Cloud (existing estates)VercelVirtual private servers
Servers and runtime
LinuxNGINXDockerKubernetes
Databases
PostgreSQLMySQLRedisPoint-in-time recovery
Monitoring
Uptime and health checksMetrics and log aggregationError trackingAlert routing
Change control
GitHub ActionsInfrastructure as codeStaging environmentsMaintenance windows
Access and security
Named accounts and MFALeast-privilege rolesSecrets managementAudit logging
Standard cover is UK business hours. Extended or on-call cover for planned events — a launch, a migration, a peak trading weekend — is agreed and priced in advance, never assumed.
Use cases
When teams bring us their infrastructure.
The situations that usually start a support engagement — and what support looks like in each.
Taking over an orphaned setup
We audit the accounts, recover access, document how everything is deployed and bring it under routine support before changing anything else.
Support alongside a product team
Your developers ship features; we keep the platform patched, monitored and sized, so infrastructure work stops interrupting the roadmap.
Ready for peak trading
Capacity checks, load tests and extended cover agreed ahead of Black Friday or a major campaign, with a plan for what happens if traffic exceeds it.
Evidence ready for audits
Patch records, access reviews, backup test logs and incident write-ups kept as routine, ready when an auditor, insurer or customer asks.
End-of-life server upgrades
A server on an unsupported operating system or PHP version upgraded — or rebuilt in containers — with a tested rollback rather than an overnight gamble.
A second line for application hosting
Your IT provider handles laptops, email and the office network; we look after the application servers, databases and cloud accounts outside their usual remit.
Relevant work
Products we have designed and built.
A selection of client projects related to this work. Each case study covers the brief, the approach and the stack.
All case studiesIoT · Smart Home
Connect Home
Smart-home dashboard for device control, schedules and energy use.
ReactNode.jsMQTTAWS IoT
Read the case studyLegal · SaaS
CO-LAW Group
Client intake, risk checks and document workflows for a boutique law firm.
Next.jsPostgreSQLAWSStripe
Read the case studyFinance · Mobile
Equity Bank
Digital banking app: accounts, bill payments, loans and investments.
React NativeNode.jsPostgreSQLAWS
Read the case studyWhy Techsleight
What working with us is actually like.
No inflated numbers — just how we run projects, and what you can hold us to.
Product engineering, not ticket-taking
We ask what the software is for before we estimate it — and we will tell you when something should not be built, or should be bought instead.
AI where it earns its place
LLM features, retrieval and automation built with evaluation, guardrails and cost controls, and plain software where that is the better answer.
Full-stack under one roof
Design, frontend, backend, mobile, cloud and QA in one team, so nothing falls between suppliers.
UK-focused delivery
UK business hours, estimates in pounds, and a contract with a UK company. Our engineers are based in the UK and India.
Flexible engagement
A fixed-scope project, dedicated developers or a monthly retainer — and you can move between them as the work changes.
You own everything
Code, IP, cloud accounts and documentation are yours from day one. We sign an NDA before discovery if you need one.
Support after launch
We stay on for fixes, upgrades and new features, or hand over cleanly to your in-house team with the documentation to match.
FAQs
Questions we get asked.
Straight answers on scope, cost, timelines and how we work. If yours is not here, ask us directly.
What does cloud infrastructure support include?
Monitoring and alerting, patching and upgrades, backup checks and test restores, security hardening, capacity and cost reviews, incident response and documentation. The exact scope is written down per engagement, so you know what is covered and what would be billed separately.
Do you offer out-of-hours cover?
Our standard cover is UK business hours. Extended hours or on-call cover can be agreed for specific periods — a launch, a migration, peak trading — and priced in advance. We do not run a round-the-clock service desk, and we would rather say so than overpromise.
Can you support infrastructure you did not build?
Yes. We start with an onboarding audit covering access, architecture, deployment, backups, costs and risks. You get a written report and a ranked list of issues before we take responsibility for anything, so both sides know exactly what is being inherited.
How much does infrastructure support cost?
A fixed monthly fee based on the size of the environment, the response targets you need and the hours of cover. The onboarding audit is quoted separately up front. Your cloud provider bills stay in your name and are paid by you directly.
How quickly do you respond to incidents?
Response targets are agreed per engagement and depend on severity: a production outage is handled very differently from a slow report. They are written into the support agreement, together with how to raise an incident and who you will hear from.
What do you need from us to get started?
Admin access to the cloud accounts, or someone who can grant it; any documentation that exists; and an hour with whoever knows the system well. If nobody really knows it any more, that is exactly what the onboarding audit is for.
Which cloud providers do you support?
Mainly AWS, our primary platform and where our experience is deepest. We also support existing environments on Azure, Google Cloud, Vercel and virtual private servers, where that is where your systems already live.
How do you handle urgent security patches?
Routine patches go in on a schedule during agreed maintenance windows, after testing on staging. Critical security updates are assessed as they are announced and applied sooner where the risk justifies it, with you told before and after.
Can you help us meet UK GDPR security expectations?
We put the technical measures in place and keep the evidence: encryption, access control, logging, backups and tested recovery. If a breach happens, we help gather the facts quickly, because a reportable breach should be notified to the ICO within 72 hours of becoming aware of it. Compliance decisions stay with you.
How is this different from application maintenance?
Infrastructure support looks after what your software runs on: servers, databases, networks and cloud accounts. Application maintenance looks after the code itself: bugs, dependency updates and small features. The two are often combined in one retainer.
Start a project
Not sure what is running in your cloud account?
Tell us what you run and who looks after it now. We will explain how an onboarding audit works and what ongoing support would cover.
What happens next
- 1A senior engineer reads your brief within one working day, and replies with questions or a first view.
- 2A 30-minute call to understand the goal, constraints and what good looks like — no sales script.
- 3A written proposal with scope, milestones, team and a GBP estimate you can take to your board.
Techsleight Labs is a trading name of Krapton IT Consultancy.
Explore