What it means
With self-hosting, your data and the software sit on your machine, in your office or with a hosting company you choose. You decide who has access, where backups go and when to upgrade. In return someone has to look after the server: power, internet, security patches, backups and restores. Businesses choose this for control over their data or because they already have IT staff.
Example
Kaveri Agencies runs its system on a rented virtual server:
| Need | What it takes |
|---|---|
| Server | Ubuntu 24.04 or Debian 12; at least 2 vCPU and 8 GB RAM |
| Network | A domain name, ports 80 and 443 open |
| Install | about 7.5 to 11 minutes for a fresh install |
| Backups | daily, with a copy kept off the server |
| Restore drill | 79.5 seconds from backup files to a usable site (22 Oct 2026) |
Common mistakes
- Keeping the only backup on the same server.
- Never testing a restore until the day it is needed.
- Leaving the server unpatched because “it works”.
In MyRecords
MyRecords runs on your own Linux server, with a daily backup timer and a health check every five minutes set up at install, and a yearly AMC for support and updates. Or choose MyRecords Cloud: a dedicated system per client on our servers. Either way it is the same product, with unlimited users. See cloud or your server.