Website Hosting & Support

Your website,
in good hands.

Managed WordPress hosting, maintenance and technical support, with clear arrangements for routine care and for the day your website needs attention. You’ll know who is responsible for what, what’s being looked after and exactly how to raise a problem.
Talk about your website support
See what your support arrangement can cover

What looking after your website involves.

Three situations cover almost everything. Your agreement says what happens in each.

Routine care

Hosting, updates to the supported software, monitoring and backups suited to your site.
The agreement sets
Who does each job, how often or how widely, and what’s excluded.

Something goes wrong

How you report it, how it’s assessed and who coordinates the response.
The agreement sets
The support hours, how urgency is judged, how it escalates and who’s responsible for recovery.

Something needs changing

How a request is assessed, and whether it’s support or a separate piece of work.
The agreement sets
Any included allowance, who approves extra cost and who does the development.
A broken form may be a maintenance fix. Changing how the form works is design or conversion work. Repairing what happens to the enquiry afterwards may be integration work. The agreement says which is which, so nothing falls between them.
WordPress Development
Custom Digital Platforms

Hosting suited to the website you depend on.

A business website needs a suitable environment, infrastructure that someone maintains and a defined route for infrastructure problems. Managed hosting provides that, so the site isn’t sitting on a server nobody is watching.
Where it applies, we host supported WordPress sites with Pagely, a managed WordPress host built on Amazon Web Services.

Three parties, three jobs

You

look after the business decisions: approving changes, keeping your contacts current and telling us what matters most on the site.

Redfox

looks after your website on that infrastructure: the agreed updates, checks, backups oversight and support, and the conversation with the host when it’s their side.

The host

looks after the infrastructure: the servers, the network and the platform the site runs on.
A host that watches its infrastructure around the clock isn’t the same as someone at Redfox being on call. Your agreement says exactly which you have.

Keep the everyday work under control.

The recurring work is unglamorous and it matters: relevant software updates, checks, oversight of backups and the agreed monitoring.
Updates aren’t a button to press and forget. An update can break a plugin’s compatibility or a function the business relies on. So the arrangement accounts for what gets checked afterwards and how we respond if a change causes a problem, at a level that suits your site.

Reachable isn’t the same as working.

Knowing the site loads is different from knowing the enquiry form, the checkout or the login works. We only say we check a function when we do, and your agreement names which ones.
Where reporting is part of your arrangement, it shows three things:

What was done

What needs your decision

Anything still open

Know how to get help when something goes wrong.

In the moment, five things matter:

01

Where to report it

02

What information helps

03

How urgency is judged

04

Who keeps you informed

05

When another provider has to be brought in

Your arrangement answers each one before you ever need it.

A response isn’t a resolution.

An acknowledgement tells you we have it. The fix depends on the fault, the backups available, third-party services and whether the work sits inside the agreed scope. Any response commitment we make is stated precisely. It’s never dressed up as a guaranteed fix time.

Say a site stops loading after an update. Four decisions follow:

  • Which component caused it
  • Which way back is safest
  • Whether to restore or repair
  • How to confirm the important functions work again
That’s an illustration of the questions, not a promised procedure.

A backup needs a usable recovery plan.

Storing a copy of your website isn’t the same as being able to bring it back.

A recovery plan answers four questions.
01

What’s backed up?

02

How long are copies kept?

03

Who can authorise a restore?

04

And who checks the restored site?

One more thing worth knowing

A restore takes the site back to an earlier moment. If yours takes orders, enquiries or bookings, the plan has to account for what came in after that copy was made. Nobody honest promises that nothing will ever be lost. A good plan tells you what would be, and how it’s handled.

Already have a website? Start with its current condition.

Before we take responsibility for a site, we review it:
  • The site itself
  • The hosting
  • Administrator access
  • Software dependencies
  • Licences
  • Any significant custom functionality

You get a proposed support scope and a list of anything that needs attention first. Some sites are ready to onboard. Others need remedial development, an unsupported component replaced or a different conversation about the application behind them. We don’t take on every site sight unseen.

If the site is moving host, that’s a planned piece of work with agreed responsibilities and checks, not a switch we flip. Your domain registration, DNS and business email may sit outside the hosting arrangement. We’ll identify them, and moving host doesn’t quietly make them ours.

May sit outside the hosting arrangement

Domain registration

DNS

Business email

Care you can see.

Illustrative, not a client’s. It shows the three things a record should make clear: what was done, its status and any decision you need to make.
What was done
Software updates applied, key pages and the enquiry form checked.
Status
Done
Your decision
None needed
What was done
Contact form plugin no longer supported by its developer.
Status
Open
Your decision

Approve the replacement. Quote attached.

What was done
Backup checked, test restore completed.
Status
Done
Your decision
None needed

Who’s looking after your website right now?

If the answer takes a while, that’s a good reason to talk. Share the website address, the current arrangement and what you need help with. You don’t need a technical diagnosis.
Talk about your website support
Please don’t send passwords or administrator logins through the enquiry form. If a review goes ahead, we’ll arrange access properly.

You can have hosting and support without any wider engagement. Where the website is one part of a bigger program, it can sit alongside a Growth Partnership as its own defined service.