Office IT infrastructure for businesses in Riga

CloudHosting moves office systems in stages, usually starting with the one that hurts most, so nothing forces a single big migration. Most companies begin with the file server or an ageing machine running an application everyone depends on. We move that first, let it settle, then plan the next step. Some systems stay in the office on purpose because moving them brings no benefit, for example a device tied to production hardware on site. The point of the first conversation is to work out that order together, not to sell you one big project.

CloudHosting counts the Windows Server, remote desktop and Microsoft 365 licences your people actually need during the survey and lists them as separate lines in the proposal, never folded into the hosting price. Whether licences you already own can still be used depends on the product and on how the system will be hosted, and we check that one by one instead of assuming. If your licensing today is a mix of old purchases and nobody is quite sure what is covered, we go through it and write down where you stand. Licensing rules change, so the count follows how your people work, not a template.

CloudHosting connects staff to the moved systems in two ways, often both: a VPN from the office network and published remote desktops that open from any computer. With the VPN, applications behave as though nothing moved. A published remote desktop gives each person a full working environment they can reach from a laptop at home or a machine in a branch office. Which one fits depends on the applications: some are happy over VPN, others are far more comfortable running next to their database and being shown to the user as a desktop.

CloudHosting prices office infrastructure individually after a survey, while the ready remote office for teams of up to 20 people starts at 200 EUR a month without VAT. For anything larger, the bill has three parts: the servers, the licences your people actually need, and the monthly support. After the survey you get all three as concrete numbers, with the monthly figure fixed before anything is ordered, and you decide from there. What moves the number most is not the hardware, it is how many people need a remote desktop and how much data has to be kept and backed up.

CloudHosting leaves Microsoft 365 mail, Teams and OneDrive where they are, and can take over the licences and the administration if you want one supplier for it. What usually moves into the data centre is the other half: the file server, the accounting or ERP system, and the applications that never fit into a cloud subscription. The two live together well, and in most offices that split is the whole design. Mailboxes and shared files are not touched during the move, so day to day communication carries on as usual.

CloudHosting hands your data back when you leave, with no exit fee: virtual machine images or plain files and a database dump, whichever fits what you are moving to, plus the documentation of how the setup is wired. There is no proprietary format holding it. Services are invoiced in EUR per paid period and nothing is charged automatically, so to stop at the end of a period you simply do not pay the next invoice; ending early inside a paid period takes 20 days' notice by email. We would rather you stayed because the service is good than because moving is painful.

CloudHosting keeps office systems in the Tier 3+ data centre it runs itself at Bērzaunes iela 1 in Riga, Latvia, so company files stay inside the European Union. The racks, the power, the cooling and the network under our own AS58269 are ours, not rented space in someone else's facility. The site runs with N+1 power and redundant cooling, is guarded and closed to visitors, and only a limited number of our own specialists have access. For GDPR we sign a data processing agreement that says where the data lives and who can reach it.

CloudHosting engineers administer the moved systems themselves: the platform is under monitoring and incident response 24/7, and engineers answer requests on working days from 9:00 to 17:00 Riga time. That covers updates, user accounts and permissions, backup checks, and the small changes an office asks for every week. Alerts go to the engineers, not to a mailbox nobody reads, and an outage that stops the company is handled at any hour. You get one contact for servers, network and licences, in English, Latvian or Russian, and the same people read the whole thread.

CloudHosting backs up office servers on a schedule written into the design, typically every night, keeps the copies apart from the servers they protect and tests restores instead of assuming they work. Files and databases are backed up differently, because a database copied as a file while it runs is often not restorable. How far back you can go, and how much recent work you could lose, are agreed per system as recovery targets, and a tighter target costs more because it means more frequent copies or a standby server. When a restore is needed, our engineers do it and tell you what was recovered.

CloudHosting regularly works next to a company's own IT person or outside administrator, and the split of duties is written down before the move. A common split is that your person keeps the laptops, printers and user questions in the office while we run the servers, network, backups and monitoring in the data centre. Named, logged admin access is set up for everyone who needs it, so it is always clear who changed what. If the person leaves or the contract ends, we can take over the rest without starting from scratch, because the setup is already documented.