Infrastructure for ERP, SQL and remote work

CloudHosting brings the ERP vendor into the plan from the start, and in our experience vendors keep supporting a system after it moves to our Riga data centre. The vendor usually cares about the environment meeting their requirements, not about which building the server stands in. We share the planned specification with them, agree who does what during the migration window and who to call if something behaves oddly on the first working day. If your contract with the vendor names a specific setup, tell us early and we build to it rather than around it.

CloudHosting sizes an ERP server from measured numbers rather than a price list: database size and its growth over the last two years, concurrent users, reporting and month-end peaks, and the integrations running in the background. A system used by eight accountants is a very different machine from one where forty people also work in a warehouse module. We size for the peak you actually have, with headroom to grow, and we would rather tell you the current server is enough than sell a bigger one. For orientation, our dedicated servers start at 130.05 EUR a month on a 12-month term, without VAT.

CloudHosting checks your database against the limits of SQL Server Express before recommending an edition, because Express is free but capped at 10 GB per database and a small share of memory and CPU. A growing company eventually hits those caps, usually at the worst possible moment. Standard removes them and runs proper scheduled backup jobs through SQL Server Agent, which Express lacks. We look at what your system uses now and where the ceiling is, then say plainly which edition we recommend and what it costs. If Express still fits, we say so.

CloudHosting normally moves an ERP system at the version it runs today and treats an upgrade as a separate project, because mixing the two is how migrations go wrong. Moving to new hardware and upgrading the application carry separate risks, so we prefer to move the system as it is, let it run for a while, and only then talk about the version. There are exceptions: if your current version will not install on a supported operating system, or the vendor has stopped patching it, the upgrade has to be part of the plan and we say that at the survey rather than halfway through.

CloudHosting backs up ERP databases separately from files, with the database engine's own backup mechanism, because a database copied as a file while it is running is often not restorable. The copies are kept off the machine that made them, and we test a restore into a scratch environment so the procedure is proven rather than assumed. How often depends on how much work you are willing to redo: for most accounting systems the honest answer is a nightly full copy plus transaction log backups during the working day.

CloudHosting sizes a remote desktop server at about 4 GB of memory for the system plus 2.5 GB for each person working with a browser and Office open, so the number of people is a question of memory and CPU rather than a fixed cap. People who work with large spreadsheets or reports need more. The licences for each user are counted separately in the proposal. We size from your real user count with headroom, watch the load after launch, and add resources if the numbers say so rather than guessing upward from the start.

CloudHosting rents ready 1C:Enterprise servers from 56.10 EUR a month on a 12-month term, without VAT, and a larger 1C installation can be built as a project like the ones on this page. The ready servers are VPS with a high-frequency CPU, NVMe disks and Windows Server by default, in the same Riga data centre. When the base is big, many people work at once, or 1C runs next to other business systems on a shared SQL Server, a project fits better: we size a dedicated platform, move the base and publish it over remote desktop. The survey shows which of the two you need.

CloudHosting publishes an ERP system to remote users only through a VPN or a remote desktop gateway, so the SQL Server database itself is never reachable from the open internet. Every user has a named account, access is logged, and it can be revoked the same day someone leaves. Accountants at home, sales people on the road and a warehouse in another town all work in the same environment next to the database, which is why a slow home connection stops mattering. Where more protection is needed, a FortiGate firewall, which we supply as a Fortinet authorised partner, can sit in front of the platform.

CloudHosting usually switches an ERP system over in an evening or a weekend window, after a rehearsal in which the data is copied and the system is tested on the new servers. The work before that, the survey, building the servers and the rehearsal, happens while you keep working on the old system. The final switch brings over the latest data, checks key figures with your accountant and points users to the new environment. After it we watch performance and stay in touch through the first month end, which is when hidden issues tend to show.

CloudHosting keeps ERP databases in the Tier 3+ data centre it runs itself at Bērzaunes iela 1 in Riga, Latvia, inside the European Union, on hardware and a network (AS58269) that are ours. For GDPR we sign a data processing agreement that states where the data lives and who has access. Our engineers reach the servers only through named, logged accounts, to do the work you asked for or to respond to an incident. Your accounting data stays yours: when you leave, you get the database and the documentation of the setup, with no exit fee.