Skip to content
Menu
Services · Managed hosting and support

Managed hosting and support

We run client sites on Frappe Cloud and on client servers, and support them under an annual maintenance contract: a named support engineer, response times written into the contract, a monthly report, and upgrades planned with you.

Problems we are called in for

01Tickets go to a shared inbox and come back from whoever is free, who has never seen your setup.
02Nobody can say when a backup was last restored.
03Small fixes and new features share one queue, and support quietly turns into a development budget.
04The version is getting old and every upgrade is postponed.

How the work runs

The same six waypoints and three gates as every implementation.

  1. Survey · 2 weeks
  2. Chart · 2 to 4 weeks
  3. Build · 4 to 12 weeks by tier
  4. Rehearse · 3 to 5 weeks
  5. Cross over · 1 to 2 weeks, plus the parallel run
  6. Settle · 30 days
  7. Next leg · Optional add-on, as scoped
YOU SIGN ATBlueprint sign-offGo-live readiness reviewHandover sign-off
How we implement, waypoint by waypoint →

What is included

  • A named support engineer who knows your configuration and custom code, and a second engineer who reviews every change
  • Response times agreed per contract and written into it,With priority set by business impact
  • Fixes to the configuration and custom code we deliveredAnd help for users and administrators
  • Small configuration changesa new field, a print format, a permission
  • Monitoring, daily backups and tested restores, where we host the site
  • Upgrades planned and agreedWith you, run on a copy first
  • A monthly report of tickets raised and closedWhat changed and any recurring problem

How it works: from ticket to fix

  1. Your point of contact logs the ticket

    what happened, where and to whom.

  2. We classify it as a defect

    A how-to question or a change request

  3. We reproduce it on a staging copy

    Never by experimenting on live data

  4. We fix it in the right place

    configuration in the system, code in your custom app, never in ERPNext core.

  5. A second engineer reviews the change

    And it is tested on staging before release

  6. The ticket closes

    With a note on the cause; repeats go into the monthly report with a proposed cure

What is included in hosting

Most clients run on Frappe Cloud, with managed backups, upgrades and monitoring. Others run on their own servers for data residency, an air-gapped network or an existing infrastructure team: IIT Bombay's ESTEM platform runs on-premise inside the institute's own network, with releases through its GitLab pipelines.

Technology

  • Frappe Cloud

Where we have done it

FAQ

Frappe Cloud for most clients: managed backups, upgrades and monitoring. Your own server when data residency, an air-gapped network or an existing infrastructure team requires it; we then run a split app and database setup.

No. The framework is open source, the custom code is in your repository with documentation, and support after hypercare is your choice. Clients leave when they want to; a few have come back.

New modules, new integrations and new features. They run as a small project with their own requirements and sign-off, so the support queue stays free for problems.

Start a conversation

Tell us what you need.

An engineer reads it and replies within one working day with questions, not a brochure.