MANAGED FRAPPE / ERPNEXT

Frappe hosting, operated end to end.

We run the bench so your team doesn’t have to. Isolated sites, staged version upgrades with a tested way back, and backups we restore on a schedule to prove they work.

WHAT’S INCLUDED

Everything the bench needs, handled.

Frappe is straightforward to install and difficult to operate. The gap between those two is what you’re paying us for.

01

Managed benches, isolated sites

Each client gets its own site with its own database and file storage. Shared benches for smaller deployments, dedicated when isolation is a requirement.

  • Per-site database isolation
  • Dedicated or shared bench
  • Resource limits per site
02

Staged upgrades with rollback

Version bumps run on a staging copy of your production data first. You sign off on the result before we touch production, and we keep a restore point either way.

  • Staging clone from live data
  • Scheduled cutover window
  • Tested rollback path
03

Backups you can actually restore

Daily database and file backups with off-site copies. We run restore drills monthly — an untested backup is a rumour, not a backup.

  • Daily database + files
  • Off-site retention
  • Monthly restore drill
04

Custom app deployment pipeline

Your custom apps ship through a build pipeline, not a manual bench get-app on a Friday. Branch, review, deploy, roll back.

  • Git-based deploys
  • Per-environment config
  • One-command rollback
05

Monitoring and on-call

Site health, queue depth, scheduler status, disk and error rates. Alerts go to an engineer, not to a dashboard nobody reads.

  • Scheduler & worker checks
  • Error-rate alerting
  • Named on-call engineer

SPECIFICS

The things people ask on the second call.

Frappe versions
v14, v15 — staged upgrades between majors
Data residency
Saudi Arabia
Backup frequency
Daily, with 30-day retention by default
Restore target
Under 4 hours for a full site restore
Upgrade window
Scheduled, outside your business hours
Environments
Production and staging on every plan

MIGRATION

Moving an existing Frappe site to us.

Most migrations take two to three weeks from first call to cutover. Longer if there are custom apps to untangle.

  1. 01

    Inventory

    We list your sites, apps, custom code, integrations and data volume.

  2. 02

    Dry run

    A full copy is restored on our infrastructure and handed to you to test.

  3. 03

    Cutover

    Final sync in a scheduled window. DNS moves, old site stays warm as a fallback.

  4. 04

    Watch

    Two weeks of heightened monitoring, then into the normal support rhythm.

QUESTIONS

Before you ask us.

Yes. We take your repositories, wire them into the deployment pipeline, and version them against the Frappe release you’re on. If an app blocks an upgrade, we’ll tell you what it would cost to fix.

Send us your bench. We’ll tell you what it takes to run it.

An audit call and a written scope, before any commitment.