Cloud & offline
Same software. Your choice of setup.
Offline / Local and Cloud are the same JPRAXC ERP with the same modules. What changes is where the server sits, who maintains it, and how your branches reach it.
Offline / Local — Runs on your premises
A dependable local deployment for organizations that need LAN-first access and direct control of their server.
- Works on local network
- Local database control
- Scheduled local backups
- Cloud-migration-ready data
Choose offline when
- Your work must continue when the internet does not
- Policy or preference requires the data to sit on your own machine
- Most users are in one building on one network
- You would rather buy the system than subscribe to it
Illustration of the offline edition running on a server in your own building: a module rail, the number of users on the local network, the time of the last local backup, a note that no internet connection is required, and a table of scheduled local backups. Illustrative interface — sample figures, not live data.
Cloud — Access from anywhere
A centrally managed cloud deployment for branches, remote teams and secure browser access.
- Multi-location access
- Centralized updates
- Managed online backups
- Scales with users and branches
Choose cloud when
- You have more than one branch, or staff who work away from the office
- You would rather we run the server, the updates and the backups
- You want to start quickly without buying hardware
- Users need access from a browser on any device
Illustration of the cloud edition reached from a browser: a module rail, the number of branches online, users signed in across locations, the time of the managed offsite backup, and a twelve-month activity chart. Illustrative interface — sample figures, not live data.
Side by side
The modules are identical in both editions. These seven points are the whole of the difference — read down the column that matches how your organisation works.
| What differs | Offline / Local | Cloud |
|---|---|---|
| Primary access | On your local network | Any browser, any location |
| Server location | Your premises | Managed hosting |
| Remote branches | Possible with additional setup | Included |
| Low-connectivity operation | Continues to work | Needs a connection |
| Updates | Applied on a scheduled visit | Applied centrally |
| Backups | Scheduled locally | Managed online |
| Migration path | Can move to Cloud later | Already cloud-native |
Both editions run the same eight modules per suite. If you are unsure, start the conversation and we will recommend one.
Moving from offline to cloud
A planned cut-over, not a rebuild. Your offline data is the starting point.
-
01
Assess
We review your current database size, users, branches and customisations, and agree what moves.
-
02
Prepare
A cloud environment is provisioned and configured to match your existing setup, module for module.
-
03
Validate
Your data is loaded and checked against the offline system while both are running, so differences surface before the switch.
-
04
Cut over
A scheduled switch, usually outside working hours, with the offline system kept available until you confirm.
Not sure which setup suits you?
Tell us how many locations and users you have. We will recommend one and explain why.
Prefer email? sales@jpcerpcloud.com