Monthly retainers for website support vary enormously. Some cover nothing more than keeping a server running. Others provide genuine ongoing stewardship of a business-critical platform. If you are paying a monthly fee for ExpressionEngine or Craft CMS support, understanding what a well-structured retainer looks like will help you assess whether you are getting good value, or just paying for a contact you rarely use.
Platform maintenance, not just hosting
A retainer should cover the platform itself, not just the server it runs on. For ExpressionEngine and Craft CMS, that means keeping the core installation up to date, monitoring addon and plugin compatibility, and applying security patches promptly. Hosting is a commodity. Platform expertise is not. The two should not be conflated in what you are paying for.
Security monitoring and incident response
Business-critical websites attract automated attacks constantly. A properly structured retainer includes monitoring for unusual activity, prompt response when something is flagged, and a clear process for what happens if there is an incident outside normal business hours. If you do not know what your developer's incident response process looks like, that is worth asking about directly.
Proactive reviews, not just reactive fixes
The difference between a retainer that protects your business and one that just fixes things when they break is proactive review. A good support arrangement includes periodic checks on PHP compatibility, addon health, server performance, and any upcoming changes that could affect your site. You should not be the one discovering problems first.
Clear scope and a known escalation path
A retainer should have a defined scope: what is included, what falls outside it, and what happens when out-of-scope work is needed. Vague arrangements tend to create friction when something significant needs doing. The best retainers also include a clear escalation path, so that when something serious happens you are not trying to reach someone through a generic support inbox at the worst possible moment.
What to ask your current developer
If you have an existing support arrangement, the questions worth asking are: what specifically is covered, what is the response time commitment, when did you last proactively review the site, and what would happen if something went wrong tonight? The answers will tell you quickly whether you have a genuine support arrangement or just an informal understanding that exists on paper.