Problems found first
Monitoring and alerts, so we often fix issues before you notice them.
Service 15 of 15
Maintenance & support
Monitoring, fixes and updates that keep your software safe and running.
- Typical start
- 1–2 weeks
- Pricing
- Monthly plan
- Team
- Support engineer + lead
Our 3 promises
Your software. Our goal.
Three promises we make on every support plan.
Always up to date
Security patches and updates on a regular, planned schedule.
Clear and honest
Monthly reports on uptime, fixes and what is coming next.
Tech stack
The stack behind your maintenance & support
Proven, well-supported tools at every layer. Picked for your product, never for our habits.
- MonitoringDatadog
- MonitoringMost requestedSentry
- MonitoringGrafana
- MonitoringUptimeRobot
- CloudAzure
- CloudMost requestedAWS
- CloudGoogle Cloud
- CloudVercel
- SupportMost requestedJira
- SecuritySnyk
- SecurityDependabot
- SecurityPatching
- SupportSlack
- SupportEmail
- SupportStatus pages
- BackupsDaily backups
- BackupsRestore tests
- BackupsDisaster recovery
What’s included
What you get
Everything a live product needs to stay safe, fast and up to date.
01StartTakeover review
We review the code, hosting and risks before we take over.
Read more +Show less −
A takeover review is a check of your code, hosting and risks before we take over support, so we know exactly what we are looking after. You get a code review, a ranked risk list and a support plan with a monthly price. It usually takes 1–2 weeks.
What you get
- Review of code quality, structure and outdated libraries
- Review of hosting, access, backups and security settings
- Ranked risk list with recommended fixes
- Documentation of how the system is set up
- Support plan with response times and monthly price
How it works
- You give us access to code, hosting and accounts
- We review the code, infrastructure and current issues
- We share the risk list and recommended fixes
- You approve the support plan and start date
Good to know: Gather all logins and access details before the review starts, as missing access is the most common cause of delay.
02RunMonitoring
Uptime, error and speed monitoring with alerts.
Read more +Show less −
Monitoring watches your software around the clock and alerts us when it goes down, slows down or starts throwing errors. We use tools such as Sentry, Datadog, Grafana and UptimeRobot, with 24/7 alerts. Most problems are spotted and investigated before your users report them.
What you get
- Uptime checks on your website, app and APIs
- Error tracking with details needed for quick fixes
- Speed monitoring for key pages and endpoints
- 24/7 alerts to our support team
- Optional public status page for your users
How it works
- We set up checks and error tracking in week one
- We tune alerts so only real problems trigger them
- We investigate alerts within the agreed response times
- We summarise incidents in the monthly report
Good to know: Tell us your busiest times, such as sales or payroll days, so alert levels match what matters to your business.
03RunFixes & updates
Bug fixes, security patches and library updates.
Read more +Show less −
Fixes and updates keep your software working and secure as browsers, operating systems and libraries change. We fix bugs, apply security patches and update libraries on a planned schedule, using tools such as Snyk and Dependabot to flag risks. Every change is tested before it goes live.
What you get
- Bug fixes within the response times in your plan
- Security patches applied to code and servers
- Library and framework updates on a planned schedule
- Automated alerts for known security issues
- Testing of every change before release
- Log of all changes in Jira
How it works
- You report bugs by email, Slack or Jira
- We rank each issue by severity and impact
- We fix, test and release with your approval
- Planned updates run on a set schedule
Good to know: Small, regular updates are safer and cheaper than one large upgrade after years of neglect.
04RunBackups & recovery
Daily backups and tested restore plans.
Read more +Show less −
Backups and recovery make sure your data and systems can be restored quickly if something goes wrong. You get daily backups, regular restore tests and written runbooks for disaster recovery. Restore tests prove the backups work before you ever need them.
What you get
- Daily backups of databases and files
- Backups stored separately from your live system
- Regular restore tests with results recorded
- Disaster recovery runbook with step-by-step instructions
- Agreed targets for how quickly systems come back
How it works
- We review current backups and close any gaps
- We set up daily backups and retention rules
- We run restore tests on a regular schedule
- We update runbooks whenever the system changes
Good to know: A backup that has never been restored is untested, so we treat restore tests as part of every plan.
05GrowSmall improvements
Hours each month for small features and changes.
Read more +Show less −
Small improvements are a set number of hours each month for small features, content changes and tweaks to your software. You get steady progress without starting a new project, plus a monthly report of what was done. Larger changes are quoted and approved before work starts.
What you get
- Set hours each month for small features and changes
- Content and text updates done on request
- Small design and usability tweaks
- Monthly report of work done and hours used
- Suggestions for useful next improvements
How it works
- You send requests by email, Slack or Jira
- We agree priorities and estimate each request
- We build, test and release the changes
- We report hours used in the monthly report
Good to know: Keep a short, ranked wish list, so monthly hours go to the changes with the most value first.
How it works
From idea to launch
Every service runs through the same five steps. Here is what each one means for Maintenance & support.
01of 05
ReviewWeek 1Once
We review your code, hosting and risks before taking over.
You getTakeover review
What we do
- Code and dependency review
- Hosting and backup review
- Risk and priority list
You get
- Takeover review
- Risk list
- Priority fixes
From you
- Access to code and hosting
- 1 hour with your team
Tools
- GitHub
- Notion
02of 05
PlanWeek 1–2Once
Support plan, response times and a monthly price you approve.
You getSupport plan
What we do
- Agree response times
- Set up monitoring and alerts
- Plan updates and backups
You get
- Support plan
- Monthly price
- Contact process
From you
- Review and approve the plan
Tools
- Jira
- Slack
03of 05
RunEvery day↻ Repeats
Monitoring, alerts and fixes, every day.
You getStable product
What we do
- 24/7 monitoring and alerts
- Bug fixes within agreed times
- Daily backups
You get
- Fixed issues
- Uptime and error tracking
From you
- Report issues through one channel
Tools
- Sentry
- Datadog
04of 05
UpdateEvery month↻ Repeats
Security patches and updates on a planned schedule.
You getUp-to-date software
What we do
- Security patches
- Library and framework updates
- Restore tests
You get
- Patch notes
- Restore test results
From you
- Approve major updates
Tools
- Dependabot
- Snyk
05of 05
Review & growEvery month↻ Repeats
A monthly report and small improvements.
You getMonthly report
What we do
- Monthly report on uptime and fixes
- Small features and changes
- Plan for the month ahead
You get
- Monthly report
- Roadmap notes
From you
- Monthly 30-minute review
Tools
- Grafana
- Notion
FAQ
Maintenance & support questions
What is included in a support plan?
Bug fixes, security patches, dependency and OS updates, uptime monitoring, backups and a set number of hours for small improvements each month.
How are maintenance plans priced?
As fixed monthly plans based on the size of your system and the response times you need. Extra work is quoted and approved before it starts.
What response times do you offer?
Each plan states clear response times, with faster cover for critical issues. Ask us for the current service levels.
Can you support software built by someone else?
Yes. We start with a code and infrastructure audit, document what we find, then take over support.
Is there a minimum contract?
Plans run monthly with a short notice period, and you keep full access to your code and accounts throughout.
Why do apps need ongoing maintenance?
Operating systems, browsers, libraries and security threats change constantly. Without updates, apps break or become vulnerable, usually at the worst moment.
Who owns the code?
You do. All IP is assigned to you in the contract, and the code, accounts and documentation are yours from the first sprint.
Let’s talk
Let’s talk
A 30-minute call with an engineer and a clear next step for your project.