When does a self-hosted ERP make sense?
A customer accepts a quote. Project details are copied into another application, staff record time elsewhere, and invoicing waits for missing information. An ERP should connect those steps. Hosting it in an environment you control is useful only when that control serves a business need.
Choose the software first, then the infrastructure. Confirm that the licence and delivery model allow installation in your chosen environment. A cloud product with a dedicated customer account is not necessarily available for self-hosting.
Your own server can still be rented
A virtual private server runs on a provider's physical infrastructure. A dedicated physical server may be reserved for your organisation but owned by the provider. An on-premises server may be owned by your business and operated in your building.
A dedicated application instance is different again: it describes a separate application environment, not necessarily dedicated hardware or unrestricted system access. Our VPS introduction helps distinguish these terms when comparing proposals.
Ask who owns the hosting account, who holds administrator access and how you receive your records and attachments when the relationship ends. Control should be practical, including export and recovery, rather than a label on a quotation.
Reasons to choose a separate environment
You may need to schedule upgrades around production, connect to older equipment or meet a documented location requirement. A separate environment can also support unusual integration or configuration needs.
If the main problem is fragmented information, server ownership alone will not fix it. Map the route from quotation through delivery to invoicing. Identify where records are duplicated, who approves changes and which application holds the authoritative information.
A supplier-operated ERP service may be easier when you have no internal infrastructure expertise. You can outsource management of a separate environment too, but someone must own both routine operations and the incident response.
Agree who fixes each layer
A server can be online while invoices fail to send. Infrastructure monitoring will not necessarily detect that business failure.
| Area | What the agreement should answer |
|---|---|
| Operating system and database | Who patches them and reacts to alerts? |
| ERP application | Who tests and installs releases? |
| Integrations | Who investigates missing or duplicated records? |
| Backups | What is copied and who verifies restoration? |
| Incidents | Which channels, service hours and response targets apply? |
| Exit | Which data, files and documentation are supplied, at what cost? |
The label “managed” does not settle these questions. Managed and unmanaged VPS responsibilities explain why application support must be agreed separately from operating-system maintenance.
Define how much work you can lose
Imagine restoring the ERP to last night's backup. Could staff reconstruct today's orders, time entries and stock movements? If not, a daily backup alone may be insufficient.
Define acceptable data loss and downtime before selecting the backup method. Recovery may need the database, uploaded files, application configuration and integration settings. A restore exercise should show that a user can sign in and complete a meaningful workflow, not merely that a file can be downloaded.
Database backups must be consistent and appropriate to the database engine. PostgreSQL's backup documentation distinguishes logical dumps, file-system approaches and continuous archiving. Your maintainer selects the mechanism; your business defines the recovery need.
Size for actual work
Ten people recording time are a different workload from ten people generating large reports simultaneously. Consider concurrent users, database size, attachments, imports and scheduled jobs. Ask how capacity can be increased and whether doing so requires downtime.
External services need separate consideration. Keeping the ERP server in Europe does not mean that an AI integration, invoicing connection or email service processes every record there. Document where each integration sends information and what access it requires.
Compare the complete project cost
Separate one-off implementation from recurring licences, infrastructure, backups, maintenance and support. Include data cleaning, staff training and integration work. Ask how later changes, additional locations and new reports are charged.
Resappi brings CRM, projects, time recording and invoicing into one system; its suitability and any self-hosted delivery arrangement must be confirmed directly with its team. Do not assume a deployment model from a product description.
Website hosting is a separate workload from an ERP. If your business website also needs an accountable maintenance team, discuss ResaHost web hosting or contact us with the two requirements clearly identified.