Backup and update retainers
Fewer updates to chase, and a clear choice about who looks after the rest
What they typically handle
Typical retainers cover scheduled backups, WordPress core, theme and plugin updates, uptime monitoring, and a set amount of content edits each month.
WordPress recommends backing up a site before updating it, which is one reason update work is often bundled with backups.[1]
On a rebuilt site
Checkpoints you can roll back to
Replit creates checkpoints of the project as changes are made, including files and, where selected, database contents, so a change that goes wrong can be rolled back.
Changes reviewed before they go live
Edits are previewed in the workspace and published deliberately, so the public site does not change halfway through an update.
Packages updated on purpose
There is no plugin list updating itself. Packages are updated when needed, checked in preview, and published.
A clear choice of who does it
Client-managed: you make changes through Replit Agent and pay your own Replit usage. Managed by us: you send requests and we handle them within the agreed scope.
What we ask you first
- What does your current retainer include, and what do you actually use?
- How many content changes do you make in a typical month?
- Would you rather make changes yourself or send them to someone?
- Who should be contacted if the site has a problem?
Questions
Common questions
Do I still need a retainer?
No. Many owners make their own changes through Replit Agent. If you would rather hand them off, we manage the site under a simple agreement.
Are checkpoints the same as off-site backups?
Checkpoints let you roll the whole project back within Replit. For an off-site copy as well, the code can be kept in a GitHub repository in your name; we set that up on request.
Sources
- [1]Updating WordPress · WordPress.org Documentation · Checked 2026-10-26
- [2]Checkpoints and Rollbacks · Replit Docs · Checked 2026-10-26
Want to know how this would apply to your site?
Ask about your current setup