Skip to main content
Kodvana

Cloud hosting and support, handled for you

Software does not stay healthy on its own. Dependencies age, certificates expire, traffic patterns change and small problems become outages. Maintenance is the least visible work we do and often the most valuable.

Cloud engineer checking an uptime and deployment monitoring dashboard across two screens
Typical timeline
Set up in 2 to 3 weeks, then monthly
Usually built with
Vercel, AWS, Azure, Cloudflare
You own
Code, data and accounts, in your name
Overview

About cloud hosting & support

Plenty of businesses have a website or an internal system that works, and nobody responsible for it. It runs until it does not, and then there is a scramble to find whoever built it. A maintenance arrangement replaces that with monitoring, routine updates, verified backups and a defined response time. It also covers the small changes that otherwise wait months because raising them feels like too much trouble.

Illustrative interface, not a client system
Is this for you

Who needs ongoing support

Usually a good fit for

  • Businesses with a live site or system and no in-house technical person
  • Companies whose original developer is no longer available
  • Organisations running software that has not been updated in a long time
  • Businesses that need a known response time when something stops working
  • Teams that want small changes handled without a new project each time

Signs it is time

  • Nobody knows whether backups exist or whether they would restore
  • Dependencies have not been updated for years and carry known vulnerabilities
  • An outage is discovered by a customer rather than by monitoring
  • Small content or layout changes wait for months because there is nobody to ask
  • An SSL certificate or domain renewal is missed and the site goes down
What's covered

What's covered

01

Proactive monitoring

Uptime, error rate and performance monitoring with alerts routed to us, so problems are usually addressed before you notice them.

02

Security and dependency updates

Regular patching of frameworks and libraries, tested on staging before being applied to the live system.

03

Backup management

Automated backups on a defined schedule, with periodic restore tests to prove they work.

04

Content and small changes

A monthly allowance for text updates, new pages, image changes and minor layout adjustments.

05

Issue response

A defined channel and response time for problems, with severity levels agreed in advance.

06

Cloud hosting and DevOps

Hosting on AWS, Azure or Vercel set up in your name, with automated deployments, staging environments and cost reviews.

07

Takeover of existing systems

Auditing, documenting and taking responsibility for a site or application originally built by someone else.

Every plan

Included in every support plan

  • Uptime monitoring with alerting
  • Error tracking so exceptions are visible rather than silent
  • Monthly dependency and security updates applied on staging first
  • Automated backups with periodic verified restores
  • SSL certificate and domain renewal tracking
  • Performance review with recommendations
  • A monthly allowance of small change requests
  • Defined response times by issue severity
  • A monthly report of what was done and what needs attention
  • Documentation kept current as changes are made

Not included: hosting, domains, email, licences and other third-party services. These are billed to you directly by the provider at cost, stay in your name, and are estimated in the proposal.

Typical response times

Agreed per client and written into your arrangement.

  • DownThe site or system is unavailableSame business day
  • SignificantA key feature is broken or badly slowedNext business day
  • RoutineSmall changes and content updatesWithin a few business days

Tools we use

Final choice made during scoping.

Hosting
VercelAWSAzureCloudflare
Monitoring & updates
SentryGitHub Dependabot
Platforms we look after
Next.js and ReactNode.jsWordPressPHP
Getting started

How support gets set up

Typical timeline: set up in 2 to 3 weeks, then monthly, depending on scope and how quickly access and content arrive.

  1. 013-5 days

    Audit and handover

    For systems we did not build: a full review of code, hosting, dependencies, backups and security, with findings written up.

  2. 021 week

    Stabilise

    Immediate risks are fixed first: backups configured, critical vulnerabilities patched, monitoring put in place.

  3. 032-3 days

    Set up monitoring and access

    Alerting configured, staging environment created, access and credentials organised properly.

  4. 041-2 days

    Agree the arrangement

    Response times, severity definitions, the change allowance and the escalation path, all written down.

  5. 05Ongoing

    Monthly cycle

    Updates applied, backups verified, performance reviewed, change requests handled and a summary sent.

Need someone to look after your site or system?

Tell us what you run today. You get a written proposal with a fixed monthly fee, with no obligation.

How our fixed quotes and payments work →
Get a fixed monthly support quote
Business benefits

What having someone responsible changes

What tends to happen, not a guarantee.

  1. 1

    Problems found before customers find them

    Monitoring turns a customer complaint into an alert that was already being handled.

  2. 2

    A recovery path that has been tested

    Backups only count if a restore has actually been performed. We test them.

  3. 3

    Small changes stop piling up

    A monthly allowance means minor improvements happen instead of waiting for a project.

  4. 4

    Security you can evidence

    Regular patching and a written record matter when a client or auditor asks how the system is maintained.

  5. 5

    Predictable cost

    A fixed monthly fee instead of unpredictable emergency work at the worst possible time.

Questions

Cloud hosting & support FAQs

Not covered here?

Ask us directly
Can you maintain a website you did not build?

Usually yes. We start with an audit covering code quality, hosting, dependencies, backups and security, and give you a written report. Occasionally a system is in a state where maintenance is not sensible without remedial work first, and we will say so with a clear estimate rather than quietly taking on something we cannot support.

What response times do you offer?

Response times are agreed per client and written into the arrangement. A typical structure is same business day for a site that is down, next business day for a significant issue, and within a few business days for routine change requests. We do not advertise round-the-clock support because a team should not promise what it cannot consistently deliver.

What counts as a small change?

Text and image updates, adding a page using existing layouts, updating a team or product listing, changing form recipients, minor styling adjustments. Anything that needs new design work or new functionality is quoted separately as a small project. The boundary is written into the arrangement so it is not a monthly negotiation.

Is there a minimum contract period?

No lock-in. Maintenance is monthly with one month of notice on either side. If you take the system elsewhere, we hand over documentation, credentials and current access without obstruction.

Do you cover hosting costs?

No. Hosting, domains, email and third-party services are billed to you directly by those providers and remain in your name. We manage and monitor them on your behalf, which keeps you in control of your own infrastructure.

Start here

Talk to us about cloud hosting & support

Tell us what you run, where it is hosted and what worries you about it. We will come back with what support involves, the response times we can commit to and a fixed monthly fee.

The first conversation is free, with no obligation.