Berries and Company
Services / Application maintenance

We take responsibility for your business applications.

Monitoring, incident response, security patching, compliance changes and new features, under an SLA and a monthly fee per application. Onboarding starts with documentation, so nothing depends on one person, including us. Whether we built the system or someone else did.

Tell us which applications, roughly how old, and what worries you. Written reply within 2 business days.
Applications we run serve 15M+ monthly usersEU-based teamIT-liability insured
What is included

Everything an auditor asks about and a thin IT team has no time for.

Monitoring and incidents

Availability and error monitoring, alerting, incident response within the agreed hours, root cause written up. Incidents become detectable and reportable on deadline, which NIS2 and DORA expect.

Patches and compliance

Security updates for the base software, dependency upgrades before they become audit findings, adaptation to regulatory changes, tested backup and recovery drills with a written record.

Changes and features

A monthly change budget for small improvements and fixes; larger features specified and delivered in iterations. The specification is updated with every change, so documentation never lags.

Service levels

Three tiers. Priced per application, not per person.

Exact response times, hours and change budgets are set per application during onboarding. The tiers below are the shape; the numbers come with the offer.

Bronze

Internal tools with low criticality
  • Business-hours support
  • Monthly security patching
  • Quarterly review and report
  • Backup verified, recovery tested yearly

Silver

Business applications your operations depend on
  • Extended hours, defined response times
  • Monitoring and alerting
  • Monthly change budget
  • Recovery drill twice a year, written record
  • Compliance change tracking

Gold

Customer-facing or regulated systems
  • 24/7 incident response
  • Dedicated release calendar
  • Quarterly recovery drills
  • Audit support and evidence pack
  • Named technical lead
How onboarding works

First we understand it. Then we take it over.

Step 1

Document

We read the application, AI-assisted, and write down what it does, how it is deployed, where its data lives and what breaks. If documentation exists, we verify it. The result goes under version control next to the code.

Step 2

Stabilize

Monitoring, alerting, backups and a tested recovery path are in place before we sign the SLA. Known risks are listed with a recommendation: fix now, plan, or accept.

Step 3

Run and evolve

The SLA starts. Monthly reporting in the style you need, changes delivered in iterations, and a yearly review of whether the application should be kept, modernized or retired.

A strict onboarding gate protects you too: we do not sign an SLA on a system we cannot restore. If step 2 finds a problem, you get a written recommendation before any commitment.

Systems we run

Long-term operation, not just delivery.

All 13 reference projects →

Which of your applications would fail a restore test today?

Tell us about them in two or three sentences. You get a written reply within 2 business days: what onboarding would cover, which tier fits, and a rough monthly range.

Prefer to talk? Book a 30-minute meeting
Request assessment