Maintenance

After launch we keep the system patched, watched, and fixable, so a small bug does not become a lost weekend.

Software drifts. Dependencies age, forms break, and a page that was fast last year gets heavy. A maintenance retainer gives you a queue and a person who already knows the codebase.

JantaraX uses that time for security updates, small improvements, and checks that the public pages — including the blog and service pages — still resolve and still match what you sell.

What this includes

  • Security and dependency updates
  • Bug fixes with a written outcome
  • Performance and uptime checks
  • Content and SEO page updates
  • A monthly note on what changed

Who it is for

  • Companies with a live site and no in-house engineering team
  • Products that need small releases every month
  • Teams that want incidents handled by the people who built the system

How an engagement runs

  1. 1Agree the hours, response window, and what is in scope
  2. 2Take inventory of the repo, host, and accounts
  3. 3Fix the known issues first
  4. 4Schedule updates instead of waiting for an outage
  5. 5Report what shipped and what is still open

Questions

Is maintenance the same as a new feature build?

No. The retainer covers upkeep and small fixes. A new product area is scoped separately so the support queue stays predictable.

How fast do you respond?

We agree a response window up front. Production outages jump the queue; content tweaks wait for the next scheduled slot.