Maintenance and care plans

Our monthly care plans keep websites, apps and platforms patched, backed up, monitored and improving, with a team that knows your code.

Overview

Software decays when nobody looks after it. Dependencies age, certificates expire, a plugin opens a security hole, and small fixes pile up until a rebuild feels like the only option. A care plan prevents that. Each month we apply updates and security patches, verify backups, watch uptime and errors, and ship a block of small changes from your list. You get a short monthly report of what we did and what we recommend next. Plans cover software we built and software we inherit, after an onboarding audit.

01 — What we deliver

  • 01

    Updates and security patches

    Framework, dependency and server updates applied and tested on staging before production.

  • 02

    Uptime and error monitoring

    Round-the-clock checks and error tracking, with alerts reaching us before your customers notice.

  • 03

    Backups and restore tests

    Automated off-site backups, with restores tested so we know they work.

  • 04

    Small changes

    A monthly allowance for content help, copy updates, minor features and fixes from your list.

  • 05

    Performance and SEO checks

    Core Web Vitals, broken links and indexing issues reviewed and fixed regularly.

  • 06

    Monthly reporting

    A plain-language summary of updates, incidents, changes shipped and recommendations.

02 — Solutions

Website care

For marketing sites and CMS-driven content that must stay fast, secure and current.

Web application and SaaS care

For products with users and data, where updates must never break a release.

Mobile app care

OS updates, SDK target changes and store policy deadlines handled before they block a release.

E-commerce care

Checkout monitoring, payment gateway updates and preparation for sale seasons.

Inherited software

Taking over software another team built, after an audit that sets a clear baseline.

03 — Delivery cycle

  1. Step 01

    Onboarding audit

    We review code, hosting, dependencies and backups to establish a baseline and flag urgent risks.

  2. Step 02

    Access and documentation

    Credentials stored securely, environments documented and a staging copy set up if missing.

  3. Step 03

    Monitoring setup

    Uptime checks, error tracking and alert routing configured for your systems.

  4. Step 04

    Monthly maintenance

    Updates, patches and backup checks applied on a regular, predictable schedule.

  5. Step 05

    Change requests

    Your requests tracked in a shared queue, prioritised together and shipped in order.

  6. Step 06

    Monthly report

    What we did, what we found and what we suggest next, in plain language.

  7. Step 07

    Quarterly review

    A call to review priorities, upcoming risks and whether the plan still fits.

06 — Why Foxbeta

  • 01

    The people who built it look after it

    For software we delivered, the same engineers maintain it, so nothing is lost in a hand-over.

  • 02

    Prevention over firefighting

    Regular updates and tested backups make emergencies rare and recoveries quick.

  • 03

    Clear scope every month

    You always know what is included, what was done and what is waiting, with no surprise invoices.

  • 04

    Support across time zones

    Response times are agreed in writing and planned around your working hours, wherever you are.

08 — FAQ

What does a care plan include?
Updates and security patches, uptime and error monitoring, backups with restore tests, a monthly allowance for small changes, performance and SEO checks, and a monthly report. Exact scope is agreed per plan.
How much does a care plan cost?
It depends on the size of the system, the number of environments, how many change hours you need each month and the response times you require. We give a fixed monthly quote after a short review of your software.
Can you maintain software another team built?
Yes. We start with an onboarding audit to understand the code and hosting, fix anything urgent and then move onto the regular monthly cycle.
What happens if something breaks urgently?
Monitoring alerts us directly. Urgent issues are handled within the response time agreed in your plan, and you receive a short incident note afterwards explaining the cause and the fix.
Do we need a care plan if our site is brand new?
New software still needs updates, monitoring and backups from day one. A care plan also gives you a steady channel for the small improvements that follow every launch.

What happens next

  1. 01

    We reply within one working day

    A real person, with first questions about your goals.

  2. 02

    We clarify scope and constraints

    A short call about users, timelines, budget and risks.

  3. 03

    You get a written proposal

    Scope, team, timeline and a fixed or monthly price.

  4. 04

    We start building

    Kickoff within the week, a shared board and weekly demos.

Start a project

Bring the idea. We bring the team that ships it.