Hosting · Support

Ten brands, ten websites, one team looking after them.

A group of scientific instrument manufacturers whose brands each need their own website — and whose estate needs to be patched, monitored and kept online as one thing rather than ten.

Scientific Instruments Managed hosting Retained support Inherited sites
estate / productionretained
HostingAll ten sites, one platform
Managed
Monitoring & backupsAcross the whole estate
Managed
MaintenancePatching and platform updates
Ongoing
DevelopmentSites we built and sites we did not
Ongoing
The engagementcurrent
10SITES IN THE GROUP
All 10HOSTED BY US
SeveralBUILT BY US
OngoingENGAGEMENT
How it is arranged

Separate on top, shared underneath.

scientific-instruments-group / architecture diagram
Ten sites, one thing underneath themTen brand sitesseveral built by usthe rest inheritedOne hosting platformmonitored & backed upOne retained teampatching, fixes, changescontinuous — monitoring, patching, maintenance
The inverse of a consolidation. Ten brands stay ten separate sites, because each has its own products and its own audience. What gets unified is everything underneath them — one platform to patch, monitor and back up, and one team who knows all ten rather than knowledge scattered per site. Scroll the diagram sideways to see all of it.

The challenge

A group of scientific instrument manufacturers, each trading under its own brand with its own products, its own specialist audience and its own website. Ten of them.

Consolidating ten brands into one site was never the aim — the brands are the point, and the buyers of one are not the buyers of another. The problem is the other end of it. Ten websites built at different times, several by us and the rest inherited, is ten platforms to keep patched, ten sets of backups to actually be running, and ten things that can go quietly out of date.

That is usually where estates like this come apart: not in a dramatic failure, but in a site nobody has updated in two years because it was never clear whose job it was.

What we do

  • Host all ten sites on infrastructure we manage, rather than ten arrangements with different providers.
  • Monitoring, backups and certificate renewal running across the whole estate.
  • Platform and security patching, applied as maintenance rather than when something breaks.
  • Development and changes on every site — including the ones we did not originally build.
  • One team with the whole estate in view, so knowledge is not stranded per site.

The outcome

One supplierHosting and development are the same conversation.
Nothing in betweenNo gap for a problem to be passed into.
Brands stay separateEach site keeps its own identity and audience.

Why it is worth saying

Most case studies describe a build and stop at launch. The majority of a website's life is what happens afterwards, and taking on sites somebody else wrote is a different skill to writing them — you inherit decisions you would not have made, and the job is to keep them running regardless.

Ready to build?

Have an estate nobody is quite looking after?

Sites built by different people at different times, where it is no longer clear who patches what. We take those on — starting with a review of what is actually there, so you know what you have before anybody commits to looking after it.