Skip to content

03.01 / Care

Monitoring and evolution.

Uptime, error and Core Web Vitals monitoring, dependency and security updates, a quarterly roadmap and full release management for web, App Store, Google Play and over-the-air updates, on a monthly senior retainer.

days from diagnosis to the new backend runningConcert Music Festival
4
Lighthouse mobile: accessibility, best practices, SEOKD.tech
100 / 100 / 100
A status screen on the wall of a hotel group's technical room: availability, response time and today's bookings, every service in green and the response time chart with a spike already resolved.

In detail

What you should know.

A technician crouches in a dark pump room reading his phone beside a caged work lamp and an open tool bag, water pooling on the concrete floor

For example: 4 days from diagnosis to the new backend running. Concert Music Festival

What it is

Monitoring and evolution is the part of a Polargate CARE retainer that keeps a live website, portal or app healthy and moving forward after launch. We watch uptime, errors and Core Web Vitals on real traffic, keep dependencies and security patches current, agree a quarterly roadmap with you, and manage every release, from a web deploy to an App Store submission or an over-the-air update. It is senior work on a fixed monthly fee, not a ticket queue.

How we do it

The retainer runs through the Polargate ServiceDesk: one place for tickets, email in and out, your hours balance and your invoices. Each plan carries an hours envelope, for example 16 maintenance hours plus 4 urgent hours a month. Continuous integration runs typecheck, lint, unit tests and a production build on every change. On kd.tech that means 155 unit tests and an external healthcheck every six hours; on the Concert Music Festival app, 106 unit tests plus an end-to-end smoke test. Once a month an audit routine reviews the live site and the repository across performance, accessibility, security, structured data and AI-search readiness, and reports before anything is deployed. Our AutoFix agent drafts fixes for routine tickets and a senior engineer reviews every diff. Releases are automated and reversible: tag-triggered pipelines build and sign iOS and Android, submit through the store APIs, and self-hosted over-the-air updates ship JavaScript changes in hours, with channels, staged rollout and a kill switch per platform.

What you get

What you take away.

Everything is written down before we start, and everything stays in accounts your company owns.

01Deliverables

  1. 01

    Uptime and error monitoring on the live product, with JavaScript error tracking and native crash reporting where there is a mobile app

  2. 02

    Core Web Vitals (LCP, INP, CLS) measured on real traffic, plus a Lighthouse check after every significant change

  3. 03

    Dependency and security updates applied in reviewed batches, verified by continuous integration before they reach production

  4. 04

    Continuous integration on every change (typecheck, lint, unit tests, production build) and a scheduled external healthcheck

  5. 05

    A monthly maintenance audit of the live site and the repository across performance, accessibility, security, structured data and AI-search readiness, reported before anything is deployed

  6. 06

    A quarterly roadmap: what we propose to improve next, agreed with you and re-prioritised each quarter

  7. 07

    Release management: tag-triggered builds and signing, App Store and Google Play submissions, and self-hosted over-the-air updates with channels, staged rollout and a per-platform kill switch

  8. 08

    A client portal and ServiceDesk with tickets, email in and out, your hours balance, your invoices and a written monthly report

02How it runs

  1. 01 · Week 1 to 2

    Takeover and baseline audit

    We take access to the repository, hosting, database, domain and analytics, then audit the live site from the outside and the code from the inside. You get a ranked list of findings and a short risk register, so you see the real state of what you own before anything is touched.

  2. 02 · Week 2 to 4

    Close the critical findings

    Critical issues go first: security headers, exposed permissions, soft 404s, broken indexation, performance blockers. Each fix travels as a reviewed pull request and is deployed with your approval, so the retainer starts from a clean, known baseline instead of inheriting debt quietly.

  3. 03 · Every month

    The monthly cycle

    Tickets flow through the ServiceDesk against your hour pool, the scheduled audit runs over the live site and the repository, and the fix agent proposes changes as pull requests. A human reviews and merges. At the end of the month you get a report of what changed, why and at what cost in hours.

  4. 04 · Every quarter

    Review and re-plan

    Every quarter we look at consumption, recurring issues and what the product needs next. The hour pool is resized up or down to match reality, evolution work is agreed as a small roadmap, and anything that has grown into a project is quoted separately instead of eating the retainer.

For example: 100 / 100 / 100 Lighthouse mobile: accessibility, best practices, SEO. KD.tech

Who it is for

We don't take every project.

We would rather tell you now than halfway through. If you recognise yourself on the left, let's talk.

It fits if

  • You have software in production that your business needs every day
  • You want a senior team that answers, not a ticket queue with no owner
  • You prefer a known monthly fee to surprise hourly invoices
  • You are fine with an agent proposing fixes as long as a person reviews every change

It is not for you if

  • You need round-the-clock cover with a response in minutes
  • You want changes in production without anyone reviewing the diff
  • You are only looking for cheap hosting
  • Nobody can give us access to the code or the servers

For example: 62 user accounts migrated with their IDs preserved. Concert Music Festival

Timing and budget

How we quote.

No price list and no hourly billing during a build. After a short call you get a written quote for your project.

Timeline
Monthly and rolling. Onboarding takes about two weeks: monitoring and error tracking wired up, continuous integration and healthchecks running, a baseline audit of the live product and the repository, and a first roadmap. Three-month minimum, then cancellable with 30 days of notice.
Team
Our team runs the retainer: it watches the alerts, plans the improvements and ships them, including native releases, infrastructure or design when the work needs them. Pedro Ciordia, CTO, reviews every change before it ships.
How the price is set
A monthly retainer sized to the system: how many hours of maintenance and urgent work it needs and how critical it is. Quoted privately before you sign.
The stack
VercelSupabaseGitHub ActionsGitHubCapacitorExpoiOSAndroidFirebasePlaywrightVitestESLintSearch ConsoleGA4ClaudeMCP

For example: 327 bilingual pages in the sitemap accepted by Search Console. KD.tech

Same line

Other services in Care.

Each service has its own page with what it includes, the usual timeline and the projects where we did it.

For example: 22 customer tickets resolved through the desk, April to July 2026. KD.tech

FAQ

What people ask us.

How much does monthly website and app maintenance cost?
Polargate CARE is a monthly retainer for a site or app under monitoring and release management, sized to the system: the hours of maintenance and urgent work it needs, the quarterly roadmap and the monthly reporting. Anything outside the hours envelope is quoted before we start. Tell us what you have live and you get a private quote.
How quickly do you respond when something breaks?
We answer within 48 business hours as standard, and urgent work comes out of a separate pool of urgent hours, so one incident does not eat your improvement budget. We do not sell 24/7 on-call cover and will not pretend otherwise. What you get instead is a senior engineer who knows your codebase, a ticket you can follow in the portal, and a fix reviewed before it ships.
Can you handle our App Store and Google Play releases?
Yes. Store releases are part of the retainer: tag-triggered pipelines build and sign iOS and Android, and we submit through the App Store Connect and Google Play APIs. For JavaScript changes we use self-hosted over-the-air updates, which reach users in hours instead of days, with channels, staged rollout and a kill switch per platform in case a build misbehaves. The Concert Music Festival app runs exactly this way.
What happens to the hours we do not use in a month?
Unused maintenance hours go into proactive improvements rather than disappearing: performance work, accessibility fixes, dependency upgrades, structured data, whatever the last audit flagged. You see the balance in your portal next to tickets and invoices. They are not a bank you can hoard indefinitely, they are a monthly envelope, and at the end of each month we tell you where they went.
How long does it take to get started, and can we cancel?
Onboarding takes about two weeks: monitoring and error tracking wired up, continuous integration and healthchecks running, a baseline audit of the live product and the repository, and a first roadmap. After that the retainer is monthly and rolling, cancellable with 30 days of notice. We do not ask for a long lock-in.
Can you maintain a site or app that another agency built?
Usually yes, and we start with an audit rather than a promise. We review the live product and the code across performance, accessibility, security and search readiness, tell you what we found and what it would cost to fix, and only then propose a retainer. If the foundation is beyond repair we say so and price a rebuild, instead of billing you every month to keep it breathing.

For example: 30 min sync interval between WordPress and the app. Concert Music Festival

Get started

Tell us what you want to build.

Websites, apps, custom systems and AI for companies that need them in production in weeks. Fill in the form or book a 30 minute call: a senior engineer answers within 48 business hours with a first take on scope, timeline and price.

What do you need?
Budget
When

At least ten characters.

Answer in writing within 48 business hours. No newsletter, no automatic sequence.

Rather answer the full brief?

First step

Discovery Sprint

Two weeks to close scope, architecture and price before anything is built.

No price list. You get a private quote, in writing, after a short call.

Then, to build, always at a fixed price

Not ready yet?

AI-native digital studio for mid-market companies

POLARGATE, S.L. · CIF B24895005
Calle Electrónica 6, 28027 Madrid, Spain