1. Home
  2. Enterprise care
  3. Sitecore support

Sitecore support for sites your previous partner left behind

We support Sitecore XP and XM sites on a monthly retainer: security hotfixes, version upgrades, component and template changes, and performance work. When the time comes, we plan the move to XM Cloud or a simpler CMS.

Example monthly report · illustrativeAll systems normal
99.98%uptime · 12 mo
42patches this month
11 minavg. first response
5systems looked after
RESPONSE TIME · LAST 30 DAYSSLA 30 MIN
  • corporate-site.comIIS 10 · .NET Framework 4.899.99%
  • investors.corporate-site.comSitecore 10.3 · Azure100%
  • careers portalJava 17 · Tomcat · Oracle99.97%
  • intranetSharePoint 2019 · on-premise99.95%
  • partner API.NET 10 · SQL Server99.99%
Why it matters now

Sitecore sites tend to outlive the partner that built them. Years later the company is left with a powerful platform, a long list of custom components, licence renewals and security bulletins that someone needs to act on.

Sitecore publishes mainstream and extended support dates for every XP and XM version, along with security bulletins and hotfixes. Our audit maps your version, modules and customisations against them, then we keep the site patched and agree whether to upgrade in place, move to XM Cloud or move to another CMS altogether.

Signs you need this

  • Your Sitecore version is out of mainstream support
  • Security bulletins are not being reviewed
  • Editors avoid publishing because it is slow
  • Licence renewal is coming and you are unsure what to do
Request an audit →

What we do every month

01

Security hotfixes

Sitecore security bulletins reviewed as they are published and hotfixes applied within your SLA.

02

Version upgrades

Planned upgrades to supported XP or XM versions, rehearsed on a copy of production.

03

Component changes

Renderings, templates and workflows changed from a monthly bank of hours.

04

Performance

Caching, publishing and indexing tuned so editors and visitors both get a fast site.

05

Infrastructure

Solr, SQL Server and content delivery servers monitored and patched, on-premise or in Azure.

06

Next-platform plan

An honest comparison of upgrading, XM Cloud and moving to another CMS for your editors and budget.

Patching cadence

Security bulletins and hotfixesReviewed on publication, applied within your SLA
Windows, SQL Server and Solr updatesMonthly
Licence and module reviewAnnually, before renewal
Upgrade rehearsalBefore every version upgrade, on a copy of production

Security posture

  • Named-user access only, through your VPN, jump host or SSO
  • Credentials stored in a vault, never in email or tickets
  • Every change logged against a ticket, with a rollback step
  • NDA and data processing agreement before any access
  • Findings from your penetration tests fixed and documented

Service levels

Written into the contract. Mix tiers across your estate according to how critical each system is.

Example service levels by support tier
EssentialBusinessMission-critical
Critical (site down)4 hours1 hour15 minutes
High (major feature broken)Next business day4 hours1 hour
Normal3 business days1 business day4 hours
Cover hoursMon–Fri, business hours7am–10pm, 7 days24/7/365
Uptime target99.5%99.9%99.95%
Named engineers12Dedicated team

How the takeover works

  1. Weeks 1–2

    Audit

    Read-only access under NDA. Versions, risks, costs and a quote.

  2. Weeks 3–4

    Knowledge transfer

    Runbooks, credentials vault and handover sessions with your current team or vendor.

  3. Month 2

    Stabilise

    Urgent patches, monitoring and backups in place before anything else changes.

  4. Ongoing

    Run & improve

    SLA-backed support, planned upgrades and a monthly report.

Free estate audit · 2 weeks

Get a written report on your Sitecore estate.

Read-only access, under NDA. Versions, end-of-support dates, security findings and a monthly quote. Keep the report either way.

How many sites and apps?
Main technology
Maintained today by

We reply with an NDA and an access checklist.

Sitecore support: questions, answered

Are you a Sitecore partner?
We say so only where it is true; ask us for our current status. Partner status is not required to maintain or upgrade a Sitecore site, but we are always clear about it.
Should we move to XM Cloud?
It depends on how your editors work and how much custom code you have. We compare upgrading in place, XM Cloud and another CMS in the audit, with effort and running costs for each.
Can you work alongside our marketing agency?
Yes. We often look after the platform while an agency handles campaigns and content.